SFO sync - Limit attachments option doesn't!

Since SFO uses MSDE (which has a Max database size of 2GB), we're
hitting the limit shortly.

I've pinned this down to the attachments saved in the
ActivityMimeAttachments table which cumulatively are a little in excess
of 1GB. The rest of the database is 700MB if we exclude the
attachments (guess-timate).

Now SFO has an option to exclude attachments where size is > 100K
according to users. Evidently this does not work at all, since it
doesn't reduce the database size any and appears to still send them across.


My options at the moment appear to be to remove attachments from the
main CRM database (via SDK) and tell users not to save attachments which
are common (like manuals in PDF format) and to only save attachments
which are 'bespoke'.

What are my options (if any)?

Thanks.

Paul
Sun Mar 13 21:58:52 CST 2005

Paul,
First off, I would recommend limiting the amount of data
your SFO Clients are bringing down in general. I suspect
that your Business Unit settings are pretty wide open. I
would suggest sectioning that off a bit. In my
organization, the MSDE is about 150 Megs of core, and
probably another 100 of attachments. We section our
clients into 12 different child business units based on
region. Now, I do not see how any sales representative
using the SFO Client would ever possibly "need" 700 Megs
of text data to do their jobs on the field, but I could
be wrong. I also assume your initial syncs take a good 3
hours or more. If you break up the amount of data
individuals bring down so that the data they receive on
their client is a bit more... pertinent to thier daily
operations rather than grabbing just about everything;
than you should be left with shorter sync times, and less
data per user. Also, attachment sizes will be decreased
because they are also broken down by Business Unit
settings. Give that a try, or post your amount of users,
the business units they are broken up into, and any
sharing/teaming you are currently using in your
organization. The more "open" your business structure is;
the larger the MSDE cleint will be. Keep that in mind and
think about ways of making the data more pertinent per
user. That is about all I can suggest at this time.
-Paul
>-----Original Message-----
>Since SFO uses MSDE (which has a Max database size of
2GB), we're
>hitting the limit shortly.
>
>I've pinned this down to the attachments saved in the
>ActivityMimeAttachments table which cumulatively are a
little in excess
>of 1GB. The rest of the database is 700MB if we
exclude the
>attachments (guess-timate).
>
>Now SFO has an option to exclude attachments where size
is > 100K
>according to users. Evidently this does not work at
all, since it
>doesn't reduce the database size any and appears to
still send them across.
>
>
>My options at the moment appear to be to remove
attachments from the
>main CRM database (via SDK) and tell users not to save
attachments which
>are common (like manuals in PDF format) and to only save
attachments
>which are 'bespoke'.
>
>What are my options (if any)?
>
>Thanks.
>
>.
>

Paul
Mon Mar 14 05:26:34 CST 2005

And you're probably hitting the nail on the head.

As for the sync times - try 21 hours for the first sync! (according to
the users)

I've forwarded this info onto colleagues who are slightly more aux fait
than myself.




Paul Reitmeyer wrote:
> Paul,
> First off, I would recommend limiting the amount of data
> your SFO Clients are bringing down in general. I suspect
> that your Business Unit settings are pretty wide open. I
> would suggest sectioning that off a bit. In my
> organization, the MSDE is about 150 Megs of core, and
> probably another 100 of attachments. We section our
> clients into 12 different child business units based on
> region. Now, I do not see how any sales representative
> using the SFO Client would ever possibly "need" 700 Megs
> of text data to do their jobs on the field, but I could
> be wrong. I also assume your initial syncs take a good 3
> hours or more. If you break up the amount of data
> individuals bring down so that the data they receive on
> their client is a bit more... pertinent to thier daily
> operations rather than grabbing just about everything;
> than you should be left with shorter sync times, and less
> data per user. Also, attachment sizes will be decreased
> because they are also broken down by Business Unit
> settings. Give that a try, or post your amount of users,
> the business units they are broken up into, and any
> sharing/teaming you are currently using in your
> organization. The more "open" your business structure is;
> the larger the MSDE cleint will be. Keep that in mind and
> think about ways of making the data more pertinent per
> user. That is about all I can suggest at this time.
> -Paul
>
>>-----Original Message-----
>>Since SFO uses MSDE (which has a Max database size of
>
> 2GB), we're
>
>>hitting the limit shortly.
>>
>>I've pinned this down to the attachments saved in the
>>ActivityMimeAttachments table which cumulatively are a
>
> little in excess
>
>>of 1GB. The rest of the database is 700MB if we
>
> exclude the
>
>>attachments (guess-timate).
>>
>>Now SFO has an option to exclude attachments where size
>
> is > 100K
>
>>according to users. Evidently this does not work at
>
> all, since it
>
>>doesn't reduce the database size any and appears to
>
> still send them across.
>
>>
>>My options at the moment appear to be to remove
>
> attachments from the
>
>>main CRM database (via SDK) and tell users not to save
>
> attachments which
>
>>are common (like manuals in PDF format) and to only save
>
> attachments
>
>>which are 'bespoke'.
>>
>>What are my options (if any)?
>>
>>Thanks.
>>
>>.
>>