Re: ROLLBACK a transaction
From: Toby Herring (therring*_at_*teletrack.com)
Date: 08/27/04
- Next message: Anith Sen: "Re: Aggregate XOR ? Or UDF help..."
- Previous message: sserge: "Cursor in view"
- In reply to: Jeannick: "ROLLBACK a transaction"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 27 Aug 2004 11:15:45 -0400
Not really. That's the whole point to transactions.
An alternative might be to use READPAST, in which case you could still
execute your select query, but it would ignore all non-committed records as
though they didn't exist.
-- Toby Herring MCDBA, MCSD, MCP+SB Need a Second Life? http://secondlife.com/ss/?u=03e0e5b303c234bf08e80ee40119a65e "Jeannick" <Jeannick@discussions.microsoft.com> wrote in message news:7C21FBC6-072D-4B85-8B9E-2680EBBF7E61@microsoft.com... > I'm reading records from one database to another database, when something > goes wrong i'm doing a rollback. We have to do a rollback of all the > records. > Everything is going well, except that the records are locked untill the > commit. > > And when a record is locked we can't do a select in this table whitout > nolock. > > Table a with 100 records, 1 of these records is locked > " select * from a " fails. > > Is there a solution for this whitout changing the select to "......with > (nolock)" > > Thanks in advance
- Next message: Anith Sen: "Re: Aggregate XOR ? Or UDF help..."
- Previous message: sserge: "Cursor in view"
- In reply to: Jeannick: "ROLLBACK a transaction"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
