How does the SQL Server handle two simoutanious read or write operations?
From: Quentin Huo (q.huo_at_manyworlds.com)
Date: 03/22/04
- Next message: Tenaya: "Re: Case Sensitive"
- Previous message: Greg Linwood: "Re: Error with "Operand type clash""
- Next in thread: Adam Machanic: "Re: How does the SQL Server handle two simoutanious read or write operations?"
- Reply: Adam Machanic: "Re: How does the SQL Server handle two simoutanious read or write operations?"
- Reply: Greg Linwood: "Re: How does the SQL Server handle two simoutanious read or write operations?"
- Reply: Louis Davidson: "Re: How does the SQL Server handle two simoutanious read or write operations?"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 22 Mar 2004 15:37:31 -0600
Hi,
In web application, if there are two visitors of a website read/write
from/to a database at the same time, how does the SQL Server handle these?
The read operations will be run at the same time and the write operations
will be put into a queue and are run one by one? If it is right, that means
a write operation will take more time than a read operation and many write
oprtations will cause the traffic problem, but the read operations won't no
matter how many they are.
Thanks
Q.
- Next message: Tenaya: "Re: Case Sensitive"
- Previous message: Greg Linwood: "Re: Error with "Operand type clash""
- Next in thread: Adam Machanic: "Re: How does the SQL Server handle two simoutanious read or write operations?"
- Reply: Adam Machanic: "Re: How does the SQL Server handle two simoutanious read or write operations?"
- Reply: Greg Linwood: "Re: How does the SQL Server handle two simoutanious read or write operations?"
- Reply: Louis Davidson: "Re: How does the SQL Server handle two simoutanious read or write operations?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
Loading