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.
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.
By Vinay Thakur
Following up on my Part 1 baseline, the journey from 2017 onward changed how...
By Brian Kelley
In cryptography, the RSA and ECC algorithms which we use primarily for asymmetric cryptography...
By Steve Jones
In today’s world, this might mean something different, but in 2010, we had this...
Comments posted to this topic are about the item Dancing Robot Goes Rogue
Hi , i installed winscp on my pc, added it to GAC thru vs...
Comments posted to this topic are about the item Identities and Sequences II
In thinking about the differences between the identity property and a sequence object, which of these two guarantees that there are consecutive numbers (according to the increment) inserted in a single table?
See possible answers