Re: How to really cancel an asynchronous Connection.Execute
From: Ian Boyd (ian.msnews010_at_avatopia.com)
Date: 03/23/04
- Next message: Brannon Jones [MS]: "Re: MSDataShape (MDAC 2.8) limitation on the query length"
- Previous message: Anxan: "Create Connectionless Recordset Errors"
- In reply to: William \(Bill\) Vaughn: "Re: How to really cancel an asynchronous Connection.Execute"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 23 Mar 2004 11:45:03 -0500
> When you cancel an operation, you're asking the engine to undo what you
> asked it to do. If it's an update or other action query it has to roll
back
> the work.
My particular frustrations where with a select statement.
> If it's a long-running operation (and it sounds like it is) there
> is a lot of work to do. It also might be blocked by some other operation
> going on which means it can neither proceed or rollback until it times
out.
It's not blocked; just SQL Server decides to finish trying to run the query,
before it will cancel running the query.
- Next message: Brannon Jones [MS]: "Re: MSDataShape (MDAC 2.8) limitation on the query length"
- Previous message: Anxan: "Create Connectionless Recordset Errors"
- In reply to: William \(Bill\) Vaughn: "Re: How to really cancel an asynchronous Connection.Execute"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|
