Error handling in SQL Server 2000 is tricky. And it isn't the most robust system in the world. Stefan Popovski started a series on error handling using @@error and xact_abort. Here's the second installment of this series looking at error handling in nested stored procedures.
2004-06-08
10,026 reads
The error handling in SQL Server leaves something to be desired, especially compared with other RDBMSes and languages. The standard method of testing for errors can leave your code bloated and hard to read. Stefan Popovski looks at another method of handling errors.
2004-04-21
8,352 reads
In this short article that follows up on an earlier one that discussed dependency issues we have some code that will generate simple treeview type view of the relationships between procs. Mostly code, more so than usual, but we thought you might find the idea useful!
2004-02-09
7,018 reads
Sysdepends is a neat idea, but in practice it's not always accurate. This article talks about why it's not always reliable and presents some code (recursive even!) that will let you find all the dependencies by querying the system tables.
2003-12-18
9,431 reads
Word can do that. Why SQL not? Sometimes I want to see every space, horizontal tabulation, line feed or carriage return. It can help to write well formated store procedures.
2003-11-28
363 reads
Calculates the factorials of numbers between 1 - 31.High level is 31 because maximum stored procedure, function, trigger, or view nesting level is limited to 32.
2003-10-08
644 reads
New Author! Stephan writes about why he thinks the bulk load capabilities added in the SQLXML3 addition are a great way to handle imports - maybe so good that you'll stop using BCP.
2003-07-21
12,718 reads
By Steve Jones
This is my last week of the year working (I guess I come back...
By Steve Jones
suente– n. the state of being so familiar with someone that you can be...
Anyone (everyone?) who has ever tried to learn a programming language knows that to...
I am getting the below error when I execute a SQL command in SQL...
I am getting the below error when I execute a SQL command in SQL...
Hi everyone. I have this table and this information. (left side of the image)...