All user databases in suspect mode - SQL Server 2000
DISCLAIMER: This is a question about Root Cause not on how to fix a Suspect Database Recently our systems engineering section "Re-IP'd" one of our QA SQL Server database servers after migrating to new blades. Immediately after the box came up All the USER databases were in suspect mode. I was curious if the changing of the IP address would cause this situation and what I can have them do differently for any other servers going forward. One thing to note was they did not put the services in manual start mode so SQL tried to reconnect as soon as the box came back up. That is one thing I told them they should have done would be to put the services in manual start mode and then that way it could be brought up cleanly when they were actually ready for it to be started. Just trying to mitigate another issue in the future so if you have had this experience or have any ideas (other than the Re-IP) then I would be grateful for your assistance. Cheers!
Changing the IP address should not have had any effect on SQL Server nor your databases unless this was a primary clustered instance and it caused a failover, in that case SQL Server should have shut down servers and migrated and came up clean on the secondary node. That does not sound like the case here. What is more likely the scenario is that systems engineering improperly shut down your server once or multiple times not allowing SQL Server to go through crash recovery properly and then forcing SQL Server to mark the databases suspect. I would be looking at the SQL Server Log as well as the Windows Event logs to see what actions took place. If the logs are missing some Sys Eng is trying to cover their butts. Changing an IP address on a standalone instance should have only caused the database server to not be available via the network for a few seconds or minutes while the IP changed and DNS was updated.