SQL Server Q&A

Symptoms
When you use Database Engine Tuning Advisor (DTA) to tune a database in Microsoft SQL Server 2005 Service Pack 2 (SP2), you receive the following error message:

An unhandled win32 exception occurred in dtaengine90.exe [4308].Additionally, a minidump file is generated in the SQL Server 2005 log.
Resolution
The fix for this issue was first released in Cumulative Update3. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
939537?(http://support.microsoft.com/kb/939537/LN/) Cumulative update package 3 for SQL Server 2005 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 2005 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:
937137?(http://support.microsoft.com/kb/937137/LN/) The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was releasedMicrosoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

Symptoms
In Microsoft SQL Server 2005 Service Pack 2, you run a query that selects many columns and that joins many tables. When you do this, you may receive the following error messages:
Error message 1

8624 error is being generated and a mini-dump written by the exception handler.
Error message 2

Msg 8624, Level 16, State 1, Line 1
Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services.Additionally, a minidump file is generated in the SQL Server log.
Resolution
This issue occurs because the query runs under the execution context of the sp_cursoropen stored procedure. The SQL Server 2005 Database Engine generates an exception when SQL Server 2005 tries to create an execution plan.

Symptoms
When you try to run a SQL Server Integration Services (SSIS) package in Microsoft SQL Server 2008, the Integration Services package may not run as expected. You may receive an error message that resembles the following:

Warning: Script Task 1: Found SQL Server Integration Services 2005 Script Task “ScriptTask_eec78d42403c4257ba3bd09c2352f060″ that requires migration!
Error 0×3: Script Task 1: There was an exception while loading Script Task from XML: System.IO.FileNotFoundException: Could not load file or assembly ‘VSTADTEProvider.Interop, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’ or one of its dependencies. The system cannot find the file specified.
File name: ‘VSTADTEProvider.Interop, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’
at Microsoft.SqlServer.VSTAHosting.VSTAScriptingEngine.EnsureDTEObject()
at Microsoft.SqlServer.VSTAHosting.VSTAScriptingEngine.InitNewScript(String languageID, String projectname, String projectext, Boolean bCleanupOnClose)
at Microsoft.SqlServer.VSTAHosting.VSTAScriptingEngine.InitNewScript(String languageID, String projectname, String projectext)
at Microsoft.SqlServer.Dts.Tasks.ScriptTask.ScriptTask.LoadFromXML(XmlElement elemProj, IDTSInfoEvents events)
Resolution
This problem can occur when the following conditions are true:SQL Server 2008 is installed on an IA-64-based computer.The Integration Services package was created in one of the following versions of SQL Server: SQL Server 2008 Release Candidate 0 SQL Server 2008 Community Technology Preview 6 SQL Server 2005 Service Pack 2 SQL Server 2005 Service Pack 1 SQL Server 2005The Integration Services package contains a script task or a script transform.

Symptoms
On a computer that is running Windows Vista, you install a default instance of Microsoft SQL Server 2005 Service Pack 2 or alater version of SQL Server 2005. On the same computer, you install a named instance of Microsoft SQL Server 2008. For example, you install an instance that is named “SQL2008.”
In this scenario, you may receive an error message that resembles the following when you start the SQL Server 2008 Reporting Services Configuration Manager:

No report servers were found. Details: Invalid namespace
Resolution
This problem occurs if the SQL Server 2008 Reporting Services Configuration Manager points to the SQL Server 2005 Reporting Services instance, and it cannot find the SQL Server 2008 instance.