sp_resetstatus
If that does not work you might try the following::
1. Turn off the SQL Server,
2. Copy the data file to a secure location on the drive
3. Turn on the SQL Server
4. Create a new database, call it foo or something
5. Turn off the database
6. Look in the /Data/ directory (or wherever you place your DB's). You
should see the FOO Data and Log files. Overwrite your backup data file you
moved earlier in Step 2 and replace it exactly with the Data name of Foo.
7. Turn on the database, and try to access FOO. That should work
That should work, at least it has for me in the past
<http://intranet>
Stephen E. Schuster
PeopleSoft Administrator
2000 Ashland Drive
Ashland, KY 41101
Office Phone 606.920.7447
Cell Phone 606.831.4590
-----Original Message-----
From: Eric Creese [mailto:[EMAIL PROTECTED]
Sent: Monday, January 05, 2004 10:10 AM
To: CF-Talk
Subject: RE: OT-SQL Data file issue
Unfortunately the last back up I had was from 11/28. This all happened
yesterday. And yes the .ldf file was deleted.
-----Original Message-----
From: Tony Weeg [mailto:[EMAIL PROTECTED]
Sent: Monday, January 05, 2004 9:10 AM
To: CF-Talk
Subject: RE: OT-SQL Data file issue
you deleted the ldb file?
uhhh, hmm, do you have a backup?
tw
-----Original Message-----
From: Eric Creese [mailto:[EMAIL PROTECTED]
Sent: Monday, January 05, 2004 10:06 AM
To: CF-Talk
Subject: OT-SQL Data file issue
Ok I made a big mistake. I had a database set to FULL thinking it was set to
SIMPLE and forgot to set up a job to truncate the transaction log. Needless
to say, the transaction log grew huge (14g) and sucked up all my memory. So
I took the database offline and deleted the file and replaced it with a new
empty one. Well that made my database suspect. How can I fix this?
_____
_____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
