Error Handling

External Article

ERROR_PROCEDURE Does Not Return a Schema Name

  • Article

"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

Handling SQL Server Errors

  • Article

This article covers the basics of TRY CATCH error handling in T-SQL introduced in SQL Server 2005. It includes the usage of common functions to return information about the error and using the TRY CATCH block in stored procedures and transactions.

2010-05-17

5,003 reads

Blogs

T-SQL Tuesday #192: SQL Server 2025 Backup Changes

By

I hosted this month, but I decided to put my own entry in as...

Why Databases Still Fascinate Me

By

I get asked a lot about why or how I began working with databases...

Monday Monitor Tips: ServiceNow Integration

By

Earlier this year I visited a customer that was using the Redgate Monitor webhook...

Read the latest Blogs

Forums

Member was not found in the cube when the string

By giles.clapham

Hey, I've not done a cube for many years but I find myself supporting...

Implementing PostgreSQL with Python for Real-Time Logging and Monitoring

By sabyda

Comments posted to this topic are about the item Implementing PostgreSQL with Python for...

Identify a Slipstream Installation

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Identify a Slipstream Installation

Visit the forum

Question of the Day

Identify a Slipstream Installation

I get a new SQL Server instance from my build team. How can I tell if the instance was installed using a slipstream installation later?

See possible answers