Re: SQL log file running rampant by Matt
Matt
Fri Jan 14 16:02:18 CST 2005
I would look for jobs in Enterprise Manager that seem to be related to Mobile
and check the schedules.
As for the backups, I usually schedule mine with the Database Maintenance
Wizards. They do a pretty good job of scheduling and running the backups. If
the log is growing that fast, I'd consider running the log backup multiple time
during the day.
If you are bent on doing this with scripts, refer to the SQL Books Online for
syntax on backing up the log.
Matt Parks
MVP - Microsoft CRM
----------------------------------------
----------------------------------------
On Fri, 14 Jan 2005 11:15:03 -0800, Dave McGuire
<onayamspaydavid_mcguire@hotmail.com> wrote:
Simple Recover: Done. :)
Jobs hitting the DB: How can I tell what's hitting it? I can't seem to find
anything in either SQL Enterprise or Scheduled Tasks.
Backing up the log: I have this T-SQL task that goes through and runs a
BACKUP command against all applicable DBs. Do you have a template that I can
use, tweak, and add log backups to this mondo script?
"Matt Parks" wrote:
> Dave,
>
> First things first.....
>
> Change the properties of that database to Simple Recover mode. This will at
> least stop the current loggin activity and give you an option to shrink the file
> to a more manageable size. Afterwards, make sure you have a full backup of the
> database as well.
>
> Next step is to find out what is hitting the database with so much activity. I
> haven't installed Mobile yet, so I'm not sure what it might be doing. But look
> for any jobs that may be scheduled to run at a high frequency against that
> database. It seems odd that there should be a lot of activity, especially in
> the metabase though.
>
> CRM doesn't use the DB logs in any way shape or form any more than any
> application does. The log is maintained by SQL and the applications have no
> idea it even exists. So you can treat this the same as any other transaction
> log file. I usually don't worry about logs on my test servers, so I almost
> always first set recovery to Simple on them.
>
> If you want to maintain the logs for recovery, then you need to make sure you
> have a log backup scheduled periodically as well as the complete backup. A
> complete backup will not backup the log file itself and it will continute to
> grow. When you do a log backup, it will free up the space being used by the
> transaction records you just backed up.
>
> Matt Parks
> MVP - Microsoft CRM
>
> ----------------------------------------
> ----------------------------------------
> On Fri, 14 Jan 2005 08:47:10 -0800, Dave McGuire
> <onayamspaydavid_mcguire@hotmail.com> wrote:
>
> On our development server,
> Adventure_Works_Cycle_MSCRMMobileMetabase_log.LDF
> is going nuts. it's at 1.7GB and growing at an alarming rate (about 500MB /
> Day). The corresponding database is only 5MB! :o
>
> I've tried shrinking it. I've tried forcing a backup of the transactions.
> I've asked our SQL gurus who don't know. I'm afraid of deleting the
> transaction log for two reasons:
> 1) I don't know the implication on CRM
> 2) if it grows again that fast after I'm done, I haven't really fixed it,
> I've only delayed the inevitable
>
> I will admit, we've not gotten CRM Mobile working yet due to a number of
> 'whoopsie' issues, but we shouldn't have a log going bonkers like this.
>
> Help, quick! We're running out of HD space! :o
>
>