Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
totano
Starting Member
2 Posts |
 Posted - 2004-07-31 : 21:22:48
|
| i were running a BCP to bulk insert a huge text file (1.000.000 more and less but doesn't matter). because i forgot to drop the indexes, after 3 hour of BULK INSERT running i decide to kill the BCP. bad idea? now, after 48 hours, the rollbak it's still alive. the facts: 669.000 rows were lifted to insert to the table, in thats hours. i just have only 24 hours to do (what ?)1) stop the sql services and pray for the non suspect state? or2) wait until rollback ends ?it's a democratic problem. just vote it ! thanks in advance ! remember the deadline ! gurús! |
|
|
kselvia
Aged Yak Warrior
526 Posts |
Posted - 2004-08-01 : 00:41:20
|
| I have stopped SQL Server many times to cancel a rollback without adverse affects (i.e.. suspect DB) but your mileage may vary. This is just my experience. Others may have different experience.--KenYour Kung-Fu is not strong. -- 'The Core' |
 |
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2004-08-01 : 14:56:41
|
| Drop the table and recreate it? :) Have fun with this one.MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
|
|
|
totano
Starting Member
2 Posts |
Posted - 2004-08-01 : 17:13:32
|
| thank's to both, finally, after 50 hours of runnig, the rollbak ends with an error 1608, because the syslog segment of the database it has filled out. after that, i made an dump tran of the database with no log and restart the services. i think that it was the same as if i were down the services. isn't it ?thanks again ! i really suffer a lot (50 hours at least!) |
|
|
|
|
|
|
How much to kill a rollback from an bulk insert ?