I dropped a table today and it took 7.5 hours! There were 5 million rows. There were 6 columns including an identity and a double value plus 4 foreign identity columns that were indexed (both individually and one composite index). I did this from the web console using all default settings. There were no other connections to the db. The computer is quite standard and was not a constraint. The CPU, memory and disk usage were quite standard.
I have a backup of the db so I also tried truncating the same table (on my backup file) and this took just as long. Previously I had tried to delete 4 of the 5 million rows but I cancelled this because it took too long. There was a huge delay to re-open the database after the cancellation (several hours). Then the db was ok again (i.e. responsive). While I was waiting all those hours I was browsing this forum and also looking for an alternative database product. I can't afford to be delayed like this. How can I avoid this ever happening again? -- View this message in context: http://h2-database.66688.n3.nabble.com/Performance-DROP-TABLE-very-slow-on-large-tables-tp2885986p4024540.html Sent from the H2 Database mailing list archive at Nabble.com. -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
