They have also released SQL Server 2014 Service Pack 1 Cumulative Update 11, which is Build 12.0.4502.0. There are 15 hotfixes in the public fix list for this CU.

There is no corresponding CU for the RTM branch, since SQL Server 2014 RTM is no longer a supported Service Pack level.

The post SQL Server 2014 Service Pack 2 Cumulative Update 4 appeared first on Glenn Berry.

As they previously did for SQL Server 2014 SP2, Microsoft has managed to include all of the hotfixes from the latest SQL Server 2016 RTM CU3 in SQL Server 2016 SP1 RTM, including the very recent security fixes in Security Update MS16-136, so there is no need to wait for a subsequent SP1 CU to get caught up with the latest fixes from the RTM branch.

The Microsoft SQL Server Release Services Blog has a lot more detail about SQL Server 2016 SP1 here. The Data Platform blog has more detail about SP1 feature improvements here.

Given all of the feature changes and other useful improvements in SQL Server 2016 Service Pack 1 (on top of all of the hotfixes), it is almost a no-brainer to move to SQL Server 2016 Service Pack 1 as soon as you can do your testing, and plan and implement your deployment.

This is also a good time for organizations that are running down-level versions of SQL Server Standard Edition to seriously consider upgrading to SQL Server 2016 Standard Edition (preferably on new hardware, running Windows Server 2016).

The post SQL Server 2016 Service Pack 1 and SQL Server 2016 RTM CU3 appeared first on Glenn Berry.

These include Row-level security, Dynamic Data Masking, Change Data Capture(*), Database Snapsnots, Columnstore indexes, Table Partitioning, Data Compression, Multiple Filestream containers, In-Memory OLTP, Always Encrypted, Distributed Partitioned Views, Polybase, and Fine grained Auditing.

There are some scalability limits for some of these features running on Standard or Web/Express Edition. For example, In-Memory OLTP is limited to 1/4 of the Edition buffer pool memory limit. Columnstore is also limited to 1/4 of the Edition buffer pool memory limit. These feature memory limits are in addition to the buffer pool limit for each edition.

In Standard Edition, Columnstore is limited to 2 DOP, and in Web/Express is limited to 1 DOP. Polybase worker compute nodes can be deployed on Standard, Web, and Express Editions, but still requires Enterprise Edition for the head node to scale out with (multiple worker compute nodes).

Keep in mind that you will need SQL Server 2016 Service Pack 1, to get these new features (and many other nice improvements, as detailed here).

The primary goal here is to provide application developers with an easy way to program an application in the same way using all of the application features of SQL Server 2016, regardless of which edition of SQL Server 2016 that the application may eventually be deployed on.

This is going to make it much easier for ISVs to use these features without requiring their customers to use Enterprise Edition. They will be able to simplify their deployment scripts by not having to check the Edition of SQL Server before they run DDL statements to create database objects. This is a very welcome development that should encourage many more organizations to move to SQL Server 2016.

Once you have an application using SQL Server 2016 Standard Edition, you can just do an Edition Upgrade to Enterprise Edition to get even more scalability and performance, taking advantage of the higher license limits in Enterprise Edition. You will also get the intrinsic performance benefits that are present in Enterprise Edition. Microsoft should consider publicizing some of these performance differences between Standard Edition and Enterprise Edition.

Note: Change Data Capture won’t be available in Express Edition, since it does not have SQL Server Agent.

The post Major Changes for SQL Server 2016 Standard Edition appeared first on Glenn Berry.

June 20, 2016    SQL Server 2014 RTM CU14 (12.0.2569)

June 20, 2016    SQL Server 2014 SP1 CU7 (12.0.4459)

July 11, 2016     SQL Server 2014 SP2 RTM (12.0.5000)

SQL Server 2014 RTM CU14 will be the last cumulative update for the SQL Server 2014 RTM branch, and it is now an “unsupported service pack”. If you are still on the RTM branch, you should be be planning on moving to either SP1 or preferably SP2. SQL Server 2014 SP2 RTM has all of the fixes that are in SQL Server 2014 SP1 CU7, so there is no need to wait for SQL Server 2014 SP2 CU1 in order to “catch up” to the previous branches. It also has a number of new features and performance improvements (which you can read about here), so I think people are going to want to move to the SP2 branch relatively soon.

You can find the official Microsoft Build list for SQL Server 2014 here:

SQL Server 2014 Build Versions

For SQL Server 2012, we have these updates:

July 18, 2016     SQL Server 2012 SP2 CU13  (11.0.5655)

July 18, 2016     SQL Server 2012 SP3 CU4    (11.0.6540)

As always, I think you are better off to be on the latest Service Pack for whatever version of SQL Server you are using. For SQL Server 2012, the RTM and SP1 branches are both considered “unsupported service packs”. You need to be on either SP2 or SP3, preferably SP3.

You can find the official Microsoft Build lists for SQL Server 2012 SP3 and SP2 here:

SQL Server 2012 SP3 build versions

SQL Server 2012 SP2 build versions

Finally, if you or your organization are still reluctant to deploy SQL Server Cumulative Updates, you should read the current official guidance from Microsoft about this. One of the key points is “we now recommend ongoing, proactive installation of CU’s as they become available”. This does not mean that you just blindly deploy a cumulative update to Production the day it is released. Rather, you should have a good testing and deployment plan that you go through before you deploy to Production. You can read the full Microsoft guidance here:

Announcing updates to the SQL Server Incremental Servicing Model (ISM)

The post Recent SQL Server 2012 and 2014 Updates appeared first on Glenn Berry.

Table 1 shows the SQL Server 2012 SP3 CU builds that have been released so far.

Table 1: SQL Server 2012 SP3 CU Builds

You can follow the KB article link below to see all of the CU builds for the SQL Server 2012 Service Pack 3 branch.

SQL Server 2012 SP3 Build Versions

Like I did for the SQL Server 2012 SP2 branch, I decided to scan the hotfix list for all of the Cumulative Updates in the SP3 branch, looking for performance and general reliability-related fixes for the SQL Server Database Engine. I came up with the list below, but this listing is completely arbitrary on my part. You may come up with a completely different list, based on what specific SQL Server 2012 features you are using.

Here are the fixes in the Service Pack 3 branch:

SQL Server 2012 SP3 Cumulative Update 1 (Build 11.0.6518), 8 total public hot fixes

FIX: You cannot use the Transport Layer Security protocol version 1.2 to connect to a server that is running SQL Server 2014 or SQL Server 2012

FIX: SQL Server may crash when a request for execution of a remote stored procedure contains incomplete definition of arguments

FIX: You receive error messages when you run a query that uses tempdb in SQL Server

An update to enable the “-k” startup parameter to control the rate that work files can spill to tempdb is available for SQL Server 2012 Service Pack 3

