log grows after shrinking

I have truncated the log file and then used the DBCC Shrinkfile command to
reduce to physical size of the file. This seemed to work perfectly.
However, after a few days the transaction log file returns to its huge size
(8Gb). Has anyone else experienced this problem and if so can you suggest a
solution?
Thanks in advance, Simon.
Simon
It sounds like you have your database in full recovery mode, but you are not
performing transaction log backups.
If you want to use your transaction logs as part of your backup and recovery
strategy, (recommended for production systems) you need to back them up
regularly. Something like every 15 or 30 minutes (or whatever is suitable for
your requirements) during your business day.
If you really do not want your transaction logs, set your recovery mode to
simple.
Hope this helps
John
"Simon" wrote:

> I have truncated the log file and then used the DBCC Shrinkfile command to
> reduce to physical size of the file. This seemed to work perfectly.
> However, after a few days the transaction log file returns to its huge size
> (8Gb). Has anyone else experienced this problem and if so can you suggest a
> solution?
> Thanks in advance, Simon.
|||Even in SIMPLE RECOVERY mode, the transaction log file(s) will grow to about
the size of the data portion of your data files if you are doing regular
maintenance with the DB maintenance wizard. The reason is that the
Organization task will serially reorganize your data tables. The largest
table will dictate the amount of free space in your data file and the size
of transaction log for normal operations.
If you do not want your tranaction log to be bigger than this, you need to
be in SIMPLE RECOVERY or backup the tlogs frequently if in FULL RECOVERY or
BULK INSERT RECOVERY modes.
How big is your data files?
Sincerely,
Anthony Thomas

"John Bandettini" <JohnBandettini@.discussions.microsoft.com> wrote in
message news:9B630219-A733-4032-87DF-45B858628C31@.microsoft.com...
Simon
It sounds like you have your database in full recovery mode, but you are not
performing transaction log backups.
If you want to use your transaction logs as part of your backup and recovery
strategy, (recommended for production systems) you need to back them up
regularly. Something like every 15 or 30 minutes (or whatever is suitable
for
your requirements) during your business day.
If you really do not want your transaction logs, set your recovery mode to
simple.
Hope this helps
John
"Simon" wrote:

> I have truncated the log file and then used the DBCC Shrinkfile command to
> reduce to physical size of the file. This seemed to work perfectly.
> However, after a few days the transaction log file returns to its huge
size
> (8Gb). Has anyone else experienced this problem and if so can you suggest
a
> solution?
> Thanks in advance, Simon.

log grows after shrinking

I have truncated the log file and then used the DBCC Shrinkfile command to
reduce to physical size of the file. This seemed to work perfectly.
However, after a few days the transaction log file returns to its huge size
(8Gb). Has anyone else experienced this problem and if so can you suggest a
solution?
Thanks in advance, Simon.Simon
It sounds like you have your database in full recovery mode, but you are not
performing transaction log backups.
If you want to use your transaction logs as part of your backup and recovery
strategy, (recommended for production systems) you need to back them up
regularly. Something like every 15 or 30 minutes (or whatever is suitable for
your requirements) during your business day.
If you really do not want your transaction logs, set your recovery mode to
simple.
Hope this helps
John
"Simon" wrote:
> I have truncated the log file and then used the DBCC Shrinkfile command to
> reduce to physical size of the file. This seemed to work perfectly.
> However, after a few days the transaction log file returns to its huge size
> (8Gb). Has anyone else experienced this problem and if so can you suggest a
> solution?
> Thanks in advance, Simon.|||Even in SIMPLE RECOVERY mode, the transaction log file(s) will grow to about
the size of the data portion of your data files if you are doing regular
maintenance with the DB maintenance wizard. The reason is that the
Organization task will serially reorganize your data tables. The largest
table will dictate the amount of free space in your data file and the size
of transaction log for normal operations.
If you do not want your tranaction log to be bigger than this, you need to
be in SIMPLE RECOVERY or backup the tlogs frequently if in FULL RECOVERY or
BULK INSERT RECOVERY modes.
How big is your data files?
Sincerely,
Anthony Thomas
"John Bandettini" <JohnBandettini@.discussions.microsoft.com> wrote in
message news:9B630219-A733-4032-87DF-45B858628C31@.microsoft.com...
Simon
It sounds like you have your database in full recovery mode, but you are not
performing transaction log backups.
If you want to use your transaction logs as part of your backup and recovery
strategy, (recommended for production systems) you need to back them up
regularly. Something like every 15 or 30 minutes (or whatever is suitable
for
your requirements) during your business day.
If you really do not want your transaction logs, set your recovery mode to
simple.
Hope this helps
John
"Simon" wrote:
> I have truncated the log file and then used the DBCC Shrinkfile command to
> reduce to physical size of the file. This seemed to work perfectly.
> However, after a few days the transaction log file returns to its huge
size
> (8Gb). Has anyone else experienced this problem and if so can you suggest
a
> solution?
> Thanks in advance, Simon.sql

