Answer / nixo

You will have to backup the Transaction Log. You may
schedule a job which backs up the log every night.

Backup the log before shrinking the database.

Answer / sujay kumar

You should schedule the job for shrinking the database log.
Sometime, it looks impossible to shrink the Truncated Log
file. Following code always shrinks the Truncated Log File
to minimum size possible.
USE DatabaseName
GO
DBCC SHRINKFILE(<TransactionLogName>, 1)
BACKUP LOG <DatabaseName> WITH TRUNCATE_ONLY
DBCC SHRINKFILE(<TransactionLogName>, 1)
GO

Answer / rama krishna

try allocate a room for taht log file

Answer / rajesh ranjan

In MS SQL Server 2005
select * from sys.database_files
Above Query will return .mdf , .ldf file & all other
details releted to these files of the database
After that you should run following DBCC Statement

DBCC Shrinkfile(Log_file_name.ldf,1,truncateonly)

Answer / rajkumar

You should schedule the job for shrinking the database log.
or you have to minimize the growth of the log file.

What are all new concepts in SQL Server 2008? That is Exactly Difference between 2005 to 2008

2 Answers   IBM,

1.how to find the dead lock in sql server? 2.How to fine the memory leaks in sql server? 3.suppose transaction log file increasing what action will take ?

0 Answers  

What is purpose of normalization?

0 Answers  

What is a Stored Procedure?

8 Answers  

what protocol both networks use? : Sql server database administration

0 Answers  

Can we create nonclustered index in a table without creating a clustered index

1 Answers  

What is the difference between login and a user?

13 Answers   CTS, TCS,

If user is owning any SQL Objects, can we drop that user

0 Answers  

Mention the 3 ways to get a count of the number of records in a table.

0 Answers  

Differentiate between sql temp table vs table variable?

0 Answers  

Explain where clause?

0 Answers  

What is indexed view? How to create it?

0 Answers