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.
Waterfall is the practice most destructive to developer productivity? Nonsense, according to Phil Factor. Lack of basic team coordination skills comes much higher in the list.
Steve Jones looks at the idea of cataloging our data sets in order to make it easier for
With the new temporal table feature, SQL Server 2016 internally manages two tables: a base table, which contains the latest data all the time, and a history table, which contains a history of all of the changes. Arshad Ali looks at the new feature, how it works, and how to either create a new table with this feature or enable it for an existing table.
By Zikato
When I'm looking at a query, I bet it's bad if I see... a...
By Steve Jones
This month is a milestone for T-SQL Tuesday. It’s number 200, which doesn’t sound...
The DBA life is fraught with pain. Those battles that we endure are mostly...
Comments posted to this topic are about the item A Quick Second Opinion
Comments posted to this topic are about the item Five Intelligent Query Processing Features...
Comments posted to this topic are about the item Checking the Error Log I
On my SQL Server 2025, I want to search the error log from my T-SQL code for potential issues and then inform an administrator. What is the current way to easily query the error log?
See possible answers