SQL Server Q&A

Symptoms
On server that is running Microsoft SQL Server 2008 Reporting Services, you generate a report from a custom data extension data source. To do this, you use the “Asynchronous Processing = True” setting in the connection string property.When you run the report, the report server stops responding.
Resolution
This issue occurs because the System.Data.SQLclient namespace does not support asynchronous processing in any hosted common language runtime (CLR) environment. Because Reporting Services hosts the CLR within the Reporting Services process, the asynchronous call always fails.
Note The System.Data.SQLclient namespace is the SQL Server .Net Data Provider.

Symptoms
When you try to install or upgrade to Microsoft SQL Server 2008, the results of rule checks may be logged incorrectly in the System Configuration Check Report (SystemConfigurationCheck_Report.htm) file and in the Detail.txt log file. For example, the results of the Engine_UserHasNotDefinedSchemaSysCheck rule check may be logged as “Not Applicable.” This occurs even though there is a schema named “sys” in one of the SQL Server databases.
Note This rule check determines whether the user has defined a schema called ’sys’.
Resolution
This problem can occur if the rule is evaluated by using a three-state rule check in SQL Server 2008. A three-state rule check is a rule that can return a Passed, Failed, or Warning status.