2 typo
source | link

The reccomendedrecommended approach is to choose a relatively quiet time (i.e. minimal log activity) then do the following:

  1. Backup the log
  2. Shrink the log file with DBCC SHRINKFILE with TRUNCATEONLY to get it as small as possible
  3. Run ALTER DATABASE MODIFY FILE to re-size the log to an appropriate size

Appropriate size for the log is of course dependent on your observations of log usage for each database.

The reccomended approach is to choose a relatively quiet time (i.e. minimal log activity) then do the following:

  1. Backup the log
  2. Shrink the log file with DBCC SHRINKFILE with TRUNCATEONLY to get it as small as possible
  3. Run ALTER DATABASE MODIFY FILE to re-size the log to an appropriate size

Appropriate size for the log is of course dependent on your observations of log usage for each database.

The recommended approach is to choose a relatively quiet time (i.e. minimal log activity) then do the following:

  1. Backup the log
  2. Shrink the log file with DBCC SHRINKFILE with TRUNCATEONLY to get it as small as possible
  3. Run ALTER DATABASE MODIFY FILE to re-size the log to an appropriate size

Appropriate size for the log is of course dependent on your observations of log usage for each database.

1
source | link

The reccomended approach is to choose a relatively quiet time (i.e. minimal log activity) then do the following:

  1. Backup the log
  2. Shrink the log file with DBCC SHRINKFILE with TRUNCATEONLY to get it as small as possible
  3. Run ALTER DATABASE MODIFY FILE to re-size the log to an appropriate size

Appropriate size for the log is of course dependent on your observations of log usage for each database.