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.

Explain the cursor lock types?

0 Answers  

Do you know what is normalization of database? What are its benefits?

0 Answers  

What is the use of =,==,=== operators?

0 Answers  

What is Cross Join

3 Answers  

Explain what are the restrictions that views have to follow? : SQL Server Architecture

0 Answers  

What is policy management?

0 Answers  

Can you have a nested transaction?

4 Answers   HCL,

How many database files are there in sql server 2000?what are they?

0 Answers  

What is mean by "fill factor" ? and what is mean by "Index "in sql?

1 Answers   iGate, Logica CMG,

What is a Join in SQL Server?

3 Answers  

Determine when to use stored procedure to complete sql server tasks?

0 Answers  

what is a transaction and what are acid properties? : Sql server database administration

0 Answers