|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Today @ 2:33 PM
Points: 5,201,
Visits: 11,150
|
|
ravi@sql (12/3/2012) ya maxsize is given for autogrowth What are the size details for the log currently? Do you have any long running transactions?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs"
|
|
|
|
|
SSC Journeyman
      
Group: General Forum Members
Last Login: Monday, May 13, 2013 5:44 AM
Points: 88,
Visits: 182
|
|
Thank you all .
Regards, Ravi@sql
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Friday, May 03, 2013 3:06 AM
Points: 42,
Visits: 285
|
|
ravi@sql (12/3/2012) ok cant i point my log file path any other drive ? if yes how can i do that ? pls share the query ?
Thanks Ravi@sql
If you want to move the existing t-log file to different location then, follow the below steps: 1. Run ALTER DATABASE command and change location of ldf file 2. Take database offline 3. Move the physical file from old location to new location. 3. Bring database online
You can also try to add second log file to your database
USE [master] GO ALTER DATABASE [DB_NAME] ADD LOG FILE ( NAME = N'second_log_file', FILENAME = N'D:\LOG_FILES\second_log_file.ldf' , SIZE = 1024KB , FILEGROWTH = 10%) GO
|
|
|
|
|
Old Hand
      
Group: General Forum Members
Last Login: 2 days ago @ 9:49 PM
Points: 323,
Visits: 960
|
|
arunyadav007 (12/3/2012)
USE MASTER GO DBCC FREESESSIONCACHE WITH NO_INFOMSGS GO DBCC FREESYSTEMCACHE 'ALL' GO
and how does it will help to manage the log space ?
you are just adding trouble to existing issues
----------------------------------------------------------------------------- संकेत कोकणे
|
|
|
|
|
Old Hand
      
Group: General Forum Members
Last Login: 2 days ago @ 9:49 PM
Points: 323,
Visits: 960
|
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Today @ 12:59 PM
Points: 37,640,
Visits: 29,895
|
|
arunyadav007 (12/3/2012) If not, you can try this
USE MASTER GO DBCC FREESESSIONCACHE WITH NO_INFOMSGS GO DBCC FREESYSTEMCACHE 'ALL' GO USE (YOURDBNAME) GO DBCC SHRINKFILE (N'LOGFILENAME', 0, TRUNCATEONLY) GO DBCC SHRINKFILE (N'LOGFILENAME' , 1024) GO
Well, I suppose that you can try that, but since none of those will help in the slightest with a full transaction log and may in fact make the scenario worse, I personally would recommend that you don't try any of those commands.
Gail Shaw Microsoft Certified Master: SQL Server 2008, MVP SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter We stand on the bridge and no one may pass
|
|
|
|