January 17, 2006 at 12:57 pm
Hi,
We are on a MSSQL San Server. At one time the one drive which has system, database, and database backups files was very full due to big transaction log files generated, causing the system to crash. After space was added to the drive and functioning restored, the SQL Server Log subdirectories suche as: Current, Archive are very big, cannot click to be opened. Their sizes are close to 0.3 GB and 0.8 GB. Any attempt to click open these subdirectories will cause entire Enterprise manager to ' Not Responding' and have to close it. Any suggestion to solve this problem is very much appreciated.
Thanks
January 17, 2006 at 1:04 pm
Log files are just text files. Try to connect by mapping a drive from your computer and browse to the directory where the logs are.
Regards,Yelena Varsha
January 18, 2006 at 4:26 am
eek - it sounds like you have a few problems !!
A couple of suggestions here
- ensure your database transaction logs are backed up or databases are in simple mode. Adding space to a drive that contains t-logs isn't an appropriate way to manage t-logs
storing t-logs (ldf) and data files (mdf) on the same array will slow performance considerably
storing backups and data on the same array is asking for a disaster! what happens if your tape backup fails and you need to recover?
you can clear down the existing logs with sp_cycle_errorlog command in query analyser
(you may need to run it several times to clear all of the old logs) i'd recommending running theis command once a week in order to avoid large log files (which enterprise mansager hates) - you can take a backup of these files before you do this and open them with notepad if you really want to sort through millions of lines of log
MVDBA
January 18, 2006 at 4:36 am
Hi
I think u should cycle error logs regularly according to ur needs. U can schedule a job to run according to ur requirements. U can use sp_cycle_errorlog command.
To open the existing log files u can use any text editor like Textpad and open that in it
or u can also use
sp_readerrorlog command to find out for errors
syntax
sp_readerrorlog 1, logfilepath, startline, keyword
regards
sejal gudhka
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply