Update für SQL Server 2005 Service Pack 2
Critical Update for SQL Server 2005 Service Pack 2 (KB933508)
If you downloaded SQL Server 2005 SP2 before March 05, 2007, apply the general distribution release (GDR) update for those SQL Server 2005 SP2 installations. The GDR update is available at the Microsoft Download Center:
Critical Update for SQL Server 2005 Service Pack 2 (
> )The GDR update corrects the interpretation of cleanup tasks that were created by using the original release version of SQL Server 2005 and by using SQL Server 2005 SP1. If you created or edited maintenance plans or Integration Services packages by using the initial release version of SQL Server 2005 SP2, you must verify and update the cleanup task intervals after you apply the GDR update. If you do not do this, cleanup tasks will retain data longer than intended.
To verify and update cleanup task intervals, follow these steps:
- Open the maintenance plan or the Integration Services package.
- Open each cleanup task.
- Adjust the cleanup interval to the correct value.
- Save the plan or the package.
Tests to determine which version of SQL Server 2005 SP2 is installed should inspect the file in %ProgramFiles%\Microsoft SQL Server\90\DTS\Tasks. If the SP2 file version is greater than or equal to 9.00.3017.00 and less than 9.00.3042.00, the SP2 version is pre-release and you should install the SP2 refresh. If the file version equals 9.00.3042.00, the version is the initial SP2 release, and you should apply the GDR update.
The GDR update detects file versions and updates the files as necessary. However, if you need to verify file versions, you can use Microsoft Windows Explorer or the Filever command-line utility:
• To check the file version on individual computers, open Windows Explorer, right-click the file, select Properties, and then click the Version tab.
• To help with checking file versions on many computers, the Filever command-line utility is available. For more information about the Filever command-line utility, click the following article number to view the article in the Microsoft Knowledge Base:
913111 (
> ) How to use the Filever.exe tool to obtain specific information about a file in Windows
Quelle:
http://support.microsoft.com/kb/933508
Download:
http://www.microsoft.com/downloads/details.aspx?FamilyID=e2c358a1-ecc4-4c49-8f65-daa6b7800eec&DisplayLang=en
http://www.microsoft.com/downloads/details.aspx?FamilyID=e2c358a1-ecc4-4c49-8f65-daa6b7800eec&DisplayLang=de
Cumulative hotfix package (build 3152) for SQL Server 2005 Service Pack 2 is available
SQL Server 2005 hotfixes are now multilanguage. There is only one cumulative hotfix package for all languages.
SQL Server 2005 post-SP2 hotfixes that are included in SQL Server 2005 build 9.0.3152
Note Microsoft Knowledge Base articles that discuss these hotfixes will be released as they become available.
SQL bug number Description
50000783 When you define the value of the AdminTimeout property and the value of the ServerTimeout property, a profiler trace stops unexpectedly.
50000784 When you make a data manipulation language (DML) change to a published table, error 2812 occurs.
50000785 When you create a cursor by using an SQL statement that uses the OPTION (RECOMPILE) hint, error 16943 occurs. Error 16943 indicates that the table schema changed. This problem occurs when you retrieve information from the cursor location.
50000786 A memory leak exists in the MSOLAP provider (Msolap90.dll).
50000787 When you configure the Scheduler component to use a time-out value that is less than 15 milliseconds, you experience high CPU usage.
50000809 The LazyWriter process uses lots of CPU resources. This problem occurs on a non-uniform memory access (NUMA)-enabled x64-based server that is running SQL Server 2005 x64 Edition.
50000810 When you update a view through a cursor, you cannot make a CSEQUAL request or a TSEQUAL request for rows that are extended by using NULL values.
50000873 When you run an application in SQL Server 2005, error 8624 occurs. Error 8624 indicates that the cycle check failed.
50000874 When the stored procedure runs outside an explicit transaction, a temporary table in a stored procedure is not cleaned up correctly.
50000889 When you run a Microsoft Office Excel data mining operation, you receive the following error message:
The 'MINIMUM_DEPENDENCY_PROBABILITY' data mining parameter is not valid for the 'Table1_283833_NB_413946' model
50000939 The Maintenance Cleanup task uses an incorrect age group for cleanup operations.
Download:
x86
http://download.microsoft.com/download/7/3/f/73fe973b-5273-433d-adf9-178e670a84bc/sqlserver2005-kb933097-x86-enu.exe