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,042 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,365 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,049 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,467 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,751 reads
By DataOnWheels
The T-SQL Tuesday topic this month comes James Serra. What career risks have you...
This T-SQL Tuesday is hosted by the one and only James Serra – literally...
By Steve Jones
This month we have a new host, James Serra. I’ve been trying to find...
Hi, ssms is free here. I can think of other reasons to do this...
I've written some documentation on using different Markdown types of files on GitHub. It's...
Comments posted to this topic are about the item Not Just an Upgrade
I am doing development work on a database and want to keep a backup so I can reset my database. I make some changes and want to restore over top of my changes. When I run this code, what happens?
USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO USE DNRTest GO CREATE TABLE MyTest(myid INT) GO USE master RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACESee possible answers