SQL Server Log File size problem

L

lauriemc

Active member
Joined
Feb 2, 2007
Messages
25
A little background on my problem: we have a pilot program in the govt agency where I work where we are testing a vb.net Windows Application with a LOCAL SQL server database. The people who go out on the road do not have any inter/intranet connection, once they are on the road they have static data. It is used primarily for inquiry purposes, some printing. They also do not have SQL Enterprise or any SQL management tools.

The data is refreshed from our mainframe computer in the morning, when they plug into the intranet through their shop. We dont do a backup on the individual laptop, rather we keep a backup on another computer here in the main office. From that computer, if our roving laptop is plugged into the intranet, we can shrink the logfile.

I am finding that the size of logfile seems to impact the length of time it takes to download the necessary data from the mainframe. It is a clean wipe, btw, each table is truncated, then reloaded.

My question is this: is there any way to programatically shrink that log file from the vb Windows application? I would like to see that done before the download begins, and without our road people having to call me and ask that it be done.

Thank you, laurie mc
 
We did this in the database itself, and while it seems to prevent the log file from growing to gigantic proportions, it doesnt prevent it from growing.

I did find the kind of tool I wanted, which I put in a stored procedure.

The sp code is simply this:

DBCC SHRINKDATABASE (dbname, 10)
GO

I call it from the program before and after the upload / download, and it works like a charm, shrinks that log file right down.

Thanks, laurie mc
 
Back
Top