Race condition in SQL Server 2005

hi,
How SQL Server 2005 handel concurrent access to database.
for example. if two application user same data base and same user name to
access it. when both application attempts to access the database how Server
handle this race condition.
Thank in advance
with regards,
AnbuOn 29 May, 07:00, anbu <a...@.discussions.microsoft.com> wrote:
> hi,
> How SQL Server 2005 handel concurrent access to database.
> for example. if two application user same data base and same user name to
> access it. when both application attempts to access the database how Serve
r
> handle this race condition.
> Thank in advance
> with regards,
> Anbu
What you describe is normal. A user's session is scoped to a
connection not a user name, so there is no special problem associated
with multiple users under the same user name accessing the same
database.
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--|||Thanks David,
iam very new to SQL Server. can you refer any links where i can find details
about how race condition is handled by Server.
with regards,
Anbu
"David Portas" wrote:

> On 29 May, 07:00, anbu <a...@.discussions.microsoft.com> wrote:
>
> What you describe is normal. A user's session is scoped to a
> connection not a user name, so there is no special problem associated
> with multiple users under the same user name accessing the same
> database.
> --
> David Portas, SQL Server MVP
> Whenever possible please post enough code to reproduce your problem.
> Including CREATE TABLE and INSERT statements usually helps.
> State what version of SQL Server you are using and specify the content
> of any error messages.
> SQL Server Books Online:
> http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
> --
>|||See Books Online topics related to locking and row versioning
(http://msdn2.microsoft.com/en-us/library/ms187101.aspx).
Keep in mind the scope that David mentioned when reading the documentation.
You will often see the terms "user" and "session" used interchaneably to
refer to a user's session on a database database connection. This is
completely unrelated to the login/user used to connect to SQL Server.
Hope this helps.
Dan Guzman
SQL Server MVP
"anbu" <anbu@.discussions.microsoft.com> wrote in message
news:53410F4E-C145-446F-8F28-DFB6A24F2823@.microsoft.com...[vbcol=seagreen]
> Thanks David,
> iam very new to SQL Server. can you refer any links where i can find
> details
> about how race condition is handled by Server.
> with regards,
> Anbu
> "David Portas" wrote:
>|||"anbu" <anbu@.discussions.microsoft.com> wrote in message
news:53410F4E-C145-446F-8F28-DFB6A24F2823@.microsoft.com...
> Thanks David,
> iam very new to SQL Server. can you refer any links where i can find
> details
> about how race condition is handled by Server.
>
Really this isn't a true race condition. (Well, I suppose it can be, but
what you seem to be getting at more is simply multiple accesses.)
Keep in mind like any decent RDBMS, SQL Server is designed to handle this.
At a very basic level, "whoever gets there first wins".
But you need to look up blocking and things like Committed vs. uncommitted
read, read serializable. etc.
[vbcol=seagreen]
> with regards,
> Anbu
> "David Portas" wrote:
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html