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 |
|
wotrac
Yak Posting Veteran
98 Posts |
 Posted - 2003-06-21 : 05:30:40
|
| Before we start let me say that I am not an experienced SQL Programmer.I have a complex stored procedure that affects several tables in my database. The procedure changes the customer code on a transaction to an alternative code provided by an input parameter.I have not had any problems with it until the other day when it failed.I believe that the reason it failed was that the prodecure was called just as a SQL Transaction Log backup was processing.According to our DBA the standard SQL Log backup, Truncates the transaction log after backing up and it appears this may have caused the conflict.As I am a little inexperienced in these matters can anyone tell me how to avoid this type of conflict.Prodecure code can be supplied if it will helpPaul |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2003-06-21 : 11:55:37
|
| The transaction log backup should not affect any processing. The truncate will only truncate inactive transactions and would not have affected your processing (and your dba should know that).If this has caused a problem then there is something very wrong with your system.What was the error message that you received.Was anything recorded in the sql server/nt log?==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
|
|
|
Help with Stored Procedure Conflict