FIX: The CHANGETABLE function in a query returns incorrect results when Change Tracking is enabled for a SQL Server database

SQL Server 2012 SP3 Cumulative Update 2 (Build 11.0.6523), 20 total public hot fixes

FIX: Slow performance when you query numeric data types from an Oracle database

FIX: Access violation when you execute a stored procedure that uses a cursor on a table variable in SQL Server

FIX: An assertion failure occurs on the secondary replica when you use the AlwaysOn Availability Groups feature in SQL Server 2012

FIX: Numeric overflow when you run a query that spills more than 65,535 extents to tempdb in SQL Server 2014 or 2012

FIX: Column data is deleted when you update another column in a table in SQL Server 2012

FIX: SMK initialization fails on one node of a SQL Server 2012 failover cluster

FIX: SQL Server stops responding when you back up the certificate that is used to encrypt the database encryption key in SQL Server 2012 or SQL Server 2014

FIX: XA transactions aren’t cleaned when you exit a Java application in an instance of SQL Server

FIX: Error occurs when you try to drop or delete filegroups or partition schemes and functions in SQL Server

FIX: The Log Reader Agent stops intermittently and an Access Violation occurs in SQL Server 2012

FIX: Error when you use the replication feature in SQL Server 2014 or SQL Server 2012

FIX: Access violation and the program restarts when you change an extended events session in SQL Server 2014 or 2012

 

SQL Server 2012 SP3 Cumulative Update 3 (Build 11.0.6537), 23 total public hot fixes

FIX: You do not have the permissions to execute the system sp_readerrorlog stored procedure in SQL Server 2012

FIX: Filestream directory is not visible after an AlwaysOn replica is restarted in SQL Server 2012

FIX: Cannot alter column because it is enabled for Replication or Change Data Capture error occurs after a database is restored to a SQL Server that does not support change data capture

FIX: Error 1478 when you add a database back to the AlwaysOn availability group in SQL Server 2012

FIX: “Cannot resolve the collation conflict” error when you apply a snapshot to the subscriber database in SQL Server

FIX: “A severe error occurred on the current command” when a Table-Valued User-Defined function is referred to by a synonym

FIX: Creating a database on a system that has a large amount of memory installed takes longer

FIX: “Non-yielding Scheduler” error when versioning cleanup task runs on a SQL Server AlwaysOn secondary replica

FIX: FileTables in an AlwaysOn availability group become unavailable after failover in an instance of SQL Server 2014 or 2012

FIX: sys.dm_db_index_usage_stats missing information after index rebuild on SQL Server 2012

FIX: Memory corruption causes an access violation in an instance of SQL Server 2014 or 2012

SQL Server 2012 SP3 Cumulative Update 4 (Build 11.0.6540), 19 total public hot fixes

FIX: SQL Server crashes when you run a remote query in a stored procedure by using an invalid user name

FIX: Storage device overhead when you back up data or log files to a network share in SQL Server 2014 or 2012

FIX: Memory leak on the AlwaysOn secondary replica when change tracking is enabled in SQL Server

Transaction log backup failure on the secondary replica prevents subsequent backups on Availability Replicas in SQL Server 2012

FIX: SQL Server 2012 failover cluster diagnostic log does not accurately reflect the failure_condition_level setting

FIX: DBCC CHECKDB doesn’t report metadata inconsistency of invalid filegroups in its summary in SQL Server 2014 and SQL Server 2012

SQL Server 2012 SP3 Cumulative Update 5 (Build 11.0.6544), 20 total public hot fixes

FIX: Assertion failures occur when you query the database-state information in SQL Server 2012

CPU usage increases significantly when you execute queries that contain CHANGETABLE functions in SQL Server 2012 Service Pack 3

FIX: Queries that run against secondary databases always get recompiled in SQL Server

SQL Server crashes because of an access violation error that occurs while it reads data from an event file target

SQL Server 2014 or 2012 doesn’t start after you configure the tempdb database to use a very small log file

Unexpected growth of tempdb data files when using SQL Server Service Broker

“The log backup chain is broken” error when the log backup process fails in SQL Server

Operating system error 32 when you restore a database in SQL Server 2014 or 2016

SQL Server 2012 SP3 Cumulative Update 6 (Build 11.0.6567), 11 total public hot fixes

FIX: DBCC CHECKFILEGROUP reports false inconsistency error 5283 on a database that contains a partitioned table in SQL Server

Calculation using two measure time values in iterations returns negative values in SQL Server 2012, 2014, or 2016

FIX: TDE encrypted Databases go in suspect state during the recovery phase when you restart SQL Server 2012

FIX: Automatic failover doesn’t occur after database mirroring stops unexpectedly

FIX: Incorrect full-text keys are recorded for the rows that aren’t indexed correctly by a full-text index in SQL Server 2012

FIX: Rebuilding a nonclustered index to add new columns by using CREATE INDEX together with the DROP_EXISTING=ON and ONLINE=ON clauses causes blocking

FIX: Error 3456 “Could not redo log record” occurs, causing replicas to be suspended or repeated behavior in SQL Server

SQL Server 2012 SP3 Cumulative Update 7 (Build 11.0.6579), 11 total public hot fixes

FIX: An Always On secondary replica goes into a disconnecting state

FIX: The Target Recovery Time of a database set to a nonzero value causes an assertion and a lease timeout in SQL Server 2014

“A digitally signed driver is required” warning when you install SQL Server packages in Windows Server 2016 and Windows 10

FIX: On failover, the new secondary replica stops accepting transaction log records until the instance is restarted in SQL Server

FIX: Assert memory dump on a mirror server in SQL Server 2012

FIX: Changing the data type and then updating the table with more than 4,000 records causes database corruption

 

SQL Server 2012 SP3 Cumulative Update 8 (Build 11.0.6594), 17 total public hot fixes

FIX: DMV sys.dm_hadr_availability_group_states displays “NOT_HEALTHY” in synchronization_health_desc column on secondary replicas in SQL Server 2012

FIX: Failed assertion and many access violation dump files after the sp_replcmds stored procedure is canceled in SQL Server 2012

FIX: Bad query plan created on secondary replicas after statistics updated via FULLSCAN option on primary replica in SQL Server 2012

FIX: A memory leak in SQLWEP causes the host process Wmiprvse.exe to crash in SQL Server 2012

Update improves handling of documents too large for Full-Text Search indexing in SQL Server

Update reduces the execution frequency of the sp_MSsubscription_cleanup stored procedure in SQL Server 2012

FIX: Error 5262 when you execute DBCC CHECKDB on the primary replica in SQL Server 2012, 2014 or 2016

SQL Server 2012 SP3 Cumulative Update 9 (Build 11.0.6598), 10 total public hot fixes

FIX: “The custom resolver for this article requires OLEAUT32.DLL with a minimum version of 2.40.4276” error with merge publication in SQL Server

