Skip to main content
added [query-performance] to 2412 questions - Shog9 (Id=1924)
Link
edited tags
Link
Aaron Bertrand
  • 181.5k
  • 28
  • 402
  • 619
Tweeted twitter.com/#!/StackDBAs/status/362040858482184192
deleted 79 characters in body; edited title
Source Link
Aaron Bertrand
  • 181.5k
  • 28
  • 402
  • 619

How to avoid timeouts during big insert in MSSQLDML operations

I'm using mssql 2008 andI have a big insert script iI need to run. Its about 55.,000 records and 160 columns. The script is already created and I cantcan't create it again.

The problem iI have is that this runs for about 4 hours or so, and during that time the system that useuses this database getgets really slow and timeout a lot.

I would not care if its slower my insertINSERT is slower but i can bather the normal users with it shouldn't impact other users.

I was thinking in doing some batch of letslet's say 500 rows and use the waitforWAITFOR, but was wondering if there could be a better option for doing this.

Any suggestions are really appreciated.

Thanks!

How to avoid timeouts during big insert in MSSQL

I'm using mssql 2008 and have a big insert script i need to run. Its about 55.000 records and 160 columns. The script is already created and I cant create it again.

The problem i have is that this runs for about 4 hours or so, and during that time the system that use this database get really slow and timeout a lot.

I would not care if its slower my insert but i can bather the normal users with it.

I was thinking in doing some batch of lets say 500 rows and use the waitfor, but was wondering if there could be a better option for doing this.

Any suggestions are really appreciated.

Thanks!

How to avoid timeouts during big DML operations

I have a big insert script I need to run. Its about 55,000 records and 160 columns. The script is already created and I can't create it again.

The problem I have is that this runs for about 4 hours or so, and during that time the system that uses this database gets really slow and timeout a lot.

I would not care if my INSERT is slower but it shouldn't impact other users.

I was thinking in doing some batch of let's say 500 rows and use the WAITFOR, but was wondering if there could be a better option for doing this.

Source Link
Loading