Comments on: Output errors from SQL Server stored procedure

By: spionred

spionred — Sun, 26 Apr 2009 20:00:58 +0000

Thanks,

I will give that a try.

Kevin.

By: mrdenny

mrdenny — Sun, 26 Apr 2009 04:28:01 +0000

In SQL Server you can create a table variable and put the error information into that table variable. Then after committing or rolling back your transaction you can take the data from the table variable and put it into an actual table.

There isn’t any way to output from a stored procedure to a text file directly.

By: carlosdl

carlosdl — Fri, 24 Apr 2009 18:49:49 +0000

Interesting, Kccrosser.

It seems that you have many years of experience in Oracle.

That’s valuable.

By: kccrosser

kccrosser — Fri, 24 Apr 2009 15:39:03 +0000

Ref the autonomous transactions – this was in a system we built in 1997-2000 on Oracle 7, so those weren’t an option. We wound up with a little over 1 million lines of PL/SQL code in lots of layers, and needed a way to log errors (and debug and stats, etc.) without worrying about whether there was a transaction in progress.

With the DBMS_PIPE package, it was trivial to create a simple log procedure that anything could call and pass the data to the logging table.

By: spionred

spionred — Thu, 23 Apr 2009 21:09:45 +0000

Thanks for the advice.

I will report back when I have cracked it.

Cheers,
kevin.

By: carlosdl

carlosdl — Thu, 23 Apr 2009 19:08:24 +0000

In Oracle you could also use autonomous transactions, so you can commit the error log separately.

By: kccrosser

kccrosser — Thu, 23 Apr 2009 16:06:58 +0000

Keep in mind one common “gotcha” when dealing with error logging.

If the procedure is called from within a transaction, or if the failing statement is occurring inside a transaction, and you need to do a rollback to maintain the overall transaction integrity, there is no way to write the log record to a table, as that write will also be rolled back.

I solved this in an Oracle system using the dbms_pipe package. With dbms_pipe, you can create a “listener” process to receive and log messages, and pipe messages are not rolled back in transactions, so when an error occurs in a transaction, simply “pipe” the log information over to the listener to record it, and then execute the rollback to ensure transaction integrity.

By: spionred

spionred — Thu, 23 Apr 2009 04:51:37 +0000

Yeah,

I was hoping to just write to a txt file but I suppose once the process has complete I could query the table from code and output to file from there.