Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2000-12-30 : 11:02:46
|
Clay writes "When designing a client application (say a VB 6.0 client) which will be referencing and updating data which is located on an MS SQL Server database, what would be an appropriate way to handle locking requirements when executing stored procedures through ADO?
I have read that using client side locking mechanisms (as those which are native to ADO recordsets) has dissadvantages (in terms of performance) over using SQL store procedures, but I am unclear as to how I can handle database currency while routing all of my data manipulation through a set of stored procedures. Should I cache the values of the original record on the client, and use them for establishing a conditional update... Should I use a timestamp field in each table to determine if the row is still available for update... How is this typically implemented?
Thank you,
Clay" |
|
|
|
|
|
Locking methods when stored procedures??