| 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. |
