Additional Articles


External Article

ERROR_PROCEDURE Does Not Return a Schema Name

"A recent blog entry I read reminded me again that I wanted to rant about an issue in SQL Server for quite some time now. SQL Server 2005 introduced the separation between user and schema. Though schemata already existed before SQL Server 2005, they really became usable with this version, imho. At the same time TRY...CATCH was a new way for structured error handling introduced. And so it finally became possible…"

2011-01-26

2,799 reads

External Article

BIT of a Problem

The BIT data type is an awkward fit for a SQL database. It doesn't have just two values, and it can do unexpected things in expressions. What is worse, it is a flag rather than a predicate, and so its overuse, along with bit masks, is a prime candidate for being listed as a 'SQL Code Smell'. Joe Celko makes the case.

2011-01-24

3,676 reads

External Article

LINQ Lycanthropy: Transformations into LINQ

LINQ is one of the few technologies that you can start to use without a lot of preliminary learning. Also, it lends itself to learning by trying out examples. With Michael Sorens' help, you can watch as your conventional C# code changes to ravenous LINQ before your very eyes.

2011-01-21

3,948 reads

External Article

SQL Server Unit Testing with tSQLt

When one considers the amount of time and effort that Unit Testing consumes for the Database Developer, is surprising how few good SQL Server Test frameworks are around. tSQLt , which is open source and free to use, is one of the frameworks that provide a simple way to populate a table with test data as part of the unit test, and check the results with what should be expected. Sebastian Meine and Dennis Lloyd, who created tSQLt, explain

2011-01-19

3,084 reads

External Article

Making a more reliable and flexible sp_MSforeachdb

While the system procedure sp_MSforeachdb is neither documented nor officially supported, most SQL Server professionals have used it at one time or another. This is typically for ad hoc maintenance tasks, but many people (myself included) have used this type of looping activity in permanent routines. Sadly, I have discovered instances where, under heavy load and/or with a large number of databases, the procedure can actually skip multiple catalogs with no error or warning message. Since this situation is not easily reproducible, and since Microsoft typically has no interest in fixing unsupported objects, this may be happening in your environment right now

2011-01-18

3,580 reads

Blogs

Resetting on the AI hype train

By

There's a great article from MIT Technology Review about resetting on the hype of...

A New Word: Etherness

By

etherness – n. the wistful feeling of looking around a gathering of loved ones,...

Vibe Coding a Login Tracking System

By

A customer was asking about tracking logins and logouts in Redgate Monitor. We don’t...

Read the latest Blogs

Forums

The Microsoft SQL Year in Review

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Microsoft SQL Year in...

T-SQL in SQL Server 2025: The || Operator

By Steve Jones - SSC Editor

Comments posted to this topic are about the item T-SQL in SQL Server 2025:...

Your Value from a Conference

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Your Value from a Conference

Visit the forum

Question of the Day

UNISTR Basics

What does this code return in SQL Server 2025+? (assume the database has an appropriate collation)

SELECT UNISTR('Hello 4E16754C') AS 'A Classic';
A:   B:  

See possible answers