Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
zavier
Yak Posting Veteran
50 Posts |
 Posted - 2001-06-07 : 15:11:46
|
| Hello,I have a really big problem that I desperately need some help with. I have a stored procedure that works fine in query analyzer, but it generates errors. It does the job though. Basically the procedure creates a temp table imports a text file into the table, compares the contents of the temp table to a production table in the DB, and then inserts records into the production table based on the comparison. The errors are:Msg 3701, Sev 11: Cannot drop the table '#RES', because it does not existin the system catalog. [SQLSTATE 42S02]Msg 1708, Sev 11: The total row size (38120) for table '#RES' exceeds themaximum number of bytes per row (8060). Rows that exceed the maximumnumber of bytes will not be added. [SQLSTATE 01000]Msg 0, Sev 0: Associated statement is not prepared [SQLSTATE HY007]The total row size (38120) for table '#RES' exceeds the maximum number ofbytes per row (8060). Rows that exceed the maximum number of bytes willnot be added. [SQLSTATE 01000]These errors do not prove to be a problem to getting the processes done but when I try to call the procedure from a VBS script SQL Server returns the errors to the script not letting it continue. In fact when the procedures are called from a job the errors are recorded in the log.The problem is that I cannot take advantage of the features in the scheduling agent because even if the stored procedures process correctly they still return that the process failed. I would like to have the stored procedure not report non-fatal errors or have the agent not consider non-fatal errors as a failure. This was I can set up notification. Thanks |
|
|
|
|
|
Help with Job/Stored Proc Prob