Sign in with Microsoft
Sign in or create an account.
Hello,
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.

INTRODUCTION

This article lists SQL Server 2008 issues that are fixed by Microsoft SQL Server 2008 Service Pack 3 (SP3).

Notes

  • Some issues that are not documented might be fixed by the service pack.

  • The list of issues will be updated when the articles for the issues are released.


For more information about how to obtain SQL Server 2008 service packs, click the following article number to view the article in the Microsoft Knowledge Base:

968382
How to obtain the latest service pack for SQL Server 2008
Note Microsoft distributes Microsoft SQL Server 2008 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. Typically, you should download the latest service pack.

Download Download SQL Server 2008 Service Pack 3 now

More Information

SQL Server 2008 SP3 fixes the following issues:

  • Issues that are listed in this article

  • Issues that were fixed in the following cumulative update packages for Microsoft SQL Server 2008 Service Pack 2 (SP2):

    • Cumulative update package 1 for SQL Server 2008 SP2

    • Cumulative update package 2 for SQL Server 2008 SP2

    • Cumulative update package 3 for SQL Server 2008 SP2

    • Cumulative update package 4 for SQL Server 2008 SP2


For more information about the cumulative update packages that are available for SQL Server 2008 SP2, click the following article number to view the article in the Microsoft Knowledge Base:

2402659 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released The following table provides more information about the products or tools that automatically check for this condition on your instance of SQL Server and on the versions of the SQL Server product against which the rule is evaluated.

Rule software

Rule title

Rule description

Product versions against which the rule is evaluated

System Center Advisor

SQL Server missing update KB2546951 to guarantee principal lazywriter is started

System Center Advisor determines whether this instance of SQL Server is running on a server that has more than 64 logical processors. Also, advisor checks the current build and version of sqlservr.exe. If the current build of sqlservr.exe is less than the fix build, the advisor generates the alert about this issue. Review the details that are provided in the “Information Collected” section of the advisor alert, and apply the fix that is discussed in this article. This advisor alert refers to the fix ID 337272 that is mentioned in this article.

SQL Server 2008

Issues that are fixed by SQL Server 2008 SP3

For more information about the issues, click the following article numbers to view the articles in the Microsoft Knowledge Base.

VSTS bug number

KB article number

Description

721415

2550552

FIX: SQL Server command stops responding when it uses a nonbuffered access path to access a FILESTREAM file in SQL Server 2008 R2 or SQL Server 2008

611967

922578

FIX: Lots of messages that have message ID 19030 and message ID 19031 are logged in the SQL Server 2005 Errorlog file when you use SQL Server Profile in SQL Server 2005

628427

2463682

FIX: A database that has transparent data encryption enabled may be marked as "suspect" if the server certificate is dropped in SQL Server 2008 R2

729461

2500042

"SQL Server 2008 Setup requires Microsoft .NET Framework 4.0 to be installed" error message when you apply Service Pack 2 (SP2) for SQL Server 2008

757676

2565683

FIX: You may receive incorrect results when you run a complex query that contains aggregates functions, join functions, and distinct functions in subqueries in a SQL Server 2008 environment

746231

2569923

FIX: Upload jobs of data collector quickly open and close a large number of TCP ports if the jobs upload data to a MDW database in SQL Server 2008 or in SQL Server 2008 R2

429231

2588050

FIX: Slipstream installation of a SQL Server 2008 service pack might fail

717065

2588453

FIX: Access violation when DTA runs a query against a table in SQL Server 2008 if there is an index on a spatial data type column of the table

644781

2589980

Fix: Incorrect results or constraint violation when you run a SELECT statement or a DML statement that uses the row_number function and a parallel execution plan in SQL Server 2008

420834

2590124

FIX: "ChainerInfrastructureException" error when you install SQL Server 2008

666690

969052

How to restore the missing Windows Installer cache files and resolve problems that occur during a SQL Server update

406407

2591753

FIX: An update is available to add SPN information for service accounts to the Reporting Services log file

Additional issues that are fixed by SQL Server 2008 SP3

The following issues are also fixed by SQL Server 2008 SP3.

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.

References

For more information about how to determine the current SQL Server version and edition, click the following article number to view the article in the Microsoft Knowledge Base:

321185
How to identify your SQL Server version and edition
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!

×