- How long does going offline take?
- Posted by Dave McGuire on December 29th, 2004
We're testing going offline on a P4 machine, 384MB RAM, 100MBit network
connection. After about 20 minutes we get this message:
The process is running and is waiting for a response from one of the backend
connections.
We've waiting probably 15 minutes so far (I know, patience is a virtue) and
we've gotten 50MB in the mscrm_msde SQL file so far but only a few other
files have updated before this one.
I will say that we've never had a successful offline replication because we
have an insanely large amount of data (don't know numbers off the top, but I
do know it's thousands of accounts in the one BU). We tried a few months ago
to get one of our salespeople working but they cancelled the download after 8
hours. This was before the SFO Performance packs though.
How fast (mb/hr) should the first offline replication take? And, if it
really does take 8, 10, 12 hours is there any way to 'pre-load' the database
so we can get it done in a reasonable timeframe?
- Posted by John O'Donnell on December 29th, 2004
As you have found going offline can take a few hours. Because of this
Microsoft recommends that the first go offline be performed when the user is
physically connected to your network rather than over vpn or dialup etc. Can
you tell us how much data is in accountbase etc.
There is no way of pre-loading your companies data in to SFO so you do have
to go through the go offline process. is there any way you can sub divide
the CRM system into additional business units to reduce the amount of data
that needs to be synced?
--
John O'Donnell
Microsoft CRM MVP
http://www.microsoft.com/BusinessSol...aqLanding.aspx
"Dave McGuire" <DaveMcGuire@discussions.microsoft.com> wrote in message
news:36EB4C13-4BE1-42C8-B190-23A5A6B68140@microsoft.com...
- Posted by Dave McGuire on December 29th, 2004
Accountbase has just under 1800 records. The whole MSCRM SQL DB is about 370MB.
We are doing this replication in a switched 100mbit environment. I can see
the server from my desk. <big grin>
As for breaking out business units... That idea is not company policy, so
there's not much you can do.
However, we did find another "interesting" issue: Our production SQL server
has 512MB of physical RAM, with about 10MB free. We have also crashed a
crystal report within the last 2 weeks because it couldn't get the data back
in a timely fashion. As a result, CPU went to 100% and spikes there for over
half-hour at a time.
A belated Christmas / Chanukkah present might be some extra RAM for the
servers. <big grin>
"John O'Donnell" wrote:
- Posted by daniel on January 4th, 2005
The intial sync (and subsequent syncs) consume significant memory in my
experience. I would strongly recommend more memory in your SQL server.
"Dave McGuire" <DaveMcGuire@discussions.microsoft.com> wrote in message
news
DF4D038-5682-4747-81B4-F941E202D94A@microsoft.com...
- Posted by Matt Parks on January 4th, 2005
That is not really that much data. SQL is a resource hog. When you go offline,
that will add load to your SQL server during that time. If the machine is
underpowered, than you are going to be in for a long process. The good news
though is that the biggest issue should just be the intial sync with each client
machine. Subsequent synchs should only bring down changes since the last synch,
so the time will drop tremendously.
I would definately recommend a minimum of 1GB RAM on the server. You will
notice that SQL will quickly use all of it though. It is designed to page only
when needed, so it will keep grabbing more memory until there is no more
available and will only release the memory if it needs to. I would also take a
look at the CPU on the box. SQL can be pretty CPU intensive at times as well.
Matt Parks
MVP - Microsoft CRM
----------------------------------------
----------------------------------------
On Wed, 29 Dec 2004 12:33:02 -0800, Dave McGuire
<DaveMcGuire@discussions.microsoft.com> wrote:
Accountbase has just under 1800 records. The whole MSCRM SQL DB is about 370MB.
We are doing this replication in a switched 100mbit environment. I can see
the server from my desk. <big grin>
As for breaking out business units... That idea is not company policy, so
there's not much you can do.
However, we did find another "interesting" issue: Our production SQL server
has 512MB of physical RAM, with about 10MB free. We have also crashed a
crystal report within the last 2 weeks because it couldn't get the data back
in a timely fashion. As a result, CPU went to 100% and spikes there for over
half-hour at a time.
A belated Christmas / Chanukkah present might be some extra RAM for the
servers. <big grin>
"John O'Donnell" wrote:
