web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / SQL Server Requirement...
Microsoft Dynamics CRM (Archived)

SQL Server Requirements 2016.

(0) ShareShare
ReportReport
Posted on by Community Member

Hi All,

Mods please move if this in the wrong area..

I'm working on behalf of a client implementing CRM 2016. They have been handed the requirements doc by the consulting company and it asks for the following...

Dual Quad core CPU for the SQL Database on a SQL 2016 server, and a Dual Quad Core CPU for a Sharepoint database on the same server. 64GB of RAM. There will be around 100 users using the CRM system and these figures are only for the live system, test and development systems not accounted for.

That is 8 cores and 64GB of RAM SQL standard.. The hardware and licensing costs for this alone, bearing in mind it is in a virtualised environment, is going to be very expensive. I've run backend SQL services for many clients LoB systems with nothing like this type of horse power..

Is the application really that SQL intensive? What would be a more real world figure, and how would that be measured? Number of users of some other metric? I'm not looking for a hard and fast answer just some specific guidance such as we have x and x config with x users and the application runs fine..

Any help / pointers / strands of thought much appreciated.

Thanks

*This post is locked for comments

I have the same question (0)
  • Community Member Profile Picture
    Community Member on at

    Hello,

    That horsepower seems about right.

    The power MSCRM has behind it is massive. The customization and processes you can create will add up and be heavy on SQL, but if you plan to deploy no customization just pure data adding then maybe you could half the ram. CPU is fine.

    I have seen CRM hosting projects use way upto 1TB of ram just for SQL. 100 users and 64gb will run nice and smooth.

    That's sounds perfect and deployable in my opinion and should last you many of years without the needs to upgrade the hardware.

    I would also suggest you look into having a NLB setup with two or more ADFS servers. Split the front end and backend onto two different servers even on the same hypervisor would be fine.

    Let me know if you have any other questions.

  • Community Member Profile Picture
    Community Member on at

    Great. Thanks for your input. :-)

    1TB of Ram wow. That is impressive.

    Issue is the client needs a realistic build not one that has a big headroom. We need to understand what the scaling metric is and scale from there and I'm coming from a very blind point not knowing the product but willing to learn.  We are going to look at Netscaler for NLB in the long run but with Vmware ha it is a trade off. Front end and back end should be separate and load balanced.

    What metric or rule of thumb or gut feeling do you gurus use to size the sql backend???

  • Community Member Profile Picture
    Community Member on at

    Being realistic a powerful CRM like MSCRM needs all the ram it can get, I have seen clients get SQL timeout errors with massive amounts of ram. 64GB is perfect. But don't under estimate it, SQL can easily use 192Gb of ram per instance if it has to.

    None of us just know how much we need, we start off with servers with the headroom for upgrade then start with an average amount of ram.

    If your that worried, purchase just 16GB of ram and see how it goes! As long as you have the free slots on the server you can always just upgrade..

    But its always nice to have an extra bit of ram encase of any future projects etc.

  • Community Member Profile Picture
    Community Member on at

    I just posted a similar question not seeing this one first:

    My question is almost the same except this is for less than 10 users, the client I am working for was handed the requirements from their GP consultant stating they need separate SQL/GP front end. This sounds like ridiculous overkill for only 10 users that will not be connected at the same time. Is there any documentation from Microsoft stating the need for separate SQL/GP servers? Below is my question I just posted:

    SQL requirements for GP 2016 --> less than 10 users

     

     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans