Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
purisqlserver
Yak Posting Veteran
73 Posts |
 Posted - 2003-05-26 : 06:19:39
|
| Hi,For some reason, the transaction log file growing very quicklyand now the log file is full.Tried to shrink database, but it says there no entry for the database in the sysdatabases.Not able detached the db, for the same reason.Thanx......... |
|
|
Wanderer
Master Smack Fu Yak Hacker
1168 Posts |
Posted - 2003-05-26 : 06:27:17
|
| First, check space on drive where the DB log file is written. If it's full, try and free some space.Second, check DB properties to ensure that LOG size growth is not restricted. If it is restricted, remove restriction.Third - review size of log file. Is it excessive ? If yes, take a full db backup, then do a backup log DBNAME with truncate_only - this will truncate your log.At this point in time, you should be able to work, unless you have no space on the drive, and the data file wants to grow.Review BOL regards shrinking your log file, I have had some strange problems with this, until I found a wonderful SP (not certain of the author), called SP_FORCE_SHRINK_LOG.NOTE - I give no guarantee's, esp re: the SP referred to, but it has worked very well for me.HTH*#&#* *#&#* *#&#* *#&#* Chaos, Disorder and Panic ... my work is done here! |
 |
|
|
purisqlserver
Yak Posting Veteran
73 Posts |
Posted - 2003-05-26 : 07:23:07
|
| Hi ,Thanx for the reply.tried to backup log, here is the error"the databse could not be located in sysdatabases. make sure the name is correct"the db is not located in sysdatabases???? |
|
|
|
Wanderer
Master Smack Fu Yak Hacker
1168 Posts |
Posted - 2003-05-26 : 08:25:52
|
| Hi Puri,HmmmObvious question first - you didn't make a typo ?Oh - I notice you say you fail backing up the log? Did the DB backup go thro ok ?Assuming that's not the error. When you go into EM, does it display the DB ? If so, is it listed as suspect, or loading ? If so, you *may* be able to repair it - look into the DBCC checkdb etc. options.What does the error log say ? It *sounds* like you may have issue with the db it self.Can you turn SQL off ? If so, try and copy the MDF to another machine, and see if you can do a SP_attach_single_file_db :sp_attach_single_file_db [ @dbname = ] 'dbname' , [ @physname = ] 'physical_name'That should create get SQL to create it's own LDF for the DB - but obviously you've lost all your log data, and so the actual DB data *may* be suspect, dependant on how you use it, if you are using properly atomic transactions etc.I'm afraid it doesn';t sound too good, hopefully someone smart has a good fix ?HTH*#&#* *#&#* *#&#* *#&#* Chaos, Disorder and Panic ... my work is done here!Edited by - wanderer on 05/26/2003 08:27:40 |
|
|
|
|
|
|
|
|
transaction log full error