FIX: Can’t grant permissions to another user to log in to an availability group after the owner is removed in SQL Server 2012 or 2014

FIX: Access violation when a stored procedure is dropped before you execute END TRY section in SQL Server 2012 or 2016

FIX: A REDO thread is not available in the secondary replica after an availability database is dropped in SQL Server 2012

FIX: A stored procedure may fail after an automatic failover occurs on a mirrored database in SQL Server 2012

 

SQL Server 2012 SP3 Cumulative Update 10 (Build 11.0.6607), 5 total public hot fixes

FIX: Access violation occurs when you update compressed data in SQL Server 2012 or 2014

FIX: Timeout when you back up a large database to URL in SQL Server 2014

Update adds the “CLR strict security” feature to SQL Server 2016

FIX: Change Data Capture stops working after a recent cumulative update for SQL Server is installed

 

Once again, the idea here is to give you a lot of concrete reasons to want to stay current with the latest SQL Server 2012 SP and CU, by pointing out some of the more valuable fixes in each CU in the Service Pack 3 branch.  If my opinion does not sway everyone, this relatively new Microsoft KB article might be more convincing:

Announcing updates to the SQL Server Incremental Servicing Model (ISM)

Another very useful resource is this Microsoft KB article:

Recommended updates and configuration options for SQL Server 2012 and SQL Server 2014 used with high-performance workloads

Happily, Microsoft has been updating this KB article with new information, so you might want to read it again, if you have not done so already.

The post Performance and Stability Related Fixes in Post-SQL Server 2012 SP3 Builds appeared first on Glenn Berry.

Microsoft also released SQL Server 2012 Service Pack 2 CU12, which is Build 11.0.5649. There are 8 hotfixes in the public fix list.

As you may be aware, Microsoft has changed their official stance about proactively installing Cumulative Updates, as explained in this post:

Announcing updates to the SQL Server Incremental Servicing Model (ISM)

This means that you should make a greater effort to try to stay as current as possible on Cumulative Updates, despite the extra effort that requires.

If you are still on the SQL Server 2012 RTM or SP1 branches, you are on an “unsupported service pack”, which is not a good place to be, for a number of reasons.

The post SQL Server 2012 Service Pack 3 CU3 Available appeared first on Glenn Berry.

If you are still on the SQL Server 2012 SP1 branch, then you want to be on SP1 CU16. But really, you should be on the SP2 branch as soon as possible, since the SP1 branch is no longer a supported branch. Actually, it you are still on the SP1 branch, you should jump to the SP3 branch, and skip SP2.

Table 1 shows the SQL Server 2012 SP2 CU builds that have been released so far.

Table 1: SQL Server 2012 SP2 CU Builds

You can follow the KB article link below to see all of the CU builds for the SQL Server 2012 Service Pack 2 branch.

SQL Server 2012 SP2 Build Versions

Like I did for the SQL Server 2012 SP1 branch, I decided to scan the hotfix list for all of the Cumulative Updates in the SP2 branch, looking for performance and general reliability-related fixes for the SQL Server Database Engine. I came up with the list below, but this listing is completely arbitrary on my part. You may come up with a completely different list, based on what specific SQL Server 2012 features you are using.

Here are the fixes in the Service Pack 2 branch:

SQL Server 2012 SP2 Cumulative Update 1 (Build 11.0.5532), 43 total public hot fixes

FIX: Intense query compilation workload does not scale with growing number of cores on NUMA hardware and results in CPU saturation in SQL Server

FIX: Assertion failure when you execute a query specifying TOP N and ORDER BY in SQL Server

FIX: Poor cardinality estimation when the ascending key column is branded as stationary in SQL Server

FIX: Poor performance on I/O when you execute select into temporary table operation in SQL Server 2012

FIX: Parallel deadlock or self-deadlock occurs when you run a query that results in parallelism in SQL Server 2012

FIX: Data corruption occurs in clustered index when you run online index rebuild in SQL Server 2012 or SQL Server 2014

 

SQL Server 2012 SP2 Cumulative Update 2 (Build 11.0.5548), 43 total public hot fixes

FIX: SQL Cache Memory decreases and CPU usage increases when you rebuild an index for a table in SQL Server

FIX: Incorrect result when you execute a query that uses WITH RECOMPILE option in SQL Server 2012

FIX: Memory leak occurs when you start and stop an XEvent session repeatedly in SQL Server 2012

FIX: Cannot reclaim unused space by using shrink operation in the table that contains a LOB column in SQL Server

FIX: Undetected deadlock occurs when you use a sequence object in SQL Server 2012

FIX: Performance improvement for SQL Server Spatial data access in SQL Server 2012

FIX: A severe error occurs when you run a query that uses CTEs against the partitioned tables in SQL Server 2012

FIX: UPDATE STATISTICS performs incorrect sampling and processing for a table with columnstore index in SQL Server 2012

 

SQL Server 2012 SP2 Cumulative Update 3 (Build 11.0.5556), 32 total public hot fixes

FIX: Poor performance for cdc.fn_cdc_get_net_changes_<capture_instance> in SQL Server 2012 SP2

FIX: “Non-yielding Scheduler” condition occurs when you run a complex query in SQL Server 2012

FIX: INSERT performance decreases in merge replication that uses precomputed partitions in SQL Server 2012

FIX: Error when you execute statistics update on a table that has sql_variant data type in SQL Server 2012

FIX: Large chain of blocking occurs when you use merge replication in SQL Server 2012

 

SQL Server 2012 SP2 Cumulative Update 4 (Build 11.0.5569), 36 total public hot fixes

FIX: High CPU consumption when you use spatial data type and associated methods in SQL Server 2012 or SQL Server 2014

FIX: Sequence object generates duplicate sequence values when SQL Server 2012 is under memory pressure

FIX: SQL Server is in script upgrade mode for a long time after you apply a SQL Server hotfix or security update

FIX: DBCC CHECKDB and DBCC CHECKTABLE take longer to run when SQL CLR UDTs are involved in SQL Server 2012

 

SQL Server 2012 SP2 Cumulative Update 5 (Build 11.0.5582), 27 total public hot fixes

FIX: SOS_CACHESTORE spinlock contention on system table rowset cache causes high CPU usage in SQL Server 2012 or 2014

FIX: SOS_CACHESTORE spinlock contention on ad hoc SQL Server plan cache causes high CPU usage in SQL Server 2012 or 2014

FIX: Memory leak in USERSTORE_SCHEMAMGR and CPU spikes occur when you use temp table in SQL Server 2012

FIX: AlwaysOn availability groups are reported as NOT SYNCHRONIZING

FIX: Complex parallel query does not respond in SQL Server 2012

FIX: Performance issue occurs when you use sqlncli11.dll ODBC driver to access SQL Server in an application

