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 Steve Jones
It’s Prime Day. A few of my recommendations, since I want to do some...
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
If you’ve been watching AI roll through the data community and thinking, “this seems...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Comments posted to this topic are about the item Concurrency and Baseline Control: Level...
Comments posted to this topic are about the item Spending Time in the Office
I have this code on SQL Server 2022. What happens when it runs all at once?
DROP TABLE IF EXISTS dbo.Commission GO CREATE TABLE dbo.Commission (id INT NOT NULL IDENTITY(1,1) CONSTRAINT CommissionPK PRIMARY KEY , salesperson VARCHAR(20) , commission VARCHAR(20) ) GO INSERT dbo.Commission ( salesperson, commission) VALUES ( 'Brian', 12 ), ( 'Brian', 'None' ) GOSee possible answers