1) Autogrowth of 1MB is BAD!!!!! You created what . . . 4000 file fragments
spread over your hard drive with that, in one night? Make it s standard
practice to set appropriate file size and file growth increments in ALL your
databases. There is significant performance to be gained by preventing (or
eliminating) os-level disk fragmentation.
2) Great Plains has any number of scheduled jobs it does. I would look at
the job history table (or whatever table has the HUGE number of rows) and
determine which one or ones are most likely stuck in an infinite loop. Then
address with MS support. Also check the last run status/next run date
columns in Enterprise Manager for the jobs and see if something has a 1 min
cycle time. The jobs I am looking at now for Great Plains have a 30 minute
rerun time.
--
TheSQLGuru
President
Indicium Resources, Inc.
[quoted text, click to view] "Curt Spanburgh" <CurtSpanburgh@discussions.microsoft.com> wrote in message
news:8E1E6D69-F8BD-4743-85B2-0B6B93CBD8B6@microsoft.com...
> I've encountered a clients SQL Instance that experiences a large growth of
> the MSDB Transaction log.
>
> At one time the MDF was 14 MB and the log was 25 GB.
>
> I used T-SQL commands to shink the file.
>
> Auto growth is set to 1 mb.
>
> This morning is was 4 GB.
>
> I check for uncommitted transactions with DBCC Opentran.
>
> Nothing in there.
>
> There are nightly backups. A weekly backup and a monthend backup.
>
> IT's a Dynamics Great Plains server.
>
> Anyone experience this?
>