LOG File size is 18GB

Hi everyone,
In one of my databases, the size of the LOG has gone upto 18GB. "Truncate
Log" doesn't help. How do I reduce the physical size of the file?
Abhay
Abhay
Perfom BACKUP LOG ..... and then DBCC SHRINKFILE commad (for more details
please refer to BOL)
"Abhay Sobti" <abhay@.stansoftware.com> wrote in message
news:%23OS6JH9nEHA.3668@.TK2MSFTNGP15.phx.gbl...
> Hi everyone,
> In one of my databases, the size of the LOG has gone upto 18GB. "Truncate
> Log" doesn't help. How do I reduce the physical size of the file?
> Abhay
>
|||Enabling the "Truncate log" is just part of the job. You also need to
shrink the file. Check BOL for dbcc shrinkfile.
Adi
|||Fix your clock.
"Abhay Sobti" <abhay@.stansoftware.com> wrote in message
news:%23OS6JH9nEHA.3668@.TK2MSFTNGP15.phx.gbl...
> Hi everyone,
> In one of my databases, the size of the LOG has gone upto 18GB. "Truncate
> Log" doesn't help. How do I reduce the physical size of the file?
> Abhay
>
|||Hi
Do the following tasks:
BACKUP LOG <database name> WITH TRUNCATE_ONLY
DBCC SHRINKDATABASE(<database name>)
Regards
Eli
Abhay Sobti wrote:
> Hi everyone,
> In one of my databases, the size of the LOG has gone upto 18GB. "Truncate
> Log" doesn't help. How do I reduce the physical size of the file?
> Abhay
>

LOG File size is 18GB

Hi everyone,
In one of my databases, the size of the LOG has gone upto 18GB. "Truncate
Log" doesn't help. How do I reduce the physical size of the file?
AbhayAbhay
Perfom BACKUP LOG ..... and then DBCC SHRINKFILE commad (for more details
please refer to BOL)
"Abhay Sobti" <abhay@.stansoftware.com> wrote in message
news:%23OS6JH9nEHA.3668@.TK2MSFTNGP15.phx.gbl...
> Hi everyone,
> In one of my databases, the size of the LOG has gone upto 18GB. "Truncate
> Log" doesn't help. How do I reduce the physical size of the file?
> Abhay
>|||Enabling the "Truncate log" is just part of the job. You also need to
shrink the file. Check BOL for dbcc shrinkfile.
Adi|||Fix your clock.
"Abhay Sobti" <abhay@.stansoftware.com> wrote in message
news:%23OS6JH9nEHA.3668@.TK2MSFTNGP15.phx.gbl...
> Hi everyone,
> In one of my databases, the size of the LOG has gone upto 18GB. "Truncate
> Log" doesn't help. How do I reduce the physical size of the file?
> Abhay
>|||Hi
Do the following tasks:
BACKUP LOG <database name> WITH TRUNCATE_ONLY
DBCC SHRINKDATABASE(<database name>)
Regards
Eli
Abhay Sobti wrote:
> Hi everyone,
> In one of my databases, the size of the LOG has gone upto 18GB. "Truncate
> Log" doesn't help. How do I reduce the physical size of the file?
> Abhay
>