Unanswered: What is the Performance Impact for Dropping a large 260 Gig Database
I am dropping a production database that is about 260 GB. I am doing this during normal production hours.
What impact can this have on performance? What can I check to guage the performance impact? Could a possible impact be i/o waits?
Currently the concern is that I have a process that is executing deletes from tables that are over 50 million rows on ASE Sever-A.The large database is being dropped from a different server, ASE Server-B. Both ASE servers are on the same host. What impact could this have on the production host, if any?
As long as its multi-cpu host and no. of engines on all ASE hosts less than the no. of cpus, you should be ok. But you are better off waiting for the weekend to drop if you can wait till then. The drop database does lock up some system tables, so you may find some blocking if there are other activities in the same ASE server.