FIX: SQL Server 2012 shuts down unexpectedly when you run DBCC CHECKDB and the rollback recovery on the snapshot fails

SQL Server 2012 SP2 Cumulative Update 6 (Build 11.0.5592), 23 total public hot fixes

FIX: Corruption occurs on the page of secondary replica when you change the secondary replica to unreadable

FIX: SQL Server takes long time to open database after recovery to add or remove a data file in SQL Server 2014 or SQL Server 2012

FIX: Access violation when a missing task for a background clear operation tries to delete a missing index entry

SQL Server 2012 SP2 Cumulative Update 7 (Build 11.0.5623), 32 total public hot fixes

FIX: The change table is ordered incorrectly for updated rows after you enable change data capture for a Microsoft SQL Server 2012 database

FIX: Hash or merge join hints may be ignored when you execute a query in SQL Server 2012

FIX: “Unable to create restore plan due to break in the LSN chain” error when you restore differential backup in SSMS

FIX: Indexed view returns incorrect result after insert or delete operation on the base table in SQL Server 2012

FIX: Schema lock occurs on a table with large data when you delete lots of rows from it in SQL Server 2012

FIX: Error messages are logged when you execute a non-cacheable auto-parameterized query in SQL Server 2012

FIX: Incorrect results occur in a rare scenario when you run a query that contains a nested loop join and performance spool in its inner side in SQL Server 2012

FIX: A deadlock occurs when you execute the sp_estimate_data_compression_savings stored procedure in SQL Server 2012

FIX: Out of memory error when the virtual address space of the SQL Server process is very low on available memory

FIX: The Resource database is missing after you install updates or service packs for instances of SQL Server 2012 one after another and then restart the server

FIX: Incorrect result when you execute a full-text query with parallel execution plan in SQL Server 2012

FIX: Contention occurs when you execute many ad-hoc queries in SQL Server 2012

FIX: You receive incorrect results from the CHANGETABLE() function when snapshot isolation for a SQL Server 2012 database

FIX: Cannot enable “change data capture” on a table that uses a unique index with more than one included column in SQL Server 2012 SP2

SQL Server 2012 SP2 Cumulative Update 8 (Build 11.0.5634), 23 total public hot fixes

FIX: A stalled dispatcher system dump forces a failover and service outage in SQL Server 2014 or SQL Server 2012

FIX: Error 602 when you run a stored procedure repeatedly in SQL Server 2012

FIX: Data spill occurs when you sort large amount of data in SQL Server 2012

FIX: FileStream Share Access fails when you use AlwaysOn Availability Groups feature in SQL Server 2012

FIX: Rare incorrect result occurs when you run parallel query in SQL Server 2012

FIX: It takes a longer time than earlier versions of SQL Server when you run DBCC CHECKDB in SQL Server 2012

FIX: Access violation occurs in AlwaysOn availability groups scenarios in SQL Server 2012

FIX: Access violations when you use the FileTable feature in SQL Server 2012

FIX: Out of memory error when the virtual address space of the SQL Server process is very low on available memory

FIX: SQLDiag fails with function 87 error in SQL AlwaysOn scenario where the server name has 15 characters

FIX: Scheduler deadlock on primary replica when you remove a replica from an AlwaysOn availability group in SQL Server 2012

FIX: Error 9002 and error 3052 when you try to add or back up log file in SQL Server 2012

 

SQL Server 2012 SP2 Cumulative Update 9 (Build 11.0.5641), 13 total public hot fixes

FIX: The SQL Server service performs more I/O operations on the mirror server than on the principal server

FIX: Backup operation fails in a SQL Server database after you enable change tracking

FIX: Performance decrease when an application that has connection pooling frequently connects or disconnects in SQL Server

 

SQL Server 2012 SP2 Cumulative Update 10 (Build 11.0.5644), 12 total public hot fixes

FIX: You cannot use the Transport Layer Security protocol version 1.2 to connect to a server that is running SQL Server 2014 or SQL Server 2012

FIX: You receive errors when you execute a query that uses tempdb in SQL Server

FIX: The Log Reader Agent stops intermittently and an Access Violation occurs in SQL Server 2012

 

SQL Server 2012 SP2 Cumulative Update 11 (Build 11.0.5646), 15 total public hot fixes

FIX: Numeric overflow when you run a query that spills more than 65,535 extents to tempdb in SQL Server 2014 or 2012

FIX: “A severe error occurred on the current command” error occurs when a Table-Valued User-Defined function is referred to by using a synonym

FIX: An assertion failure occurs on the secondary replica when you use the AlwaysOn Availability Groups feature in SQL Server 2012

FIX: SQL Server stops responding when you back up the certificate that is used to encrypt the database encryption key in SQL Server 2012 or SQL Server 2014

FIX: “Cannot resolve the collation conflict” error occurs when you apply a snapshot to the subscriber database in SQL Server

FIX: Slow performance occurs when you query numeric data types from an Oracle database

FIX: An access violation occurs when you execute a stored procedure that uses a cursor on a table variable in SQL Server

FIX: XA transactions are not cleaned when you exit a Java application in an instance of SQL Server

 

SQL Server 2012 SP2 Cumulative Update 12 (Build 11.0.5649), 8 total public hot fixes

FIX: Memory leak occurs on the AlwaysOn secondary replica when change tracking is enabled in SQL Server 2012

FIX: Error when you use the replication feature in SQL Server 2014 or SQL Server 2012

FIX: “Non-yielding Scheduler” error when versioning cleanup task runs on a SQL Server AlwaysOn secondary replica

Once again, the idea here is to give you a lot of concrete reasons to want to stay current with the latest SQL Server 2012 SP and CU, by pointing out some of the more valuable fixes in each CU in the Service Pack 2 branch.  If my opinion does not sway everyone, this relatively new Microsoft KB article might be more convincing:

Announcing updates to the SQL Server Incremental Servicing Model (ISM)

Another very useful resource is this Microsoft KB article:

Recommended updates and configuration options for SQL Server 2012 and SQL Server 2014 used with high-performance workloads

Happily, Microsoft has been updating this KB article with new information, so you might want to read it again, if you have not done so already.

The post Performance and Stability Related Fixes in Post-SQL Server 2012 SP2 Builds appeared first on Glenn Berry.

If you are still on the SQL Server 2012 SP1 branch, then you want to be on SP1 CU16.

Table 1 shows the SP1 CU builds that have been released so far.

Table 1: SQL Server 2012 SP1 CU Builds

You can follow the KB article link below to see all of the CU builds for the SQL Server 2012 Service Pack 1 branch.

The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released

Like I did in my previous post, I decided to scan the hotfix list for all of the Cumulative Updates in the SP1 branch, looking for performance and general reliability-related fixes for the SQL Server Database Engine. I came up with the list below, but this listing is completely arbitrary on my part. You may come up with a completely different list, based on what SQL Server 2012 features you are using.

Here are the fixes in the RTM branch, before Service Pack 1 was released (you will get these when you install SP1):

SQL Server 2012 RTM Cumulative Update 1  (Build 11.0.2316) , 65 total public hot fixes

FIX: Low CPU spikes at a set interval even without user activity in SQL Server 2008 R2 or in SQL Server 2012

FIX: Slow performance when an AFTER trigger runs on a partitioned table in SQL Server 2008 R2 or in SQL Server 2012

FIX: It takes a long time to restore a database in SQL Server 2008 R2 or in SQL Server 2008 or in SQL 2012

FIX: Poor performance when you run a query that contains correlated AND predicates in SQL Server 2008 or in SQL Server 2008 R2 or in SQL Server 2012

FIX: Slow performance occurs in SQL Server 2008 R2 or in SQL Server 2012 if high CPU usage is observed with contention over the QUERY_EXEC_STATS spinlock

FIX: Out-of-memory error when you run SQL Server 2012 on a computer that uses NUMA

SQL Server 2012 RTM Cumulative Update 2  (Build 11.0.2325) , 37 total public hot fixes

FIX: An access violation occurs intermittently when you run a query against a table that has a columnstore index in SQL Server 2012

Here are the fixes in the Service Pack 1 branch:

SQL Server 2012 SP1 Cumulative Update 1 (Build 11.0.3321), 44 total public hot fixes

FIX: “out of memory” error when you use ODBC with SQL Server 2012, SQL Server 2008 R2 or SQL Server 2008

FIX: Performance of a SELECT statement that contains a LIKE operator and an ESCAPE clause is low in SQL Server 2008 R2 or in SQL Server 2012

FIX: SQL Server 2012, SQL Server 2008 R2 or SQL Server 2008 stops responding and a “Non-yielding Scheduler” error is logged

FIX: Slow performance or deadlock when you restore a database and execute statements at the same time in SQL Server 2012

FIX: Worker threads do not wake up immediately when multiple I/O-intensive tasks are running at the same in SQL Server 2012

FIX: “Process appears to be non-yielding on Scheduler ” error message when you run a query in SQL Server 2012

SQL Server 2012 SP1 Cumulative Update 2 (Build 11.0.3339), 50 total public hot fixes

A database transaction log continues to grow after you upgrade to SQL Server 2012, SQL Server 2008 R2 SP1, SQL Server 2008 SP2 or SQL Server 2008 SP3

FIX: The size of a database file is not reduced when you use the DBCC SHRINKFILE command in SQL Server 2008 R2 or in SQL Server 2012

FIX: High CPU usage when you query a binary large object column by using the NOLOCK hint in SQL Server 2008 R2 or in SQL Server 2012

FIX: Large queries that modify data run slower than expected when many locks accumulate in a SQL Server 2008 R2 or in SQL Server 2012

FIX: A transaction log restore operation takes longer than expected and a 3402 error occurs if a database file is removed in SQL Server 2008 R2 or in SQL Server 2012

SQL Server 2012 experiences out-of-memory errors

FIX: Deadlocks occur when you execute a stored procedure to alter a temporary table if lock partitioning is enabled in SQL Server 2008 R2 or in SQL Server 2012

FIX: Memory leak if you enable the AUTO_UPDATE_STATISTICS_ASYNC statistics option in SQL Server 2008, in SQL Server 2012 or in SQL Server 2008 R2

FIX: A “non-yielding” error occurs on a server for Service Broker Message Forwarding in SQL Server 2008 R2 or in SQL Server 2012

FIX: Error 17883 when you run a query on a server that has many CPUs and a large amount of memory in SQL Server 2012

SQL Server 2012 SP1 Cumulative Update 3 (Build 11.0.3349), 38 total public hot fixes

FIX: Access violation when you run a query that contains many constant values in an IN clause in SQL Server 2008 or in SQL Server 2012

FIX: Memory leak when you run queries against a temporary table in a nested stored procedure in SQL Server 2012

FIX: Poor performance in SQL Server 2012 when you run a SQL Server trace

FIX: You experience poor performance when you run a query against an RCSI-enabled table in SQL Server 2012

FIX: CPU spike when there is no load on a server after you install SQL Server 2012 on the server

SQL Server 2012 experiences performance issues in NUMA environments

SQL Server 2012 SP1 Cumulative Update 4 (Build 11.0.3368), 38 total public hot fixes

FIX: Out-of-memory errors related to a memory clerk in SQL Server 2012

FIX: Out of memory error when you build a columnstore index on partitioned tables in SQL Server 2012

Update that improves the Service Broker when you send messages to remote servers in SQL Server 2012 is available

An update is available for SQL Server 2012 Memory Management

FIX: “Non-yielding Scheduler” error occurs when you insert a row in SQL Server 2012

FIX: You may experience performance issues in SQL Server 2012

SQL Server 2012 SP1 Cumulative Update 5 (Build 11.0.3373), 27 total public hot fixes

FIX: Poor performance when you run a query that uses the LIKE operator in the WHERE clause in SQL Server 2008 R2

FIX: Non-yielding scheduler error when you run a stored procedure that uses a TVP in SQL Server 2012

SQL Server 2012 SP1 Cumulative Update 6 (Build 11.0.3381), 24 total public hot fixes

FIX: Slow performance on SQL Server 2012 linked server when you update the data together with different collation on the remote server

FIX: A memory leak occurs when you enable AlwaysOn Availability Groups or SQL Server failover cluster in Microsoft SQL Server 2012

SQL Server 2012 SP1 Cumulative Update 7 (Build 11.0.3393), 47 total public hotfixes

FIX: Access violation when you trace an RPC event class by using SQL profiler or XEvents in SQL Server 2012

FIX: Nonclustered index corruption may occur when you run a complex UPDATE statement together with a NOLOCK hint against a table in SQL Server 2008, SQL Server 2008 R2 or SQL Server 2012

FIX: The threads are not scheduled evenly in SQL Server 2012 Standard Edition

A memory leak occurs when a SQL Server Native Client OLE DB provider application calls the Prepare method in SQL Server 2012

FIX: “Non-yielding Resource Monitor” when you run a workload that executes concurrent queries in SQL Server 2012

FIX: Function sys.fn_hadr_backup_is_preferred_replica costs almost all the CPU usage in Log Shipping in SQL Server 2012

FIX: Slow performance in SQL Server when you build an index on a spatial data type of a large table in a SQL Server 2012 instance

FIX: Slow performance in SQL Server 2012 when you build an index on a spatial data type of a large table

An access violation occurs when “sys.dm_db_index_physical_stats” is used in an IF EXISTS statement in an SQL query in SQL Server 2012

FIX: Suboptimal execution plan is generated when you run a query in SQL Server 2012

