How can U decrease the Log Size in MS-SQL server?

Question

Hello friends,
                I am in Big Trouble. I have a Problem.we are Using MS-SQL server 8.00.924. The Database Log size is almost Full.But BackUps are not Done successfully ,,How to Shink the Log file,, Any body pls help me I will give more Points.
Regards,
Balaram

Answer 1

Hi Balaram,
Please see the link and scripts which is given hereunder.
http://support.microsoft.com/kb/873235
You can check this method also.
Method 1 – Delete the Log (LDF) File
Although this method is simple, it is not supported by Microsoft®.  Additionally, it may not work for all systems.  Follow these steps to try the simple method on your system.
Ensure that no users are logged into the database.
Open Query Analyzer or another program to execute SQL scripts.  Ensure that “dsdbase” is not selected in the drop-down “DB” list.
Open and run the script DETACH.sql.  This script detaches the DataLyzer® database from the SQL server database.
Make a backup copy of the DSdbase_Data.MDF and DSdbase_Log files.
Rename the DSdbase_log file to another name, for instance backup_DSdbase_log.
Open and run the script ATTACHMDF.sql.  This script re-attaches the DataLyzer® database to the SQL database without attaching the log file.  NOTE: If your database is not stored in the location c:mssql7data change the SQL script to reflect the location of your DSdbase file.
If the script runs successfully, a new DSdbase_Log file will automatically be created to the original size specified when creating the database.  It is suggested that users keep the backup copies made of their database and log files for several days to ensure an available backup if anything happens to the new log file.
If the script does not run successfully, method 1 will not work for your current DataLyzer® Spectrum database.  This is because your database’s structure is dependent on the logfile.  In this case, re-name the original log file back to DSdbase_log.  Run the script ATTACH.sql and again change the file location to the location of your DataLyzer® database, if necessary.  When the database is successfully re-attached, try using method 2 to shrink the log file.
Method 2 – Truncate and Shrink the Log (LDF) File
Although this method of shrinking the log file is more complicated, it is supported by Microsoft®, and it will work for almost all systems.  Follow these steps:
Ensure no users are logged into the database.
Open Query Analyzer or another program to execute SQL scripts.  Ensure that “dsdbase” is not selected in the drop-down “DB” list.
If you have already tried method 1, or if you have a current backup of you database and log file, skip to step 7
Open and run the script DETACH.sql.  This script detaches the DataLyzer® database from the SQL server database.
Make a backup copy of the DSdbase_Data.MDF and DSdbase_Log files.
Open and run the script ATTACHMDF.sql.  This script re-attaches the DataLyzer® database to the SQL database.  NOTE: If your database is not stored in the location c:mssql7data, change the SQL script to reflect the location of your DSdbase file.
Select “dsdbase” from the drop down “DB” list in the program you are using to execute the SQL scripts.
8.      Run VIEW2LDF.sql.  Below is an excerpt similar to what will be displayed on your screen: FileId   FileSize    StartOffset    FSeqNo      Status   Parity  CreateTime
2          1245184   819              1292   0          64         1999-12-15 10:25:13.597
2          1245184   1253376       1225    0          128        1999-11-19 09:12:57.743
2           1245184   2498560       1224    0          128     1999-11-19 09:12:23.82
2          1499136   3743744       1318    2          64         1999-12-15 10:25:36.880
Locate the “2” in the status column.  The location of the “2” determines where the active portion of the log is.
If the 2 is in the bottom half of the log, open and run the SQL script MOVE2LOOP.sql.  This script is an infinite loop used to move the active portion of the log.
Re-Run the VIEW2LDF.sql script to make sure that the 2 is now located in the first half of the script. 
Run the script SHRINKLOG.sql to reduce the size of the database.
Run the script VIEW2LDF.sql to view the new status of the log file.  You should notice that the number of lines is significantly smaller than it originally was.
If you wish to further reduce the size of the database, repeat steps 8 through 13.
Text Context of SQL Scripts
ATTACHMDF.sql
sp_attach_db @dbname=N'dsdbase', @filename1=N'c:mssql7datadsdbase_data.mdf'
ATTACH.sql
sp_attach_db @dbname=N'dsdbase', @filename1=N'c:mssql7datadsdbase_data.mdf',
@filename2=N'c:mssql7datadsdbase_log.ldf'
Detach.sql
sp_detach_db dsdbase
MOVE2LOOP.sql
USE DSDBASE
GO
CREATE TABLE VIRTUAL_LOG_FILE_WRAPPER (CHAR1 CHAR(4000))
GO
DECLARE @I INT
SELECT @I = 0
WHILE (1=1)
BEGIN
WHILE (@I < 100)
BEGIN
INSERT VIRTUAL_LOG_FILE_WRAPPER VALUES ('A')
SELECT @I = @I + 1
END
TRUNCATE TABLE VIRTUAL_LOG_FILE_WRAPPER
BACKUP LOG DSDBASE WITH TRUNCATE_ONLY
END
SHRINKLOG.sql
DBCC SHRINKFILE (DSDBASE_LOG, TRUNCATEONLY)
BACKUP LOG DSDBASE WITH TRUNCATE_ONLY
VIEW2LDF.sql
DBCC LOGINFO(DSDBASE)
Regards,
Anil