May 22, 2008 at 1:23 pm
Hi all! I'm new to sqlserver (using 2000) at $WORK and I've inherited a project that has been done in a less than ideal way. The author of this system decided to use a maze of stored procedures and database table triggers in order to modify the data, and has also replicated the same data across several databases. It's ugly.
Enter me. I'm working to modify this database, and one of the stored procedures doesn't work. It fails every time with this error:
Executed as user: NT AUTHORITY\SYSTEM. OLE DB provider 'MSDASQL' could not UPDATE table '[MSDASQL]'. The rowset was using optimistic concurrency and the value of a column has been changed after the containing row was last fetched or resynchronized. [SQLSTATE 42000] (Error 7343) [SQLSTATE 01000] (Error 0) [SQLSTATE 01000] (Error 0) [SQLSTATE 01000] (Error 7312) OLE DB error trace [OLE/DB Provider 'MSDASQL' IRowsetChange::SetData returned 0x80040e38: The rowset was using optimistic concurrency and the value of a column has been changed after the containing row was last fetched or resynchronized.]. [SQLSTATE 01000] (Error 7300). The step failed.
I get that something changed while it was writing (probably due to the horrible nest of stored procedured, etc.) but is there anyway I can get a stack trace to see exactly where the changes were happening, and exactly at which point of execution these errors occurred? Thanks!
May 22, 2008 at 2:30 pm
It looks like you are using snapshot transactions. You may get more help with this if you post it in a SQL Server 2005 forum. This forum is for SQL Server 2000.
This error means that the data has changed from the time your SP read it to the time it attempts to alter it. You may be able to run a trace and capture who is altering the data.
May 22, 2008 at 3:02 pm
Sounds like you might have a trigger that is firing and updating the same row that the stored procedure is updating. Did you try using SQL Profiler with the StmtStarting and StmtCompleting events selected?
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy