05-05-2011 04:40 AM
Hi - just brought in to work with an Act system - don't know Act, but know databases and servers well - they're experiencing very slow performance. I plan on getting in and doing some perf checking on the database, make sure there aren't missing indexes, key queries are optimized, etc. But as a first blush, can someone give me a sense of what practical size limits an Act database has. Their current situation:
Act! Premium for Web 2009
Server - 2.5GHz Opteron, 2GB memory, decent disks in RAID0 config
MS SQL Server 2005 standard
2 databases - total of 115,000 records
ADF size - one is 1.1GB, the other is 780MB
Not using attachments, that folder is empty
The server in general seems healthy, no obvious problems. SQL Server is certainly capable of handling that many records on this class of server - unless there's something unique about the Act schema that places greater than usual demands on a db.
Any thoughts, before i begin serious "explain plan" type optimization? One person suggested that that DB size is too big, and we need to split the database by regions ... really?
05-05-2011 06:12 AM
05-05-2011 08:39 AM
Thanks, Mike - so memory is likely impacting us, I'll have to look at that in more detail -- to size an upgrade, is there a rule of thumb, based on size of database/# of contacts? They have 7 - 8 concurrent users, but > 100K contacts.
And are there noted performance differences between SQL Server Express and Standard? I'm pretty sure they're Standard, but if not, and if performance is better, we could consider an upgrade.
05-05-2011 09:12 AM