mark.hall (2/23/2010)
SQL 2000 on W2K3I've got a 200GB database 1 file 1 log. When the DB has to grow it causes the application to wait which causes the 250 robots that are making jeeps to stop. I've tried spliting out the largest table 100GB to it's own file group but the process takes to long to run need to complete the maintenance over a weekend. So I'm wondering if I've got any other options.
I'm already archiving 2 times a year.
You have a ton of data. Is there no way for you to determine how much growth you would need each week or month and pre-grow the database during the maintenance period so it wouldn't have to grow during production time?
Also, you might want to convince Chrysler that it's bloody 'bout time to upgrade both the hardware and the software for their robots so you can take advantage of things like "instant file initialization" and some other features. I guarantee that the whole shebang will cost less the occasional outage on the production line especially when the normal rate is 60+ Jeeps per hour.
--Jeff Moden
Change is inevitable... Change for the better is not.