Alright, everyone has posted different slow CRM questions. Mine will
be extremely specific.
My organization runs CRM 3.0 with a pretty good sized database, size in
my opinion should not matter, remember infinite scalability? Primarily
with the Outlook 2003 add-in. Alright so they have an 'Offline Client',
usually that means you'll be running on a laptop, or atleast that is
how it is here. With 1.4 GHz and 1 Gig of memory exactly how does MS
expect people to support a MS SQL server locally?
It pegs the CPU, makes outlook a hog and the machine is virtually
useless until 2-5 minutes after boot, and Outlook is slow even after
completing the boot process. Both the sqlserver process and the helper
process peg the cpu at different times. My question is, how do we make
these laptops, with these necessary CRM apps on them, run at a
reasonable pace. Is there some way to improve efficiency, or lower
priority of the sqlserver, but my thought is that would only slow
Outlook queries even more.
So I guess the mobile/offline version of CRM makes a decent small form
laptop useless. MS recommends going SQL32 on the server, but offline
that won't stop the cpu from going to 100%, also increasing memory
won't get the cpu to run more cycles so these fixes are BS.
We can't be (and I am sure are not) the only people with this issue and
MS still doesn't believe that it is as slow as it is. Do they test in
a high-end environment for 25 minutes and then say we are ready to
ship? I mean how did they not see that 'mobile laptops + sql server !=
good idea'.
Seriously any solutions or ideas would be more than appreciated.