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 |
|
joe.ingle
Starting Member
14 Posts |
 Posted - 2003-04-04 : 07:27:20
|
| Can anyone shed some light on why a set of nested tranactions would work flawlessly through QA, but rollback when called through ADO Command Object??Also how long is a piece of string? Only kidding, but I feel it has more to do with ADO than t-sql.Any ideas? |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2003-04-04 : 10:05:46
|
| Why is it rolling back?Because you receive an error in the app and rollback (or fail to commit) or because the sp rolls back?Usual reasons for failuresParameters you are passing aren't what you expectdate format for the connection different (dmy vs mdy)user doesn't have permissions==========================================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. |
 |
|
|
joe.ingle
Starting Member
14 Posts |
Posted - 2003-04-04 : 10:17:18
|
| Error is me!! Friday afternoon and all that. Just discovered it was rolling back because I'd forgotten to set permissions on an extended sp it's calling! Logged into QA as sa, so didn't pick up on it straight away. |
|
|
|
|
|
|
TRANS ROLLBACK &*&%$*%$