we're about to port our databases from SQL 2000 to SQL 2005. If we can't modify directly the system tables, how are we going to proceed is log suspend on startup cases? What we usually do is to perform a bypass recovery by altering the sysdatabases table and truncating the log. Have you guys experienced this using SQL 2005?
actually, its not about porting the database from SQL 2000 to SQL 2005 and not about changing users whatsoever; its on how to go about a log suspend database on startup that can't be recovered due to insufficient logspace.