VSTS bug number | KB article number | Description |
365478 | 974749 | FIX: The last character of a char column or an nchar column is incorrectly replaced by a space character (char(32)) after a conflict is resolved by a customized conflict resolver in SQL Server 2005 or in SQL Server 2008 |
365460 | 971622 | FIX: The memory usage of a SQL Server service increases quickly when you run a query that uses a linked server in SQL Server 2005 or in SQL Server 2008 |
365450 | 972937 | FIX: A performance issue in which SQL Server Management Studio checks the fragmentation data of an index in a large database |
355200 | 973357 | FIX: Setup of SQL Server 2008 fails when the setup binary files are located in a folder whose path is in the 8.3 compatible format |
365456 | 973643 | FIX: The synchronization of a merge publication that uses Web synchronization takes a very long time to finish after the initial synchronization in SQL Server 2005 or in SQL Server 2008 |
365510 | 974067 | FIX: You use the COUNT function on a column that is returned by a subquery that returns no rows in SQL Server 2005 or in SQL Server 2008, and an incorrect result is returned |
365462 | 974130 | FIX: A memory leak may occur if you use a linked server query to retrieve a sql_variant column from a remote server in SQL Server 2005 or in SQL Server 2008 |
365464 | 974205 | FIX: Error message in the Errorlog file of SQL Server 2005 or of SQL Server 2008 after the SQL Server service stops responding: "Timeout occurred while waiting for latch" |
365467 | 974319 | FIX: Error message when you use database mirroring in SQL Server 2005 or in SQL Server 2008, and an assertion failure occurs intermittently: "SQL Server Assertion: File: <loglock.cpp>, line=823 Failed Assertion = 'result == LCK_OK'." |
365476 | 974660 | FIX: You receive out-of-memory error messages when you use merge replication with Web synchronization in SQL Server 2005 or in SQL Server 2008 |
365480 | 974777 | FIX: Database restore operation may fail during the recovery phase when the database uses query notification in SQL Server 2005 or in SQL Server 2008 |
365474 | 974785 | FIX: An API cursor plan that is created by a plan guide is not reused when the cursor is active in SQL Server 2005 and in SQL Server 2008 |
343726 | 975055 | FIX: Error message when you install SQL Server 2008 on a computer that is running Windows 7: "Invoke or BeginInvoke cannot be called on a control until the window handle has been created." |
365489 | 975089 | FIX: The restore operation takes a long time when you restore a database that has query notification enabled in SQL Server 2005 or in SQL Server 2008 |
365491 | 975090 | FIX: Deadlocks may occur when multiple concurrent query notification subscriptions are fired on same objects in SQL Server 2005 or in SQL Server 2008 |
365454 | 975134 | FIX: Capitalization and accent changes on a column of user-defined data type are not propagated in SQL Server 2005 merge replication or in SQL Server 2008 merge replication |
365454 | 975159 | FIX: For SQL Server Compact Edition (CE) Subscribers, only schema without data is replicated for newly added articles to an existing Merge Publication using “ExchangeType.Upload” |
365469 | 975417 | FIX: A SELECT statement returns an incorrect result set if a linked server is being used in SQL Server 2005 or in SQL Server 2008 |
365500 | 975681 | FIX: The database mirroring session is suspended when you add more than one log transaction file to a folder on the principle server that does not exist on the mirror server in SQL Server 2005 or in SQL Server 2008 |
365503 | 975748 | FIX: You cannot process an object when you change or delete another unrelated object at the same time in the same database in SQL Server 2005 Analysis Services or in SQL Server 2008 Analysis Services |
365507 | 975783 | FIX: You receive an incorrect result when you run an MDX query against a dimension that has a parent/child relationship after you install a cumulative update in SQL Server 2005 Analysis Services or in SQL Server 2008 Analysis Services |
365512 | 975860 | FIX: A full backup with snapshot may cause SQL Server 2005 or SQL Server 2008 to stop responding |
357673 | 975991 | FIX: The DBCC CHECKFILEGROUP statement does not check a partitioned object if the partitioned object exists in multiple file groups in SQL Server 2008 |
365514 | 976030 | FIX: Error message after you perform a Process Update on a dimension used on a cube that contains a writeback partition: "Errors in the high-level relational engine. The data source view does not contain a definition for the <tablename> table or view" |
365505 | 976041 | FIX: You receive an incorrect result when you run a query that uses a parallel execution plan in SQL Server 2005 or in SQL Server 2008 |
362018 | 976414 | FIX: Full-text search functionality does not work in SQL Server 2008 Express Edition even after you installed SQL Server 2008 CU2 |
365414 | 976761 | FIX: Error message when you perform a rolling upgrade in a SQL Server 2008 cluster : "18401, Login failed for user SQLTEST\AgentService. Reason: Server is in script upgrade mode. Only administrator can connect at this time.[SQLState 42000]" |
361640 | 977109 | FIX: After you run the merge agent during the initialization of the subscription in SQL Server 2008, the ident_current() function returns a value that is larger than expected |