Slow SQL Server performance and a memory leak occurs after you apply Cumulative Update 3 for SQL Server 2012 Service Pack 1

FIX: Slow performance in SQL Server 2012 when you build an index on a spatial data type of a large table

Slow performance or error messages are logged when you have a transactional replication publisher server in SQL Server 2012

FIX: Insufficient system memory error occurs when you try to create an index in a char, varchar, or nvarchar type column in SQL Server 2012

SQL Server 2012 SP1 Cumulative Update 8 (Build 11.0.3401), 32 total public hotfixes

FIX: Data purity corruption in sys.sysbinobjs table in master database when you log on to SQL Server 2008 R2 or SQL Server 2012 by using the SA account and then run DBCC CHECKDB

FIX: Interrupted distributed query may return partial result set without any error in SQL Server 2008 R2 or in SQL Server 2012

FIX: Replication Log Reader Agent fails when you enable CDC and transactional replication for some columns in SQL Server 2008 R2 or SQL Server 2012

FIX: Query that you run against a partitioned table returns incorrect results in SQL Server 2008, SQL Server 2008 R2 or SQL Server 2012

FIX: A small number of rows are sampled in SQL Server 2008 R2 or in SQL Server 2012 when table statistics are updated automatically or together with specified sampling rate

FIX: Access violation may occur when you query sys.dm_server_memory_dumps in SQL Server 2008 R2 or SQL Server 2012

FIX: Replication Queue Reader Agent crashes when you run transactional replication in SQL Server 2008 R2 or SQL Server 2012

FIX: Validation of service accounts takes a long time when you set up SQL Server 2012

FIX: The system function sys.fn_hadr_backup_is_preferred_replica does not work correctly after you have CU7 for SQL Server 2012 SP1 installed

FIX: The query deadlocks when the ALLOW_SNAPSHOT_ISOLATION and READ_COMMITTED_SNAPSHOT are enabled in SQL Server 2012

FIX: The clustered index table may take longer than you expect to be rebuilt when you use the ALTER INDEX REBUILD statement in SQL Server 2008 or SQL Server 2012

SQL Server 2012 SP1 Cumulative Update 9 (Build 11.0.3412), 30 total public hotfixes

FIX: Access violation in SQL Server internal deadlock monitor when you run multiple applications together with Multiple Active Result Sets enabled in SQL Server 2008 R2 or in SQL Server 2012

FIX: Access violation in replication Distribution Agent in SQL Server 2008 R2 or SQL Server 2012 Transactional Replication

FIX: Poor performance when many table-valued parameters are used in SQL Server 2008 R2 or SQL Server 2012

FIX: Merge Agent fails or you experience non-convergence when you use a custom stored procedure conflict resolver in SQL Server 2008 or SQL Server 2008 R2 or SQL Server 2012

FIX: Performance problems occur when database lock activity increases in SQL Server 2012

FIX: Performance problems occur in NUMA environments during foreign page processing in SQL Server 2012

FIX: Operating system version information that is returned from SQL Server 2008 or SQL Server 2008 R2 or SQL Server 2012 is incorrect in Windows 8.1

FIX: Performance decreases after an ALTER INDEX…ONLINE operation is aborted in SQL Server 2012

FIX: Access violation may occur when trigger query joins large dataset in deleted/inserted table and runs in parallel in SQL server 2012

FIX: Database shows “recovery pending” state when you use TDE with EKM provider in SQL Server 2012

FIX: Incorrect usage of built-in FORMAT function brings down SQL Server 2012 Instance

FIX: SQL Server 2012 instance shuts down when you join database as secondary replica during AlwaysOn Availability Groups configuration

FIX: Merge agent fails when you apply snapshot in SQL Server 2012 instance if cross database dependencies are present

FIX: Distribution Agent skips applying sp_MSins_, sp_MSupd_, sp_MSdel_ stored procedures on a Subscriber that is initialized with Backup in SQL Server 2012

FIX: Access violation occurs when you update a table that has an XML calculated column in SQL Server 2012

FIX: SQL Server takes long time to open the databases after the recovery phase when the number of databases or database files or both is large in SQL Server 2012

FIX: Message is not removed from transmission queue even though the ACK is received successfully in an AlwaysOn availability group in SQL Server 2012

FIX: Non-yielding scheduler tries to close the listener for availability group in SQL Server 2012

SQL Server 2012 SP1 Cumulative Update 10 (Build 11.0.3431), 36 total public hotfixes

FIX: Intense query compilation workload does not scale with growing number of cores on NUMA hardware and results in CPU saturation in SQL Server 2012

FIX: Assertion failure when you execute a query specifying TOP N and ORDER BY in SQL Server 2008 R2 or SQL Server 2012

FIX: Access violation occurs when you run CHECKTABLE or CHECKDB against a table that has persisted computed columns in SQL Server 2008 R2 or SQL Server 2012

FIX: Incorrect results when you run queries that contain UNION operator by using parallel query plan in SQL Server 2012

FIX: An access violation occurs when you execute update query on a table that has a DML trigger in SQL Server 2008 R2 or SQL Server 2012

FIX: Access violation when the start offset is larger than the string length in function Substring in SQL Server 2012

FIX: Poor cardinality estimation when the ascending key column is branded as stationary in SQL Server 2012

FIX: Poor performance on I/O when you execute select into temporary table operation in SQL Server 2012

FIX: Parallel deadlock or self-deadlock occurs when you run a query that results in parallelism in SQL Server 2012

SQL Server 2012 SP1 Cumulative Update 11 (Build 11.0.3449), 32 total public hotfixes

FIX: “Cannot insert duplicate key” error occurs in Spool operation when you update a table in SQL Server 2012

FIX: Incorrect result when you execute a query that uses WITH RECOMPILE option in SQL Server 2012

FIX: Memory leak occurs when you start and stop an XEvent session repeatedly in SQL Server 2012

FIX: Cannot reclaim unused space by using shrink operation in the table that contains a LOB column in SQL Server

FIX: Fatal exception when you run a query that contains CLR functions against an indexed view in SQL Server 2012

FIX: Undetected deadlock occurs when you use a sequence object in SQL Server 2012

FIX: Data corruption occurs in clustered index when you run online index rebuild in SQL Server 2012 or SQL Server 2014

FIX: The database sticks in role configuration phase when you perform a manual failover of a mirrored database

FIX: Error when you execute a Transact-SQL query that contains a long case statement in SQL Server 2012

FIX: Error when you insert a record into a FileTable or FILESTREAM in SQL Server 2012

FIX: Log Reader Agent crashes during initialization when you use transactional replication in SQL Server 2012

FIX: Poor performance when you create spatial index on Point data in SQL Server 2012

FIX: Log Reader Agent fails when you upgrade from SQL Server 2008 to SQL Server 2012

