- Shrinking the Distribution DB
- Posted by Brandon on August 4th, 2005
I have followed the instructions found in article 894811 (customersource
login required) to shrink the MSCRMDistribution database size, but after
following the directions, the size of the DB remains the same. Is there
something I'm missing?
--
Brandon Smith
Presentations Direct - "Document Finishing Solutions"
http://www.presentationsdirect.com
- Posted by Nathan Warner on August 5th, 2005
Is your database set to simple? (recovery model)
It will not shrink in full.
"Brandon" wrote:
- Posted by Jacob Mondrup - Cultivator Danmark on August 5th, 2005
The MSCRMDistribution databse is by default set to simple.
In the matter of shrinking the DB: Make a full maintenance plan for this
databse, but without backup of the transactionlog (because its is in simple
mode). Thats works for us.
Jacob Mondrup
IT manager, Cultivator Denmark.
"Nathan Warner" <NathanWarner@discussions.microsoft.com> skrev i en
meddelelse news:A9DC48EB-D6E7-48F4-AC36-A7D2ECC553F4@microsoft.com...
- Posted by Brandon on August 5th, 2005
Actually, I our recovery is set to full . . . and the database got much
smaller after the shrinking process and a server reboot.
My only question now is about deleting schedules as recommended in article
894811 (on customersource). Part 2 says to delete schedules on the SQL
SnapShot agent jobs. Aren't these needed?! I deleted them, but I thought
they might get recreated at some point . . . not yet. Do I need to manually
recreate these jobs?
--
Brandon Smith
Presentations Direct - "Document Finishing Solutions"
http://www.presentationsdirect.com
"Jacob Mondrup - Cultivator Danmark" <jm@cultivator.com> wrote in message
news:O7QUAlZmFHA.268@TK2MSFTNGP10.phx.gbl...
- Posted by Matt Parks on August 5th, 2005
You should only have deleted the schedules, not the jobs themselves.
Part of the problem, is thoe jobs initally are scheduled to run every 5 mins.
This creates a huge data load on the DB as it stores a new snapshot every 5 mins
which is pointless. However, the jobs have a step that should remove the
schedule the first time they run. Problem is, if there is an issue with the
snapshot creatin (like security rights), the steps gets removed from the job,
even though the schedules weren't removed and thus you keep getting snapshots
taken which causes the DB to fill up.
Many times, to shrink a DB file, you need to backup, shrink, backup and shrink.
It has to do with the way SQL keeps internal pointers int he files.
Matt Parks
MVP - Microsoft CRM
----------------------------------------
----------------------------------------
On Fri, 5 Aug 2005 08:49:50 -0500, "Brandon"
<bsmith@presentationsdirect.nospam.com> wrote:
Actually, I our recovery is set to full . . . and the database got much
smaller after the shrinking process and a server reboot.
My only question now is about deleting schedules as recommended in article
894811 (on customersource). Part 2 says to delete schedules on the SQL
SnapShot agent jobs. Aren't these needed?! I deleted them, but I thought
they might get recreated at some point . . . not yet. Do I need to manually
recreate these jobs?
--
Brandon Smith
Presentations Direct - "Document Finishing Solutions"
http://www.presentationsdirect.com
"Jacob Mondrup - Cultivator Danmark" <jm@cultivator.com> wrote in message
news:O7QUAlZmFHA.268@TK2MSFTNGP10.phx.gbl...
