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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2006-06-22 : 09:46:28
|
| John writes "Application executes stored procedure via own transaction (Autocommit = FALSE)Stored procedure is made up of two jobs:Job 1. Call another procedure which retrieves a value from a table, adds a number to it and writes back the new value (with COMMIT) for other users to access.Job 2. Do other work in a transaction that may or may not be committed by application.End(Application issues COMMIT or ROLLBACK)I assume Job 1 above needs a transaction DIFFERENT FROM Job 2 to work. How do I go about it?" |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2006-06-22 : 10:12:11
|
| It will have to be done on another spid.A number of ways of doing it a cou0ple that spring to mind:Starting a job which does the work - check that this doesn't lock system tables.Use osql to get another connection.==========================================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. |
 |
|
|
|
|
|
COMMIT as part of transaction