Select the product you need help with
FIX: "Incorrect syntax" error message when you use a catalog database whose name contains a special character in SSRS 2008Article ID: 2635540 - View products that this article applies to. On This PageMicrosoft 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. SYMPTOMSConsider the following scenario:
Error Message: Incorrect syntax near 'ServerDB' for Step 1. Step 1 Command: "exec <catalog database name>.dbo.AddEvent @EventType='TimedSubscription', @EventData='<some id>" CAUSEThis 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." RESOLUTIONCumulative update informationSQL Server 2008 Service Pack 3The 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 Note 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:
(http://support.microsoft.com/kb/2648098/LN/
)
Cumulative update package 3 for SQL Server 2008 Service Pack 32629969 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.
(http://support.microsoft.com/kb/2629969/LN/
)
The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 3 was released SQL Server 2008 Service Pack 2 (SP2) cumulative update package 7The 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 Note 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:
(http://support.microsoft.com/kb/2617148/
)
Cumulative update package 7 for SQL Server 2008 Service Pack 22402659
(http://support.microsoft.com/kb/2402659/
)
The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was releasedWORKAROUNDTo work around this issue, use one of the following methods:
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. PropertiesArticle ID: 2635540 - Last Review: January 17, 2012 - Revision: 4.0
| Article Translations
|


Back to the top








