Microsoft distributes Microsoft SQL Server 2008 SP2 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 SP2 fix release.
Symptoms
Consider the following scenario:
-
You have an instance in Microsoft SQL Server 2008 Reporting Services (SSRS 2008).
-
The catalog database name contains a special character, such as a hyphen.
-
You create a subscription for the instance in SSRS 2008.
In this scenario, you receive an error message that resembles the following:
Error Message: Incorrect syntax near 'ServerDB' for Step 1.Step 1 Command:"exec <catalog database name>.dbo.AddEvent @EventType='TimedSubscription', @EventData='<some id>"
Cause
This issue occurs because the catalog database name is not enclosed in double quotation marks or in square brackets. Therefore, the command fails.Note The catalog database name appears in the command in the error message that is mentioned in the "Symptoms" section."
Resolution
Cumulative update information
SQL Server 2008 Service Pack 3
The fix for this issue was first released in Cumulative Update 3 for SQL Server 2008 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2648098 Cumulative update package 3 for SQL Server 2008 Service Pack 3Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2629969 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 3 was released Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 3 hotfix to an installation of SQL Server 2008 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
SQL Server 2008 Service Pack 2 (SP2) cumulative update package 7
The fix for this issue was first released in Cumulative Update 7. For more information about how to obtain this cumulative update package for SQL Server 2008 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
2617148 Cumulative update package 7 for SQL Server 2008 Service Pack 2Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 Service Pack 2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2402659 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released
Workaround
To work around this issue, use one of the following methods:
-
Delete any special characters from the catalog database name.
-
Add double quotation marks or square brackets to the catalog database name.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
