Skip to content

What comes after a baker’s dozen of cumulative updates? CU14, that’s what, and it includes a really long list of fixes. I’m only gonna hit the highlights here: Non-yielding scheduler when there is a “heavy use” of prepared statements Columnstore index build times out after 25 seconds sys.fn_hadr_backup_is_preferred_replica returns true for multiple replicas when there…

The post Announcing SQL Server 2017 Cumulative Update 14 appeared first on SQLServerUpdates.com .

Read More

I’ll always remember where I was on Tuesday, March 19th, 2019 at 6:55PM. I was sitting in the Seattle airport, waiting to board the last leg of my flights home to San Diego. I happened to check my phone, and… It was here. The update we’d waited for for YEARS had finally landed. Yes, ladies…

The post Announcing SQL Server 2016 SP2 CU6: The Update You’ll Remember Forever appeared first on SQLServerUpdates.com .

Read More

I’m gonna be honest, dear reader: there isn’t a lot of meat on these bones (and that’s a great thing, meaning this product is pretty darned stable.) In fact, there are so few that I can list ALL of them in one post, which is fairly unusual: High CPU usage when a large index is…

The post Announcing SQL Server 2014 SP3 CU2 and SP2 CU16 appeared first on SQLServerUpdates.com .

Read More

Microsoft went on holiday vacation, and they came back with a vengeance. There are one heck of a lot of fixes inside SP2 CU5 and SP1 CU13, including: Access violation when you compile a query Access violations and unhandled exceptions with Always On Availability Groups automatic seeding Dynamic Data Masking doesn’t when there’s a cursor…

The post Announcing SQL Server 2016 SP2 CU5, SP1 CU13 appeared first on SQLServerUpdates.com .

Read More

For databases with single log files, the sp_attach_single_file_db stored procedure will work to attach the DB file and create a new single log file. The syntax is as follows: sp_attach_single_file_db [ @dbname= ] ‘dbname’, [ @physname= ] ‘physical_name’ Where there are multiple log file, the above stored proc won’t work. You can still attach this…

Read More

For those of you unfortunate enough to still be running legacy applications from the cretaceous period, the below SQL 2000 Health Check script might help to sooth that itch a little… <span style=”font-size: 85%;”>create procedure sp_emailDailyHealthCheckCSV @charfrom varchar(50), @charsubject varchar(100), @charemailserver varchar(15), @intresults int OUTPUT AS /****************************************************************** * * DAILY HEALTH CHECK SCRIPT – SQL Server…

Read More

There’s a lot that can be said about what the correct ways are to split up a database over multiple disks, and on a windows system the advantages are fairly self evident when you consider that Windows only allows four (4) concurrent read / write operations per LUN. This article isn’t going to cover the…

Read More

Removing log shipping via SQL Management studio is as simple as un-selecting the log shipping check box under the database properties, however every now and again somebody restores a database over a DB that was configured for log shipping, consequently breaking everything and now requires a little manual intervention in order to get things cleaned…

Read More

SQL Server Dynamic Management Views (DMVs) are a powerful feature set introduced with SQL 2005 that allows you to pull back the curtain on SQL Server and easily review some of the inner workings of your database server (such as performance issues etc) without first having to collect a full SQL trace then interrogating that…

Read More

Identifying SQL Server performance bottlenecks can be quite a complicated process. With so many counters required to assess where potential bottlenecks exist – both within SQL Server, it’s databases and the underlying operating system, disk subsystem etc. Below we’ve listed just a handful of SQL Server Perfmon counters which you can use to assess some…

Read More