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.

Build a POC

by Steve Jones

SQLServerCentral.com

Editorial

One way to tackle a new technology is with a proof of concept.

Changes to a Writable Partition May Fail Unexpectedly

by Additional Articles

SQLPerformance.com

Partitioning

Paul White shows how an update may fail when a partition has some data on a read-only filegroup, and explains several workarounds.

A Welcoming Conference

by Steve Jones

SQLServerCentral.com

Editorial

It's almost time for SQLBits, Steve's favorite conference.

How to fix SQL Server deadlocks with monitoring

by Additional Articles

Redgate

SQL Monitor

Learn about deadlocks and how you might better troubleshoot the issues involved.

The 2015/2016 Simple-Talk Awards: Winners Announced

by Additional Articles

SimpleTalk

Simple-Talk

The 2015/16 Simple-Talk Awards have concluded, the votes have been counted and recounted, and the winners have now been announced.

Hunting in Packs

by Phil Factor

SQLServerCentral.com

Editorial

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.

The Data Dewey Decimal System

by Steve Jones

SQLServerCentral.com

Editorial

Steve Jones looks at the idea of cataloging our data sets in order to make it easier for

Getting Started with Temporal Table in SQL Server 2016 – Part 1

by Additional Articles

Database Journal

Temporal Tables

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.