Exponential Growth in SQL log files (.LDF)

We have a customer running our software that is experiencing a strange
occurence. We have thousands of customers and this is the only one that
has this issue. Recently, we upgraded him from using MSDE to Full SQL.
Since, any time he performs certain tasks in our software, the log file
will grow by the GB before our eyes until it fill the drive and shuts
down. We have exhausted our ideas as to what could be causing this. We
have configured all of the options for maximum efficiency. We are
band-aiding the problem by regularly deleting the log file and
generating a new one upon reconnecting. Has anyone else had a similar
experience with SQL that might provide some leads?Doug wrote:
> We have a customer running our software that is experiencing a strange
> occurence. We have thousands of customers and this is the only one that
> has this issue. Recently, we upgraded him from using MSDE to Full SQL.
> Since, any time he performs certain tasks in our software, the log file
> will grow by the GB before our eyes until it fill the drive and shuts
> down. We have exhausted our ideas as to what could be causing this. We
> have configured all of the options for maximum efficiency.
What recovery model are you / they using?

> We are
> band-aiding the problem by regularly deleting the log file and
> generating a new one upon reconnecting. Has anyone else had a similar
> experience with SQL that might provide some leads?
Um, that's a strange way to limit growth of TX log. The usual approach
is to have regular backups. If you don't do that, you can at least use
BACKUP <db> LOG WITH NO_LOG and DBCC SHRINKFILE (see BOL).
Kind regards
robert|||Does the log growth happen when he "performs certain tasks" or does it occur
off hours (perhaps when you have jobs such as database maintenance plans
scheduled)?
What recovery model is the database using?
What is your database backup strategy?
Keith Kratochvil
"Doug" <dclark@.cyrious.com> wrote in message
news:1143216876.301135.47350@.u72g2000cwu.googlegroups.com...
> We have a customer running our software that is experiencing a strange
> occurence. We have thousands of customers and this is the only one that
> has this issue. Recently, we upgraded him from using MSDE to Full SQL.
> Since, any time he performs certain tasks in our software, the log file
> will grow by the GB before our eyes until it fill the drive and shuts
> down. We have exhausted our ideas as to what could be causing this. We
> have configured all of the options for maximum efficiency. We are
> band-aiding the problem by regularly deleting the log file and
> generating a new one upon reconnecting. Has anyone else had a similar
> experience with SQL that might provide some leads?
>sql