FIX: A severe error occurs when you run a query that uses a hash join parallel execution plan in SQL Server 2012

SQL Server 2012 SP1 Cumulative Update 12 (Build 11.0.3470), 14 total public hotfixes

FIX: Error 7105 when you execute UPDATE on sparse column set while ONLINE INDEX REBUILD is running on the same table in SQL Server 2012

SQL Server 2012 SP1 Cumulative Update 13 (Build 11.0.3482), 10 total public hotfixes

FIX: High CPU consumption when you use spatial data type and associated methods in SQL Server 2012

FIX: SQL Server is in script upgrade mode for a long time after you apply a SQL Server hotfix or security update 

SQL Server 2012 SP1 Cumulative Update 14 (Build 11.0.3486), 8 total public hotfixes

FIX: SOS_CACHESTORE spinlock contention on system table rowset cache causes high CPU usage in SQL Server 2012

FIX: SOS_CACHESTORE spinlock contention on ad hoc SQL Server plan cache causes high CPU usage in SQL Server 2012

SQL Server 2012 SP1 Cumulative Update 15 (Build 11.0.3487), 1 total public hotfix

The one hotfix in this CU is not particularly interesting, unless you are using Master Data Services (MDS)

SQL Server 2012 SP1 Cumulative Update 16 (Build 11.0.3492), 4 total public hotfixes

FIX: Corruption occurs on the page of secondary replica when you change the secondary replica to unreadable

FIX: Error 33415 occurs when you restart the SQL Server service or alter database in SQL Server 2012

 

Once again, the idea here is to give you a lot of concrete reasons to want to stay current with the latest SQL Server 2012 SP and CU, by pointing out some of the more valuable fixes in each CU in the Service Pack 1 branch.  If my opinion does not sway everyone, this relatively new Microsoft KB article might be more convincing:

Recommended updates and configuration options for SQL Server 2012 and SQL Server 2014 used with high-performance workloads

Happily, Microsoft has been updating this KB article with new information, so you might want to read it again.

The post Performance and Stability Related Fixes in Post-SQL Server 2012 SP1 Builds appeared first on Glenn Berry.

If you have moved to SQL Server 2008 Service Pack 3 (which is the only currently supported Service Pack for SQL Server 2008) and are patiently waiting for SQL Server 2008 Service Pack 4, you might want to know that Microsoft has announced that there will be a SQL Server 2008 Service Pack 4, that will be available sometime after July 8, 2014. This final Service Pack will include all of the fixes through SQL Server 2008 Service Pack 3 Cumulative Update 17 (and nothing else in addition).

Personally, I think most organizations would be much better off by moving to the latest Service Pack 3 Cumulative Update now, or going to Service Pack 4 when it becomes available. In order to try to convince more people that this is the right thing to do, I have put together this list of what I consider to be the more important hotfixes that have been included in each post-SQL Server 2008 Service Pack 3 Cumulative Update. This list is very Database Engine focused, and completely arbitrary on my part. If you are running SQL Server 2008, you should look at the KB articles for each Cumulative Update (which are linked below), and look for hotfixes that are most relevant to your situation and what SQL Server components that you are using.

Updated to include SQL Server 2008 SP3 CU17. There will not be a SQL Server 2008 SP3 CU18 release, CU17 is the final CU for SQL Server 2008.

SQL Server 2008 SP3 CU1 (10.0.5766)  October 17, 2011 (19 public fixes)

FIX: Certain change tracking functions and DMVs do not work correctly after an automatic database mirroring failover occurs in SQL Server 2008 R2 or in SQL Server 2008

 FIX: Recovery takes longer than expected for a database in a SQL Server 2008 or in a SQL Server 2008 R2 environment

FIX: Errors when client application sends an attention signal to SQL Server 2008 or SQL Server 2008 R2

FIX: Size of a data file that is committed by online page compression is larger than that is committed by offline page compression in SQL Server 2008 or in SQL Server 2008 R2 

 

SQL Server 2008 SP3 CU2 (10.0.5768)  November 21, 2011 (2 public fixes)

FIX: Access violation when you insert a record into a new empty partition in SQL Server 2008

 

SQL Server 2008 SP3 CU3 (10.0.5770)  January 16, 2012 (14 public fixes)

FIX: Access violation when you run a DBCC CHECKDB command against a database that contains a table that has a spatial index in SQL Server 2008 or in SQL Server 2008 R2

FIX: Access violation when a query is compiled or recompiled in SQL Server 2008 or in SQL Server 2008 R2

FIX: It takes a long time to restore a database in SQL Server 2008 R2

 

SQL Server 2008 SP3 CU4 (10.0.5775)  March 19, 2012 (10 public fixes)

FIX: “A time-out occurred while waiting for buffer latch” error when many transactions concurrently update a database in SQL Server 2008 R2 or in SQL Server 2008 if the database uses the snapshot isolation level

FIX: Transaction log backup is created even though the full backup is canceled in SQL Server 2008 or in SQL Server 2008 R2

FIX: ghost_record_count values keep increasing in SQL Server 2008 R2 or in SQL Server 2008

Improvements for the DBCC CHECKDB command may result in faster performance when you use the PHYSICAL_ONLY option

FIX: Backup operation fails on a SQL Server 2008 database after you enable change tracking

 

SQL Server 2008 SP3 CU5 (10.0.5785) May 21, 2012 (4 public hotfixes)

FIX: Slow performance when you restore a database in SQL Server 2008 R2 or in SQL Server 2008 if CDC is enabled

FIX: SQL Server Agent job randomly stops when you schedule the job to run past midnight on specific days in SQL Server 2005, in SQL Server 2008 or in SQL Server 2008 R2

SQL Server 2008 SP3 CU6 (10.0.5788)  July 16, 2012 (14 public hotfixes)

FIX: Errors when a client application sends an attention signal to SQL Server 2008 or SQL Server 2008 R2

FIX: A database page is copied into a database snapshot even though the page is not updated when you perform a read operation in SQL Server 2008 or in SQL Server 2008 R2

FIX: SQL Server 2008 R2 or SQL Server 2008 stops responding and a “Non-yielding Scheduler” error is logged

FIX: Incorrect results are returned when you run a query that uses parallelism in the query execution plan in SQL Server 2008

 

SQL Server 2008 SP3 CU7 (10.0.5794)  September 17, 2012 (11 public hotfixes)

FIX: “out of memory” error when you use ODBC with SQL Server 2012 or SQL Server 2008

FIX: Error is logged when you start SQL Server 2008 or when a client sends a request to the program

FIX: High CPU usage when you execute an UPDATE statement that includes a “WHERE CURRENT OF <cursor>” clause in SQL Server 2008

FIX: Access violation or incorrect result when you insert data into or update a new partition of a partitioned table in SQL Server 2008 R2 or SQL Server 2008

