Additional Articles


Technical 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…"

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

You rated this post out of 5. Change rating

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

A Pursuit of Lifelong Learning

By

The following came across my YouTube feed today. It’s an interview with General James...

Advice I Like: Time and Focus

By

“You don’t need more time because you already have all the time that you...

Book Review: Microsoft 365 Copilot and Agent Administration Fundamentals

By

I don’t currently manage Microsoft 365 Copilot in an enterprise environment, but it is...

Read the latest Blogs

Forums

What Did Healthy Look Like?

By Laura Copeland

Comments posted to this topic are about the item What Did Healthy Look Like?

DML Trigger Types

By Steve Jones - SSC Editor

Comments posted to this topic are about the item DML Trigger Types

PostgreSQL in action with Opensearch

By sabyda

Comments posted to this topic are about the item PostgreSQL in action with Opensearch

Visit the forum

Question of the Day

DML Trigger Types

How many types of DML triggers are there?

See possible answers