| |
microsoft.public.sqlserver.server |
Venkat > I know the source of the problem is deleting and inserting records for > So I am thinking to write sql job whose job is: > This job runs every day at 4:00 AM. > I alreday have a full backup job which runs at 3:00 AM daily. Probably I > Does any one experainced this? is it write thing to shrink file every day? > Thanks,
What is recovery model of your db? Its possible it has FULL recovery mode.
If so, please start performing BACKUP LOG to move an inactive transactions
to be moved on the disk. I'd suggest you read about recovery models in the
BOL to understand their impact on the database....
news:uWnh13jZIHA.4712@TK2MSFTNGP05.phx.gbl...
> My sql server database log file size growing rapidly, 1 GB by every week.
> I have a service running every 2 hours which deletes and inserts some
> data, say around 5000 records for every two hours.
> every 2 hours. I want to go for a densive mechansim for this, that is: i
> don't want to change the service code (for example using TRUNCATE
> statement instead of DELETE statement) for any reason.
> Backup transaction log and shrink log file.
> will add the above commnads (backup transaction log and then shrink log
> file) to the full backup job schedule as another step.
> Venkat