Sometimes, in the quest for raw SQL performance, you are forced to sacrifice legibility and maintainability of your code, unless you then document your code lavishly. Phil Factor's SQL Speed Phreak challenge produced some memorable code, but can SQL features introduced since then help to produce code that performs as well and is also easy to understand? Kathi Kellenberger investigates.
This new chapter will show you how to work with the SSIS Data Mining Query Transformation Task
Code coverage is a practice that goes hand in hand with automated testing, reporting the percentage of your code that has been exercised during a test run. Ed Elliott and Redgate have partnered to make a code coverage tool available for SQL Server, both free and open source. SQL Cover measures the coverage of your SQL Server stored procedures and functions. It has built-in support for the popular tSQLt unit testing framework, but can also be used alongside any automated testing framework of your choosing. Find out more in this blog post.
Paul White shows how an update may fail when a partition has some data on a read-only filegroup, and explains several workarounds.
Learn about deadlocks and how you might better troubleshoot the issues involved.
The 2015/16 Simple-Talk Awards have concluded, the votes have been counted and recounted, and the winners have now been announced.
Slow-running queries can degrade your Redshift cluster’s performance and lead to increased costs. Identifying...
By gbargsley
If you've been here before, you know this blog is usually about SQL Server,...
I’ve been doing storage load tests for SQL Server for a long time, both...
Comments posted to this topic are about the item How Long is a Long...
Comments posted to this topic are about the item Half of All Engineers
I have an app that has an address field on the customer and the...
In SQL Server 2025, a long I/O is recorded in the error log with message 833. How long much an I/O request be outstanding before this message is written to the log?
See possible answers