Post
by michael » 22 Apr 2005, 09:10
Posted by: Michael Hummel
thanks for your comments,
@Jim:
i have set recovery off and no one else was connected to the database (job
runs overnight)
so, does locking the database speed up the process ??
@Frank:
dropping the table is not the thing i want. its not our database, it comes
with a third party application (employee management, hr). dropping means to
rebuild all indexes, all insert/update triggers and a lot of security
(grants).
i cant understand, that deleting a row costs hundreds of times more than
inserting with load.
this morning the job comes to an end: This means one million rows in nealry
6 hours
957,934 ROWS DELETED
IN 20,682.31 SECONDS
46.12 ROWS PER SECOND / 0.02 SECONDS PER ROW
Compare: when i do the same with sqlserver 2000: 1 second (with truncate
table), 6 minutes (with delete from table)