One of the fundamental skills a developer needs is the ability to test their code. Most people don't really do a good job, partly because they don't have a good process and leave testing until the end. Grant Fritchey brings us a new method of unit testing T-SQL stored procedures that can help you build automated tests for your code.
2006-06-20
17,708 reads
Working with outer joins can be tricky since the syntax doesn't always appear to make sense. Grant Fritchey brings us a great example of how this confusion can cause issues if you use the old style syntax.
2006-05-15
15,135 reads
Having a good tool to read your SQL Server transaction log can be a lifesaver, or a job saver. RegGate Software, maker of a number of useful SQL Server utilities has a log reader and Grany Fritchey takes a look at this product and how it might work in your environment.
2005-11-01
10,305 reads
This is one of the very useful features in SQL Server 2000 and if you ever have the need to perform this actiom, you will appreciate the knowledge in this article.
2005-06-15
13,194 reads
SQL Server is an easy to use product in many ways, much better than the other major RDBMSs out there. However it's source control and ease of moving changes from development to production needs some work. Having a solid process is as important as good tools and new author Grant Fritchey brings us his proven method for moving changes through QA into production.
2005-03-22
9,448 reads
I had an excellent group of people in Gothenburg Sweden when I taught there...
By Steve Jones
How can I quickly get a CU patch for a system that’s out of...
Data analysis is all about wrangling massive datasets. To do that efficiently, you need...
Comments posted to this topic are about the item GIT Configuration and Automated Release...
hi a peer of mine recalls an error in an edi app that often...
Hello SSC! First, I would like to thank everyone who has responded to my...
I have created these triggers in SQL Server 2022:
CREATE TRIGGER triggertest_tri_1 ON dbo.triggertest FOR INSERT AS PRINT 'one' GO CREATE TRIGGER triggertest_tri_2 ON dbo.triggertest FOR INSERT AS PRINT 'two' GOI want to be sure that the trigger with "1" runs first. I decide to run this:
EXEC sp_settriggerorder@triggername = 'triggertest_tri_1', @order = 'first'What happens? See possible answers