Brandon
Thu May 26 16:33:39 CDT 2005
Thanks for all the info! Verbose logging is a setting that can be changed
in a CRM .xml file that increases the amount of logging taking place. But I
believe this involves the Windows event viewer, not SQL server.
--
Brandon Smith
IT Director
Presentations Direct - Specialized Office Equipment & Supplies
http://www.presentationsdirect.com
"Matt Parks" <mattp65@Yax_RemoveDashAndX_xhoo.com> wrote in message
news:a11c91l4lvdnd37m43co41dqo0sk29v4ve@4ax.com...
> Not sure what you mean by "verbose" logging. There is a recovery mode in
> SQL
> for the databases that can be set to either Full or Simple. In Simple
> mode, the
> transaction log auto-truncates as each transaction is committed to the DB.
> In
> SFull mode, the transaction stay in the transaction log unti la
> transaction log
> backup is performed, at which time the sapce used by those trasactions is
> freed
> up (but the log itself does not shrink).
>
> If you are confident that the log backups are working properly, then you
> can do
> the following to shring the log file in Enterprise manager:
>
> - First, manually run the transaction backup job. This will free up as
> much
> space as possible from the file.
> - Right-click on the database, select "All Tasks...Shrink Database"
> - Click the Files button (NOTE: DO NOT click OK on tis screen as it will
> try to
> shrink the entire database which is NOT what you want).
> - Select the Log file from the drop down at the top of the page
> - Select the "Shrink file to" option and choose the sizeyou want it to go
> down
> to. I would keep it at a few hundred MB just to be safe.
> - Click OK
> - Click OK when it says it shrank the file
> - Click Cancel on the original Shrink DB window (NOTE: This is the window
> you
> don't want to click on OK).
>
> When you choose the Shrink file to option, there will be an indicator
> there as
> to how low you can go. As you successfully shrink the file, if you go
> back in,
> this number will go down each time. this has to do with how the extents
> are
> allocated.
>
> Once you have shrunk the file, I would check the parms on the DB that
> specifiy
> how it allocates additional extents. By default, SQL uses a percentage, I
> prefer to set this to a fied amount. if you started with a default 1MB
> log and
> it grew by percentages up to 3GB, you have a HUGE number of extents that
> were
> allocated and this is extremely inefficient.
>
> If this has happened, then I would actually put the DB into Simple
> recovery,
> shrink the log file as small as it will go (this will require mulitple
> shrinks),
> you should be able to get it down to 1MB. Then, manually force the
> allocation
> to several hundered MB and set the growth to add 50 or 100 MB each time.
>
> After you have done all this, be sure to make sure recovery is back to
> Full and
> again, make sure the backups are actually working on the log files.
>
> Matt Parks
> MVP - Microsoft CRM
>
> ----------------------------------------
> ----------------------------------------
> On Thu, 26 May 2005 10:46:08 -0500, "Brandon"
> <bsmith@presentationsdirect.nospam.com> wrote:
>
> How can I make sure verbose logging is turned off (it was turned on at one
> point) . . . . or does verbose logging only come into play with the event
> viewer (not SQL logs)?
>
> --
> Brandon Smith
> IT Director
> Presentations Direct - Specialized Office Equipment & Supplies
>
http://www.presentationsdirect.com
>
> "Matt Parks" <mattp65@Yax_RemoveDashAndX_xhoo.com> wrote in message
> news:d6c991h8eoighttvpo83brribak64lae9b@4ax.com...
>> Check the usage of the log file itself. You can do this in Enterprise
>> Manager
>> by choosing "Task Pad" from the view menu for the DB. This view will
>> show
>> you
>> how much of the file is actually being used. It is possible that the
>> file
>> got
>> big at one point and was never shrunk. If this shows high usage, then
>> there may
>> be a problem with your log backup job.
>>
>> Matt Parks
>> MVP - Microsoft CRM
>>
>> ----------------------------------------
>> ----------------------------------------
>> On Wed, 25 May 2005 11:20:07 -0500, "Brandon"
>> <bsmith@presentationsdirect.nospam.com> wrote:
>>
>> I'm doing full backups of the DBs and also backing up the transaction
>> logs.
>> Do I need to be doing something else?
>>
>> --
>> Brandon Smith
>> IT Director
>> Presentations Direct - Specialized Office Equipment & Supplies
>>
http://www.presentationsdirect.com
>>
>> "Matt Parks" <mattp65@Yax_RemoveDashAndX_xhoo.com> wrote in message
>> news:8g8891pc550s7206lc8k8gtsghd0cr4bt5@4ax.com...
>>> You need to make sure that you are performing seperate Log backups of
>>> the
>>> database as well as the full DB backups. A full DB backup wil NOT
>>> release
>>> space
>>> from the log, only backing up the log (or truncating it) will do this.
>>>
>>> Matt Parks
>>> MVP - Microsoft CRM
>>>
>>> ----------------------------------------
>>> ----------------------------------------
>>> On Tue, 24 May 2005 10:26:15 -0500, "Brandon"
>>> <bsmith@presentationsdirect.nospam.com> wrote:
>>>
>>> Our CRM log files "CRM_MSCRM_Log.ldf" and "CRM_MSCRMIntegration_Log.ldf"
>>> are
>>> rather large in comparison to our actual data files (mdf). The log
>>> files
>>> are each over 3GB while the mdf files are only about 1.5GB each. Is
>>> this
>>> normal? It seems like I wouldn't want the log files to be this large.
>>> Am
>>> I
>>> doing something wrong?
>>>
>>
>>
>
>