| VSTS bug number || Description |
| 295196, 771825 ||You may receive the following warning message when you create the maintenance plan if the Shrink Database option is enabled in SQL Server 2008: "Shrinking of data files moves data and can cause fragmentation of the indexes within those files." |
| 295750 ||Various diagnostic tools incorrectly report the master database for queries that were executed against other databases in SQL Server 2008. |
| 337272 ||The principal Lazy Writer does not start if the 0 NUMA node contains no processor in SQL Server 2008. |
| 444202 ||A user cannot change their password in SQL Server 2005 by using SQL Server Management Studio (SSMS) of SQL Server 2008. |
| 447990 ||Assume an indexed view projects columns from the base and non-base tables, and assume a column from the non-base table has the same order id and type as a column of the base table. In this scenario if SQL Server 2008 SP3 is installed, an error occurs instead of a partition switch. |
| 450529 ||Assume that you open SSMS as a non-administrator and then you try to attach a database. In this scenario if SQL Server 2008 SP3 is installed, you receive an "Access is denied" error instead of an exception. |
| 507222 ||Consider the following scenario: |
- You create a database.
- A query is cached for this database.
- You delete the database, and then you create a new database.
- You create the deleted database again, and then you run the query.
In this scenario, you receive a "Read Access violation in FullXactImpBase::GetXdes xact.cpp @ 2536" error in SQL Server 2008.
| 546001 ||The fix for the issue of this bug resets the name for a table-valued parameter when you create a default value for the table-valued parameter. After you install SQL Server 2008 SP3, the TableVarElem element always has the correct name when it retrieves default values from the Temp table cache. |
| 643903 ||No event notifications for database-level events might be generated when a cross-database DDL operation is performed. This issue occurs because incorrect dialog handles are used. |
| 650111 ||An application cannot connect to SQL Server 2008 if a side-by-side installation of SQL Server code-named "Denali" is installed. This issue occurs because of a null pointer. When the null pointer is used, up-level instances installed on the computer are ignored. After you install SQL Server 2008 SP3, the null pointer is not used when you use SQL Server 2008 Configuration Manager. |
| 703968 ||After you install SQL Server 2008 SP3, the query optimizer can handle different output values for the same input value from the CRYPT_GEN_RANDOM column. |
| 704992 ||Issues for integral data conversions on x64-based operating systems. These issues occur because of the BindParameter method and of LONG data type parameters that are used by this method. |
| 707059 ||Profiler might not display all the events and columns for both SQL Server Database Engine and SQL Server Analysis Services. After you install SQL Server 2008 SP3, new trace template files for SQL Server Database Engine and for SQL Server Analysis Services are generated separately. |
| 709063 ||Slow performance issue occurs when you run the mdw_purge_data_[<your MDW database name>] data collector job to perform a DELETE operation. This issue occurs if a data collector of Microsoft SQL Server 2008 Management Data Warehouse (MDW) is running on a large-scale MDW database.|
| 741462 ||When running an SSIS Package from the DTExec.exe runtime utility, or from a SQL Agent Job Step, some output logging events may be missing from the logged output. Events such as OnInformation, OnProgress, Diagnostic, OnPostExecute, and PackageEnd events may be missing in the output. Commonly observed informational log events such OnInformation: "OLE DB Destination" wrote ###### rows." may be missing from the output. Other runtime utilities such as DTExecUI.exe and DtsDebugHost.exe (when debugging an SSIS package from the BIDS environment) are not affected by the problem.|
| 755932 ||LAG and LEAD analytical functions do not work in Package and Deployment Wizard (PDW) Engine. This issue occurs because some information in the MemoXML scheme is removed. |
| 771381 ||Incorrect pointer of memory object is allocated when you delete a database with a FILESTREAM filegroup. |
| 540323 ||An access violation occurs when an application tries to raise the 9530 error code. This issue occurs because a NULL pointer is used. |
| 778341 ||The SCOPE_IDENTITY() function might return incorrect values. |
| 536835 ||Setup crashes when you install Microsoft SQL Server 2008 on a computer that has SQL Server 2000 Service Pack 3 (SP3) Online Analytical Processing (OLAP) installed. This issue occurs because SQL Server 2000 SP3 OLAP incorrectly set the version registry key to Service Pack 3.0.|
| 544926 ||If you do not modify any property when you try to change the DatabaseEncryptionKey SQL Server Management Objects (SMO) object, database SMO object does not update DatabaseEncryptionKey value.|
| 729229 ||After you install SQL Server 2008 SP3, results of an enumeration are not cached and are not stored in local variables to enumerate resources. Additionally, disks are validated only one time, and the results are stored for subsequent requests.|
| 425485 ||After you install SQL Server 2008 SP3, all landing page links that run Setup scenarios are disabled.|
| 700081 ||When an application looks up names for base counters of a ratio counter, the application has to perform a substring lookup operation that is not case-sensitive in SQL Server 2008.|
| 281309 ||Incorrect CPU time when you run parallel query plans for the sys.dm_exec_query_stats table. |
| 356915 ||An error occurs when internal buffers for asynchronous read operations divide a multiple-character column delimiter into two parts. After you install SQL Server 2008 SP3, the current parsing pointer is reset after buffers are switched.|
| 645220 ||SQLAgent.exe does not run when a valid SQLAgent.exe command is typed at a command prompt. This issue occurs because of a permissions error for shared memory.|
| 747046 ||After you install SQL Server 2008 SP3, a database is not created if the database name is the same as the name of the current database user. |
| 769191 ||SQL Server 2008 SP3 contains updated VER_PRODUCTLEVEL_STR and VER_PRODUCTLEVEL_WSTR global variables in the Ntverp.h file. These variables are updated to SP3.|
| 453592 ||A user cannot access a catalog database if the user specifies a port for the database server in Microsoft SQL Server 2008 Reporting Services Configuration Manager.|
|773344||Execution account information contains truncated strings in the Russian localized build of Microsoft SQL Server 2008 Reporting Services Configuration Manager.|