FIX: SQL Server Agent job fails if you set the job schedule type as “Start automatically when SQL Server Agent starts” in SQL Server 2008 SP2, SQL Server 2008 SP3 or SQL Server 2008 R2 SP2

FIX: Poor performance when you run a query that contains correlated AND predicates in SQL Server 2008 or in SQL Server 2008 R2 or in SQL Server 2012 

SQL Server 2008 SP3 CU8 (10.0.5828)  November 19, 2012 (9 public hotfixes)

FIX: Incorrect result is returned when you query an indexed view by using the NOEXPAND hint in SQL Server 2008

Support for the varchar(max), nvarchar(max), and varbinary(max) data types is added in most OLE DB Providers in SQL Server 2008

FIX: “Non-yielding Scheduler” error message when you insert a record that contains large object (LOB) data into a snapshot database in SQL Server 2008

FIX: Memory leak if you enable the AUTO_UPDATE_STATISTICS_ASYNC statistics option in SQL Server 2008

A database transaction log continues to grow after you upgrade to SQL Server 2008 SP2 or SQL Server 2008 SP3

FIX: Large queries that modify data run slower than expected when many locks accumulate in a SQL Server 2008 R2 

 

SQL Server 2008 SP3 CU9 (10.0.5829)  January 21, 2013 (3 public hotfixes)

FIX: Installation or upgrade process fails when you install or upgrade a SQL Server 2008 clustered instance on mount points

FIX: Access violation when you run a query that contains many constant values in an IN clause in SQL Server 2008

SQL Server 2008 SP3 CU10 (10.0.5835)  March 19, 2013 (8 public hotfixes)

FIX: Access violation or incorrect result when you insert data into or update a new partition of a partitioned table in SQL Server 2008 R2 or SQL Server 2008

FIX: Poor performance when table-valued functions use many table variables in SQL Server 2008 R2 or SQL Server 2008

FIX: Access violation when you run DML statements against a table that has partitioned indexes in SQL Server 2008 R2, in SQL Server 2008 or in SQL Server 2012

FIX: Data corruption occurs when LOB data is loaded into a Transact-SQL variable in SQL Server 2008 R2 or in SQL Server 2008

FIX: Index size increases significantly after you rebuild the index online and RCSI is enabled in SQL Server 2008

 

SQL Server 2008 SP3 CU11 (10.0.5841)  May 20, 2013 (6 public hotfixes)

FIX: “Access is denied. [0x80070005]” error message occurs in SSCM when you try to change the password of an account of SQL Server 2008 or SQL Server 2008 R2 in Windows Vista or in a later version of Windows

FIX: SQL Server may freeze when an instance of SQL Server 2012, SQL Server 2008 or SQL Server 2008 R2 is shut down

SQL Server 2008 SP3 CU12 (10.0.5844)  July 15, 2013 (6 public hotfixes)

FIX: A query that runs against a DMV enters an infinite loop in SQL Server 2008 R2, SQL Server 2008 or SQL Server 2012

FIX: SQL Server performance issues in NUMA environments

SQL Server 2008 SP3 CU13 (10.0.5846)  September 16, 2013 (2 public hotfixes)

FIX: Nonclustered index corruption may occur when you run a complex UPDATE statement together with a NOLOCK hint against a table in SQL Server 2008

 

SQL Server 2008 SP3 CU14 (10.0.5848)  November 18, 2013 (6 public hotfixes)

FIX: You receive an incorrect result when you run a query that uses some ranking functions in SQL Server 2008

FIX: Query that you run against a partitioned table returns incorrect results in SQL Server 2008

SQL Server 2008 SP3 CU15 (10.0.5850)  January 20, 2014 (3 public hotfixes)

FIX: “Installer terminated prematurely” error when you install SQL Server 2008 SP3

 

SQL Server 2008 SP3 CU16 (10.0.5852)  March 17, 2014 (2 public hotfixes)

FIX: Operating system version information that is returned from SQL Server 2008 or SQL Server 2008 R2 or SQL Server 2012 is incorrect in Windows 8.1

 

SQL Server 2008 SP3 CU17 (10.0.5861) May 19, 2014 (9 public hotfixes)

FIX: Performance problems occur when database lock activity increases in SQL Server

FIX: Incorrect results when you execute a full-text search with a phrase that contains a hyphen in SQL Server 2008

FIX: Cannot reclaim free up space by using shrink operation in the table that contains a LOB column in SQL Server 2008

The post Performance Related Fixes in Post-SQL Server 2008 Service Pack 3 Builds appeared first on Glenn Berry.

As we get ever closer to the end of mainstream support for both SQL Server 2008 and SQL Server 2008 R2 on July 8, 2014, I am very curious whether Microsoft is planning on releasing a SQL Server 2008 R2 Service Pack 3 or a SQL Server 2008 Service Pack 4 ?

SQL Server 2008 Service Pack 3 was released on October 25, 2011 , and we are now up to SQL Server 2008 SP3 CU15. SQL Server 2008 R2 Service Pack 2 was released on July 26, 2012, and we are now up to SQL Server 2008 R2 SP2 CU10.

I am not looking for release dates, just some word on whether there will be new Service Packs for SQL Server 2008 or SQL Server 2008 R2 before they both fall out of mainstream support this July.  Since many organizations still refuse to install Cumulative Updates, we have the very strong possibility of many customers running some very old builds of SQL Server 2008 and 2008 R2 going forward unless we get a final set of Service Packs for both versions.

As Paul Randal discovered in his recent survey, a very large percentage of SQL Server 2008 and 2008 R2 instances in the wild are already running on “unsupported service packs”, and this situation only got worse when SQL Server 2008 R2 SP1 fell out of support on October 8, 2013. These links show the builds that have been released since the most recent Service Packs for SQL Server 2008 and SQL Server 2008 R2.

The SQL Server 2008 Builds that were released after SQL Server 2008 Service Pack 3 was released

The SQL Server 2008 R2 Builds that were released after SQL Server 2008 R2 Service Pack 2 was released

If you want to try to influence Microsoft in some small way, please take a moment to up vote these Connect items. It only will take a few seconds to click the green arrow!

This is mine, meant to be a generic item:

https://connect.microsoft.com/SQLServer/feedback/details/814658/release-final-service-packs-for-sql-server-2008-and-2008-r2

This one is from Christoph Muthmann, for SQL Server 2008 SP3:

https://connect.microsoft.com/SQLServer/feedback/details/814600/release-service-pack-3-for-sql-server-2008-r2

This one is from Erland Sommarskog, regarding SQL Server 2012 SP2:

https://connect.microsoft.com/SQLServer/feedback/details/814656/release-service-pack-2-for-sql-server-2012

If you have a bit more time, write a comment in any of the Connect items.

The post Final Service Packs for SQL Server 2008 and SQL Server 2008 R2 appeared first on Glenn Berry.