After aborting a large table transfer (48MB, 219k row) from Access using
an Append Query, the SQL Server table has been rolling back for over 10
I'm running SQL 6.5 SP4 on NT4.0 SP3 on a 2-processor 300MHZ PII 128MB
server with fast SCSI drives - so the hardware just ain't the problem!
1) Ran Append Query from Access to SQL Server linked tables
2) When Access came up with 8,000 key violations (due to design error in
an SQL table index), I selected NO (do not append remaining data).
3) Up thru 10 hours later, ALL USE OF THE TABLE FAILS with ALL
APPLICATIONS USING THE TABLE - An unacceptable situation!!!
4) Up thru 10 hours later, try to even look at the SQL table being
rolled back by double-clicking the linked table in Access, and you get a
query timeout failure
5) Up thru 10 hours later, try to select a record using ISQL/w, and it
hangs forever, as does trying to change design with Enterprise manager.
6) 10 hours later, tried stopping the SQL process and re-started it -
MISTAKE!!! NOW access to the WHOLE *&(*^&% DATABASE IS LOST while it's
"recovering". It's been HOURS since I did that, and it's STILL
This is INSANE (I've been going thru this song & dance for a solid WEEK
now - first running out of log space, then running out of locks, then
Access just locked up several hours into the append, and the NT Server
spontaneously re-booted once during a recover database operation)!!!
Anyone know if Oracle is any better????
Please reply via e-mail also