October 2, 2013 at 3:16 pm
I was using the SQL 2012 import wizard to double the size of my 80k record table.
It has been stuck on the same '1160 rows transferred message' for three hours, which is weird as it normally only takes a couple of minutes to copy the whole table.
In the Task Manager it is still in 'running' status.
Should i just let it run, or can i stop it using a command, without the DB going into 'suspect', 'emergency' or some other weird state?
Will 'take offline' and go back 'online' or 'detach' then 'attach' safely work?
Thanks
October 3, 2013 at 12:30 am
You should be able to just kill it, transactions should rollback.
If you want to know what is going on, save the SSIS package instead of running it and inspect it's contents. If you are reading and writing from/to the same source, the package might lock itself.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
October 3, 2013 at 7:59 am
I'd check for blocking and a couple of other things before I killed the job so that I could understand what's happening a little better because the same thing could happen again. It might just be that someone has a lock on the table because they forgot to commit a transaction. It could also be a serious problem but you won't know if you just kill the task and try rerunning it.
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply