Transaction deadlock crash + vb.net 2008
-
Hi, In am doing the simultaneouly two imports. Which export the data from excel to sql server. There are some common tables, which are being approached by both these imports. and results in deadlock Transaction (Process ID 53) was deadlocked on resources with another process and has been chosen as the deadlock victim. Rerun the transaction. In the sql profiler, i have seen that a couple of queries are taking time, which are using common tables in imports. I have optimized it also. Can you provide me any suggestion? Thanks
-
Hi, In am doing the simultaneouly two imports. Which export the data from excel to sql server. There are some common tables, which are being approached by both these imports. and results in deadlock Transaction (Process ID 53) was deadlocked on resources with another process and has been chosen as the deadlock victim. Rerun the transaction. In the sql profiler, i have seen that a couple of queries are taking time, which are using common tables in imports. I have optimized it also. Can you provide me any suggestion? Thanks
-
Hi, In am doing the simultaneouly two imports. Which export the data from excel to sql server. There are some common tables, which are being approached by both these imports. and results in deadlock Transaction (Process ID 53) was deadlocked on resources with another process and has been chosen as the deadlock victim. Rerun the transaction. In the sql profiler, i have seen that a couple of queries are taking time, which are using common tables in imports. I have optimized it also. Can you provide me any suggestion? Thanks
This would tell me that you can't do the imports simultaneously since they both add/modify to the same table(s). You don't have a choice but to do them sequentially.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008