SQL Server Q&A

Symptoms
In Microsoft SQL Server, you use a TRY…CATCH construct to process exceptions that are raised from the DBCC CHECKDB statement. However, when the DBCC CHECKDB statement detects a consistency error in the database, the CATCH block is not triggered.
Note This behavior also occurs in SQL Server 2008.
Resolution
This behavior occurs because the DBCC CHECKDB statement does not raise an exception when the DBCC CHECKDB statement detects a consistency error inside the database.

Symptoms
When you expand the Databases folder in Object Explorer in Microsoft SQL Server 2008 Management Studio, the Databases folder may take longer than expected to open. For example, the Databases folder may take several minutes to open.
Note This issue occurs only for instances of Microsoft SQL Server 2008 that have a large history of backups.
Resolution
This issue occurs because of a sub-optimal query that SQL Server 2008 Management Studio runs. This query is run when one of the following columns is enabled in the Object Explorer Details window for the Databases folder:Last Backup DateLast Log Backup Date

Symptoms
After you uninstall Microsoft SQL Server 2005 from a computer that has Microsoft SQL Server 2008 installed, the Microsoft ActiveX Script task in a SQL Server Integration Services package does not run.Additionally, when you try to add an ActiveX Script Task to a new package in BIDS, the task will show a validation error pointing ScriptHost can’t be instantiated.
Resolution
This problem occurs because the Axscphst.dllfile is deleted or is unregistered after you uninstall SQL Server 2005. The Axscphst.dllfile is in the following location:
%SystemRoot0%\Program Files\Microsoft SQL Server\100\COMNote SQL Server 2005 and SQL Server 2008 use the Axscphst.dll file.