Error Handling

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

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

You rated this post out of 5. Change rating

2011-01-26

2,799 reads

Blogs

A New Word: Semaphorism

By

semaphorism – n. a conversational hint that you have something personal to say on...

Using AI to Build Semantic Models, Ontologies, and Fabric Data Agents

By

(This is the third post in a three-part series on how AI is changing...

SSMS Is Getting Smarter—and This Isn’t Just About Writing SQL

By

Continuing with my takeaways from SQLCon and FabCon Europe in Barcelona, let’s talk about...

Read the latest Blogs

Forums

Pay for Performance

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Pay for Performance, which is...

Helping an English Student with R

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Helping an English Student with...

Adding Bits I

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Adding Bits I

Visit the forum

Question of the Day

Adding Bits I

I have a table, dbo.bittest, where I am testing an application response. This has this structure:

CREATE TABLE [dbo].[BitTest]
(
[insertdate] [datetime] NULL CONSTRAINT [DF__BitTest__insertd__300F11AC] DEFAULT (getdate()),
[a] [bit] NULL
) ON [PRIMARY]
GO
My application runs this code:
INSERT dbo.BitTest
(
    insertdate,
    a
)
VALUES
(DEFAULT, 'true')
GO

See possible answers