terewagency.blogg.se - Installing microsoft dynamics nav 2009 r2 sql on windows 8

INSTALLING MICROSOFT DYNAMICS NAV 2009 R2 SQL ON WINDOWS 8 MANUAL
INSTALLING MICROSOFT DYNAMICS NAV 2009 R2 SQL ON WINDOWS 8 PATCH

We have many clients running on one or two server NAV implementations from NAV 2009R2 to 2015. Our current SQL DB is ~60 GB in size.Īgain, I appreciate the responses and if you have any other questions or insights I would love to hear them. Our current NAV VM is assigned (4) processors and 64 GB RAM, and is the most resource intensive server we have. We are on the O365 platform, so we no longer have an onsite Exchange or SharePoint server. The Nimble array has been great, a huge improvement over the EQL arrays it replaced. Those are attached to a Nimble Storage array, which does SSD caching. We have (3) Hyper-V 2012 R2 hosts setup in a fail-over cluster each with dual (8) core processors and 128 GB RAM. In my opinion our virtual environment is pretty decent. Currently we're all on Windows machines, and users will use a NAV Remote App when they're out of the office. I'm not sure on the volume of transactions we do.

INSTALLING MICROSOFT DYNAMICS NAV 2009 R2 SQL ON WINDOWS 8 MANUAL

Volume of transactions (both manual and electronic), your mix of clients (Windows, tablet, Web, O365, etc.) and, very important, the quality, speed and configuration of the servers themselves. Besides that we have a data entry application which uses web services, and that application is used in spurts throughout the day.

Other users consist of our shipping department, purchasing, accounts payable/receivable, accounting, and engineers.

We currently have licenses for 36 users however we don't bump up again that limit very often and around 10 of of those users are Customer Service who just use NAV for customer look up and order entry.

My initial thoughts were we may be better off splitting SSRS and Jet onto their own server, rather than splitting NAV and SQL.but I think that may require an additional SQL license, which we weren't planning on.

Yes, on our current server we also have Jet Enterprise installed.

If nothing else uses SQL, you are sure you're not going to get resource contention, and you trust Microsoft not to cause an issue if the two co-exist then I don't see a compelling argument to split the two apart without more information on total data size, server specs, user counts, and a whole host of other things.

INSTALLING MICROSOFT DYNAMICS NAV 2009 R2 SQL ON WINDOWS 8 PATCH

Although Microsoft is pretty good about it and improvements to Windows make it much less common, if a patch to SQL server causes a problem with a library that NAV needs that can be extremely difficult to deal with

Patching has a chance at being an issue.

If one starts chewing on it is the other going to have enough? Keeping them on separate boxes keeps them from causing bad interactions with each other.

Both NAV and SQL can use a lot of resources.

Does anything else use SQL besides NAV? If so, then I'd recommend the split.

Major concerns I usually have with having things coexist would be this: Running 3 tier here, but I can see the argument for 2.