a SQL Express with 2200 managed systems???
Best move that to a dedicated SQL for having some performance.
I cannot recall but dont think using the express version is in McAfee Advisory besides small business use or testing.
Amounts of more than 1k are hardly small business.
I cannot therefor help you with the answer on SQL Express; but we do shrink our DB every night in a maintenance task without any issues.
hope this will help you.
As suggested your best bet is to go to a dedicated SQL server. 2008 R2 Express will limit you to 1 core and 1GB RAM. Shrinking the database can lead to fragmentation of both the indexes and database files. (Note: There are work arounds but you're sucking down I/O to do them) McAfee has two KB articles on the subject. The older recommends shrinking and the newer recommends against. Naturally, if you are bumping up against the max DB file size you may not have a choice but with the upgrade you can have a what 10GB DB. (Not recommended)
Thanks for the replies.
When you say dedicated SQL are you talking about setting up SQL on another server. I was thinking of installing SQL 2008R2 Standard on the actual ePO server. We can up the RAM/Cores as it is running in a VM.
We have just migrated the production ePO server to use SQL Express 2008R2. This seems to a requirement for upgrading ePO from the current 32 bit, 2003 server software to a 64 bit system running Windows 2008R2. We plan on doing the migration is a month or so. I was planning on then doing a "Edition Upgrade" to upgrade SQL Express 2008R2 to SQL Server 2008R2 on the same server.
We don't have any DBA who using SQL as they use Oracle. so with my limited SQL knowledge it is up to me to decide the best method.
Message was edited by: twenden on 2/25/14 1:18:25 PM CST
That is up to you but when I read "If managing more than 250 systems, we recommend using a dedicated server." I wouldn't