I'm working with a client that is experiencing a strange problem. It takes SQL over 5 minutes to fully startup. This is a SQL 2000 with SP4 running on Windows 2003 with SP2. Everything appears to be working fine after the startup, but the delay is strange. The server has about 8 databases on it and all are noted as "Startign up database 'XXXX'. in the log. Then after about 5 minutes, "Recovery complete." is added to the log. This also seems to be a new problem that has developed in the last couple of months, but nothing major has changed on the server. I've started SQL using the -T3608 trace flag so that only Master is started, and then walked through each database to see how long each would take. All were quick to start, except for one. It took exactly 5 minutes to start. So, this database seems to be the problem. I can CheckDB on it and found no problems. I've stopped and restarted SQL several times to see if it would vary, but always 5 minutes. Does anyone have any ideas of what to look at next? I'm assuming that something is going on with the recovery process in this particular database, but nothing is showing up in the log. Is there a way to see what is going on during the recovery process? The database is fairly large, 70 GB, but I've worked with much larger without this issue. All the settings for the server and database appear to be the defaults. Any help would be greatly appreciated!!