I am trying to determine what our environment will need to look like with version 11. Is there a document that exists with hardware and software requirements? I am interested in knowing if we will need 64 bit hardware, how much memory and RAM for each component and what OS and database versions will be the minimum standard. I am aware that we will need to update the Database to 2008 and the OS as well, but to what version?
Help,
I assume that you've been following the Preparing for v11 page in the Next Generation section? That gives some specific steps that you can take now. No requirements for 64-bit hardware, but if you're putting in new database servers, it's not a bad step. Some new OS requirements on the gateway server, which are detailed on the page as well as the requirement that machines running the application have .NET installed.
We're adding to that page as soon as we discover any new information.
Thanks!
Hi all!
We're in the same boat. Since our service contracts are expiring on our existing servers, we plan to replace them. Is there anything beyond what is shown on the Preparing for V11 page? We want to start by first replacing our gateway server followed by the DB and other servers. Is there a minimum hardware requirements doc specific to V11 we can use as a reference? We could take the already published hardware requirements doc from v9.0 and adjust from there. But I wouldn't want to miss something and cause a problem!
Thanks,
...Dave
David,
Great name by the way. We didn't have anything that was specific to requirements but we took the approach of looking at virtualizing our infrastructure. We figured that we weren't going to have enough horse power with some of our older servers to manage the new demands that we were going to see with V11. That being said we went to blades and have migrated almost all of our infrastructure over. Here it is easy to share and configure server resources to handle the needs of the future demands. Add more memory just requires a reboot and since we went to centralized storage it is very simple to move things around when required.
The one place we didn't do that was the actual SQL Server. Here we upgraded to a large box with lots of horse power to handle the needs both now and in the future. We have about a 400Gig Tessitura database and we felt that it would be best if we were to operate that one separate from the supporting infrastructure. In smaller organizations I would think even this could be virtualized. I would be happy to discuss what we did and why with anyone who wanted to know how we did it. Doing this gave us what we thought was the best approach to deal with the needs for today and into the future.
Dave