February 24, 2010 at 2:20 pm
I have a DTS package that runs every night at 8:30pm. At that time, users are entering data in tables using an MS Access application.
Between the application and the DTS there are two common tables that are updated. Users are complaining that at 8:30pm the application does not save some data. But the app does not show any error messages. Actually the app calls stored procedures that run updates on the common tables.
Can someone explain to me what happens behind the scenes if both the app and the DTS both attempt to update the same record on a common table? Are there implicit locks that might cause one to fail? No transactions are used in the stored procedures.
The DTS (which imports text files) calls a bunch of stored procedures too and once in a while, it fails at exactly 8:30pm as well.
Thanks,
February 25, 2010 at 7:08 am
To sort of answer your question. Yes, both DTS and the Access applications are taking locks on the tables/indexes/rows affected by the processes. If data is not being saved, then the application should be getting a timeout error or potentially a deadlock error. I'd check to see if the Access application is doing anything to handle errors. You could also check the windows and Sql Server logs to see if there are any messages there telling you what is happening.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply