I have a customized data import executable in .NET 3.5 which the SqlBulkCopy to basically do faster inserts on large amounts of data. The app basically takes an input file, massages the data and bulk uploads it into a SQL Server 2000. It was written by a consultant who was building it with a SQL 2008 database environment. Would that env difference be causing this? SQL 2000 does have the bcp utility which is what BulkCopy is based on. So, When we ran this, it triggered a Deadlock error.
Error details: Transaction (Process ID 58) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
I've tried numerous ways to try to resolve it. like temporarily setting the connection string variable MultipleActiveResultSets=true, which wasn't ideal, but it still gives a Deadlock error. I also made sure it wasn't a connection time out problem. here's the function.
/// <summary>
/// Bulks the insert.
/// </summary>[code].....
My application is a survey application and I am using asp.net 2.0 and sql server 2005 version. There are many users taking survey at a single point of time. Some times delock is coming at a single method where i am deleting some records in a loop one by one(This delete statement may be executed for about 20 question in a page). This is a simple delete statement as below
delete table_name where column_name1='' and column_name2=''
column_name1 has foriegn key constraint, column_name2 also has foriegn key constraint.
The exception is as below.
Transaction (Process ID 204) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction
The topic of sql server deadlock has been discussed many times, however, I was unsure that even two simultaneous inserts on a table can end up in a deadlock situation. Scenario: While testing our application (SQL Server 2005 as backend, ASP.net 3.5) we inserted records into a table simultaneously (simplified overview) and that resulted into a deadlock for more than 70% of users.
I could not get a hang of this as how an insert is being deadlock as this is not a case of multiple resources. After a detailed analysis (of reproducing the bug by two users) I found that both the processes were holding a RangeS-S lock on the primary key index of the table and were trying to convert this into RangeI-N lock, that resulted into a deadlock and one transaction being killed.
Question: Can we avoid or reduce these kind of deadlocks as this is not a case of change in order of access of resources? Cant' we force the transaction to get exclusive lock initially so that it blocks the other process and avoid deadlock? What (adverse) effects that may have? Also could some one explain more about RangeI-N lock.
a script which creates a deadlock in a Sql Server 2008 database?I want to do a trace in a customer environment using a trace flag but first I want to test it in my own environment.
Using sql server 2005 and vb.net 2005.I'm creating a .net console application where I am doing a SqlBulkCopy from a non-sql server db to a sql server db table and on the call for the bulk insert:
[Code]....
I'm getting a time out error after around 1 minute, however I set BulkCopyTimeout (see above) to 100 minutes, the error:
<ERROR>
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
</ERROR>
Has anyone experienced this and how to fix this or how do I change the timeout so I dont get this error?
I m getting following error in my eventvwr . I couldnt find reasons of the following error.
"Transaction (Process ID 110) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction. "
The only thing my page is doing is inserting/updating data into a table in sql and the thing I can think of is because multiple users are using the same page to insert/update data? Will that cause deadlock?
While updating table Un handled exception was raised (asp.net with c# and SQLServer 2005)
Error Message: "Transaction (Process ID 91) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction."
I have 5 GB data, when I move from SQL server 2000 to 2008 with Import and Export wizard, my LDF size is increased to 30 GB, Can I reduce my LDF file or move. In my one of the table contain around 20 Lakh data which i have normalized in 2008 and create 4 tables, so my data is entering in normalized form in 2008. But due to size by hard disk is full. I have used shrnik command but it reduce to only 1 GB.
Could anyone tell me the features comparision between sql server 2000, 2005 and 2008 in the table format like below. sql server 2000 features | Extra features added/supported in 2005 | Extra features supported in 2008
how to read the data's in the text file using sql server 2000 and 2008. i have a text file in a server and it contains one column name with the multiple column values i need to read that informations and i need to update in a table in the database.
Iam using web developer express 2010. I was wondering if the web developer 2010 express supports SQL Server 2000. I know i could connectSQL server 2005 and up but is it possible i could connect sql server 2000 to web developer 2010 express?
My application is in .NEt Framework 2. 0 and which i have deployed in window server 2000 . when i run this application it gives me error like . server application unavailable .
I'm currently developing a web application using SQL Server 2005, ASP.Net MVC, ASP.Net SQL Membership Provider (for authentication and authorisation), and Linq to SQL. Everything works great and is running as planned in the development environment.However, the production environment has a SQL Server 2000 installation, and we are unable to obtain a copy of SQL Server 2000 to use in development.Upon deploying the web application to the the production environment, what options do I have for migrating the database (schema + data) from 2005 to 2000?
I am trying to connect my sql server 2000 using the sql server utility. It is perfecly working fine on my system but when try it on some other system i am getting an error message as "Could not find the server".
Is there any other configuration change that i need to make? I am connecting using TCP/IP