October 13, 2003 at 3:58 am
my db goes into suspend mode
try to tell me to make into active mode
balaji ramanar
balaji ramanar
October 13, 2003 at 5:58 am
I never heard about a suspend mode.
In case you meant suspect status, use sp_resetstatus database-name
But you really should find out what is the cause from the sqlserver logs before you do so.
October 14, 2003 at 2:59 am
if your whole server enters suspend mode, you should consider looking for a new job ... 😉
October 15, 2003 at 6:29 am
ok .. I think the problem is that you have the MDB file only ( the LDB has a problem ) ...
if you still have the MDB you can get your DB work (but the transactions in Log file will not be added )
I hope these steps will help u.
-----------------------------------
Restoring databases when only data file available
A procedure too re-attach a data( MDF ) file when the log file is missing or not recoverable.
---------------------------------------------------------------------------
shutdown sql
move the current database file or rename it
restart sql server
create a new database of the same name and log file and location as the old database and log file
get rid of the old database.
you may be able to right click delete it in this situation or used sp_removedb
create a new database of the right size and shape with correct log and data file locations
stop sql
rename the new databases.mdf or delete it if you don't have enough space - do not touch the .ldf
move back in the old database .mdf file or rename it back again
restart sql server
it should come up suspect
--------------------------------
1. From a query window, set the status so that you can update the system
tables by running the following query:
use Master
go
sp_configure "allow", 1
go
reconfigure with override
go
2. Then set the status of the DB that is giving you the problem (XXXXX) into
Emergency Mode by running the following query:
update sysdatabases set status = 32768 where name = '<DBName>'
go
checkpoint
go
shutdown with nowait
go
3. Go into the data directory (MSSQL7\DATA) and rename the log file associated
the DB in question (XXXX.ldf) to some
temporary name, such as XXXX.TMP.
4. Exit the query window.
5. Then start up SQL Server from a DOS command window by issuing:
sqlservr -c -T3608 -T4022.
6. Bring up another query window and verify that the DB is in emergency mode
by issuing:
select Name, Status from Sysdatabases where name = '<DB_Name>'
7. Verify that the status is 32768. If it is, then issue the query:
dbcc traceon(3604)
dbcc rebuild_log('<DB_Name>','<log_filename>') <--- You will need the quotation marks
REBUILD_LOG should take less than 5 minutes even on a very large
database. It should complete with the message
DBCC execution completed
8. Take the database out of bypass recovery mode by issuing the command
update sysdatabases set status = 0 where name = '<DBName>'
9. Exit the query window and then shutdown (Ctrl-C in the DOS window) and
restart SQL server. Verify the status of the
database by running DBCC NEWALLOC and DBCC CHECKDB on the database.
hope this help u
Alamir Mohamed
Alamir Mohamed
Alamir_mohamed@yahoo.com
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply