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

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.

Blogs

5 Starter Projects for Your AI and Data Engineering Portfolio

By

Reading tutorials is fine. Shipping something is better. If you are trying to break...

The Book of Redgate: Taking Breaks

By

We work hard at Redgate, though with a good work-life balance. One interesting observation...

Database AI Agents: The Read-Only Rule

By

Fourth in a series on Ai and databases. What Read-Only Advisory Actually Means A...

Read the latest Blogs

Forums

Liability for AI Errors

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Liability for AI Errors

Running a Parameter-Sensitive Stored Procedure on a Secondary Replica

By abdalah.mehdoini

Hello , I would like to run a stored procedure on a secondary replica...

Pro SQL Server Internals

By Site Owners

Comments posted to this topic are about the item Pro SQL Server Internals

Visit the forum

Question of the Day

Running SQLCMD II

I run this command to start SQLCMD:

sqlcmd -S localhost -E -c "proceed"
At the prompt, I type this (the 1> and 2> are prompts):
1> select @@version
2> go
What happens?

See possible answers