03-26-2012 09:05 AM
We're supporting the implementation of an unusually large ACT! 2012 Premium (access via Lan/Web) deployment (124 users).
I'm finding that recommending a reasonable server specification is quite challenging here... The published system requirements on the ACT.com site suggest that (for between 31 and 50 users), a server with a 3.2 Ghz Pentium IV processor and 3 Gbyte of RAM might be suitable as a minimum...
Well I'd be hard pushed to buy a new laptop with a spec that low, so even extrapolating the specs for 2.5 times the number of users suggests only about 8Gbyte of RAM!.
I'd really appreciate it if anyone has experienced an APFW deployment of this size and - as a result - share any thoughts/ideas about what kind of beast of a server we should be looking to build the ACT7 instance on.
Also, as the client has an existing SQL Enterprise cluster with 4 nodes, I wondered whether this might be utilised as a database server rather than provisioning a dedicated machine, but I've never heard of anyone actually deploying SQL Enterprise successfully and returning to talk of its success?
Web access will be facilitated by a number of 'Virtual servers' running IIS, load balancing the database access.
I’d appreciate any help - thanks.
03-26-2012 09:37 AM
As nice as that would be to take advantage of the existing SQL Cluster, two problems come to mind:
1. ACT! still needs it's own named instance, which they may or may not appreciate,
2. ACT! really should be installed on the SQL box, or you forego actdiag, and creating new databases, and on and on and they may not appreciate an application like ACT! installed onto that SQL Cluster.
3. And as to SQL Enterprise edition, I can't talk to the issue of SQL Enterprise - I don't know whether that is supported and/or whether it works.
As to memory requirements - memory is the cheapest bang-for-the-buck and can make up for other shortcomings so I always push for more-is-better. But if you're spinning up several purpose-built Web Servers, and ACT! resets IIS to 32-bit mode, I've never fully understood whether IIS then can't take advantage of more than 3½GBytes of memory, like Server 2003 in 32-bit mode. I'm anxious to hear others weigh in on that.
03-26-2012 10:20 AM
03-27-2012 04:57 PM
As Kevin advises, IIS isn't running in 64-bit so you are limited to the less than 4GB RAM accessible by IIS, however IIS isn't really going to be RAM hungry. You can have multiple applications pools pointing to the same website as well. It will be SQL that demands the RAM, hence you need to run SQL Standard or better. The other limitation is ACT! is a 32 bit application so you don't get the benefits of running on a 64-bit machine from an application perspective.
Be interested to see how you go on this. I notice that your company also does Sage CRM, I am curious why you wouldn't run with Sage CRM.
03-30-2012 09:01 PM