[dba-SQLServer] Locking Discussion

Dan, the very realistic truth is this -- you can't prevent data conflicts. 
What you can do is minimize them. You do that best by letting SQL Server do 
the work for you. Of course, you need to understand how SQL Server works in 
this regard. SQL Server has a set of internal rules that it follows and 
almost always, it will make the right choice. If it doesn't, it's probably 
your strategy and not SQL Server's that's really the problem.

Susan H.


> To everyone:
>
> Several weeks ago there was a protracted 'discussion' about this issue.
> While I skimmed the discussion I never did see anyone provide an answer to
> the question, "How can I prevent data conflicts in SQL Server?"
>
> Today I started reading my copy of Mastering SQL Server 2005 Express
> Edition, coauthored by Susan Harkins and Mike Gunderloy.  News to me was
> that SQL Server has it's own quite sophisticated and flexible locking
> mechanism (see Chapter 21 - Locking).  From page 477: "What this means to
> you as an application developer is that you almost never have to worry 
> about
> locking."
>
> I'm just getting started upsizing an Access app, and would like to hear 
> some
> discussion on this and on how this locking mechanism impacts your
> development of 'unbound' or 'bound' Access FE applications.
>
> Thanks!
> Dan
>
> _______________________________________________
> dba-SQLServer mailing list
> dba-SQLServer at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
> http://www.databaseadvisors.com
>