![]() I capped the sql ram at 4 gb’s for the secondary. Part A: here I show exactly what I needed for this setup:Ĥ processors, 16GB ram, sharing 7000 RPM with secondary, virtualized with slow type 2 hypervisorĢ processors, 8 GB ram, sharing 7000, RPM with primary, virtualized with slow type 2 hypervisor ![]() So, I built a configuration and put it to the test just to see how AX would perform if I went minimal. At their size, they might have 20 or 30 non-prod environments and it was important to figure out a few things. This client wanted to test their installation with the good hardware, but they also wanted to know what was the minimum hardware they could use for non-prod environments. What I like about this post is that I will show you how to troubleshoot an install gone wrong when all the steps are there, but it just didn’t work initially. This is the only one that failed even though the steps were the exact same as the other configurations (except for my 3 machine install hack which I didn’t use for an Enterprise install). I’ve tested out 5 different configurations with the install and I’ve gotten 4 of them to work. For one, the install is a lot more stable, and the instructions have really improved. Predictably, a lot has changed since my day 1 install. I’ve been finishing up on a huge Enterprise D365 on premise install and upgrade this month for an organization, and thought I would write a special post with a configuration that I tested out for them.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |