Locking and Transactions /w Linked Servers
From: Brandon Slezak (Slezak_at_discussions.microsoft.com)
Date: 12/06/04
- Next message: mohaaron_at_gmail.com: "Re: DTS copy all objects failed with invalid column name"
- Previous message: David Gugick: "Re: Preventing deadlocks"
- Next in thread: Mike Epprecht (SQL MVP): "RE: Locking and Transactions /w Linked Servers"
- Reply: Mike Epprecht (SQL MVP): "RE: Locking and Transactions /w Linked Servers"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 6 Dec 2004 14:57:02 -0800
Hi All,
How exactly does Sql Server lock data when the transaction is across
multiple servers? Assume a default isolation level and no special locking
command.
For instance if Server A says
BEGIN TRAN
INSERT INTO Customers
OR
SELECT * FROM Customers
COMMIT TRAN
How will users on Server B be effected if they are trying to access data in
the Customers table natively on Server B? Does Sql Server issue intent
locks? How does DTC know what kind of locks to issue on Server B?
-Thanks!
-Brandon
- Next message: mohaaron_at_gmail.com: "Re: DTS copy all objects failed with invalid column name"
- Previous message: David Gugick: "Re: Preventing deadlocks"
- Next in thread: Mike Epprecht (SQL MVP): "RE: Locking and Transactions /w Linked Servers"
- Reply: Mike Epprecht (SQL MVP): "RE: Locking and Transactions /w Linked Servers"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|