Why should deleting even a large amount of data from a SQL database take more than a minute or two? On the scale of MSSQL this isn't even a 'large' amount of data.
This isn't a SQL thing really, but the application that is going against it. I tell it to delete a bunch of info and it has been sitting there for at least 5 minutes.
September 5th, 2006 11:33am
Maybe... It's semi-impossible to see them, or even the table structure, because the app installs its own SQL instance with a generated SA password.
They apparently didn't want any boneheads messing with the data directly.
Or maybe they didn't want anyone to discover the bodies...
September 5th, 2006 11:40am
heh, try 'admin' as a password...
There's lots of reasons why this can happen, but they all boil down to this: Your computer is possessed by evil demons
Solution: Get your computer exorcised by your local Catholic priest
September 5th, 2006 11:52am
Uhm that is soooo damned weird. Seriously, it just deleted part of what I told it to.
What it left is 666 records. No kidding.
September 5th, 2006 11:59am
Awesome! Our dark lord Satan RULEZ!
Are you doing a DELETE FROM blah WHERE or a TRUNCATE TABLE blah ?
The truncate is significantly faster because it doesn't write to the transaction log. Of course, if you only want to nuke *some* of the data in the table, it would be the wrong thing to do.
September 5th, 2006 12:51pm
Nah, I don't have direct access to the SQL. I'm going through the app. No clue what monkey business is going on behind the scenes. It has taken about an hour to delete ~2000 contacts from it.
Thanks for the tip though. :)
September 5th, 2006 1:00pm