arooj300 (12/11/2013)
Thanks for the reply...I want to clear my question , I think this will be easy to understand.
we have a production DB. we have millions of data which client is keep sending and we have created SSIS package to copy data from excel to the DB.
At the same time when data is loading into the DB, the end user want to catch the data, because some time data is loading into the working hour also, at the same time end user can not sit idle. so that time the deadlock occurs.
for that reason I want the script or any alternate solution so that i can resolve the issue.
Thanks.
Your client is sending 'millions of rows' ... in Excel? As the latest version of Excel has a max number of rows per worksheet of 1,048,576, this sounds like a cumbersome multi-worksheet solution and I'd seriously be looking into moving to a CSV load instead. Anyway, I am getting sidetracked.
Are we dealing with updates, inserts or both?
Some sort of partitioning solution may be possible and there would be almost zero deadlocks - how is the data organised, is it by some sort of transaction date?
-edit: fix typo
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.