08-20-2012 04:05 PM
Currently ACT! 2010 Premium is running fine on a Windows 2003 SBS Server Standard Edition as the database server and with the client running on the server for emergency access. SQL Server 2005 (Express) is used with ACT! 2010
Are there any issues anyone has experienced as part of upgrading to ACT! 2012 Premium related to a required upgrade of the SQL Server engine from 2005 to 2008 R2. In some postings, I read that SQL Server 2008 R2 is not supported under Windows Server 2003 Standard Edition, and other blogs say no problem. Comments on this from anyone?
Research indicates it is best to both uninstall ACT! 2010 Premium and SQL Server 2005 first before upgrading. Any opinions on this vs. an in-place upgrade?
I appreciate feeback from the community on this topic. Thanks!
08-20-2012 04:49 PM
I've had no problems running SQL Server 2008 R2 on MS Server 2003.
In my experiance, uninstalling SQL Server 2005, specifically the ACT7 instance is required. If any trace of the ACT7 instance remains, then MS SQL Server 2008 R2 can fail during installation. In fact, when it's a server thats had SQL 2005 on it, I often manually uninstall it, then manually install SQL 2008 (KB 26994).
08-21-2012 08:15 AM - edited 08-21-2012 08:16 AM
I would agree with Ben that best practice is to uninstall SQL 2005 (all of it if you have no other apps using SQL, only ACT7 instance if you do). You don't have to uninstall ACT! 2010, but you may as well if removing SQL. Then reboot the server and install 2012. I think it's actually faster to remove and install SQL than it is to upgrade the instance.
Note: Effective 6/1/13, Sage no longers provides support for the Act! software. This is now provided by Swiftpage.
08-21-2012 08:29 AM
Thanks for the two responses both confirming what I suspected should be done. I appreciate the quick response and I suspect this hint will be valuable for those upgrading from ACT! 2009/ 2010/ 2011 to 2012 and 2013. In my experience, it is common for users to leapfrog releases. Premium Mobile and end of upgrade pricing for 2010 seems to be the driving factor to upgrade to 2012/2013, thus the questions about best way to handle the SQL server upgrade.