Hi Sam, Actually did the MS SQL Admin course this week and tested this out by renaming the data files, however I doubt you actually did this! If the data files were corrupted in the first place, I don't think re-attaching them is likely to solve the problem. You would have received a SQL error message if you files / log was full.
There are a couple of dbcc commands that act similar to the old 'scandisk' command but for databases. However now that you've deleted them it may become more difficult. Anyway, the commands were something like (they're all available from BOL): DBCC CheckDB DBCC CheckAlloc etc. How did you delete the databases? Perhaps the master db still has remnants. If you have a backup of msdb and model, and don't mind re attaching any other databases and/or users then you could run the 'rebuildm' command which recrates all the system databases, then try re-attaching. (Note: this will also delete any jobs / agents / backups you have scheduled, which are stored in msdb) Alternatively, have you tried restoring your DB from a recent backup? Can't think of anything else.. sorry. Cheers, Andrew -----Original Message----- From: Tore Bostrup [mailto:tbostrup@;telocity.com] Sent: Friday, 25 October 2002 5:21 AM To: ActiveServerPages Subject: Re: (Suspect) SQL server database MS KB lists article ID Q274266 for the boolean search query '3624 and "SQL Server"'. I'm not sure whether you are getting the error during recovery of such a statement. If your are running SQL Server 7 SP2, you may consider installing SP3 and then trying again. HTH, Tore. ----- Original Message ----- From: "Sam Thompson" <[EMAIL PROTECTED]> To: "ActiveServerPages" <[EMAIL PROTECTED]> Sent: Thursday, October 24, 2002 12:07 PM Subject: Re: (Suspect) SQL server database > Thanks Tore. > > Ive now deleted the suspect database and kept the MDF and LDF files. Ive > created a new database and im trying to use sp_attach_db to attach the > files, but I keep getting this error: > > Server: Msg 3624, Level 20, State 1, Line 1 > > Location: recovery.c:2693 > Expression: seenCkptEnd > SPID: 12 > Process ID: 133 > > Connection Broken > > Any Ideas??!?!?!?!!? > > Thanks > > Sam > > > > ----- Original Message ----- > From: "Tore Bostrup" <[EMAIL PROTECTED]> > To: "ActiveServerPages" <[EMAIL PROTECTED]> > Sent: Thursday, October 24, 2002 5:00 PM > Subject: Re: (Suspect) SQL server database > > > > A database may become suspect for different reasons. The database may > have > > run out of space, one of the files may be corrupt, etc. > > > > Look up sp_add_data_file_recover_suspect_db, > > sp_add_log_file_recover_suspect_db or sp_resetstatus in your BOL. > > > > HTH, > > Tore. > > > > ----- Original Message ----- > > From: "Sam Thompson" <[EMAIL PROTECTED]> > > To: "ActiveServerPages" <[EMAIL PROTECTED]> > > Sent: Thursday, October 24, 2002 7:10 AM > > Subject: (Suspect) SQL server database > > > > > > > Yo, > > > im using SQL Server 7, and viewing my list of databases, one of them is > > > grayed out and has (Suspect) written next to it. What does this mean? > How > > do > > > I find out why it has been marked as suspect? > > > > > > Thanks > > > > > > Sam > > > > > > > > > --- > > > You are currently subscribed to activeserverpages as: > > [EMAIL PROTECTED] > > > To unsubscribe send a blank email to > > %%email.unsub%% > > > > > > > > > --- > > You are currently subscribed to activeserverpages as: > [EMAIL PROTECTED] > > To unsubscribe send a blank email to > %%email.unsub%% > > > > > --- > You are currently subscribed to activeserverpages as: [EMAIL PROTECTED] > To unsubscribe send a blank email to %%email.unsub%% > --- You are currently subscribed to activeserverpages as: [EMAIL PROTECTED] To unsubscribe send a blank email to %%email.unsub%% --- You are currently subscribed to activeserverpages as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED]
