Consider the scenario, and for many of my customers this is a common one. The customer has Sage CRM installed on their old Windows 2003 Server with SQL 2005. It has valiantly kept going with minor upgrades to allow it to carry with Sage CRM 7.1SP2.
Now they want to upgrade to 7.2. So, they buy a new server with Windows 2012 on it and SQL 2012. Now, here is the problem. What is the supported upgrade path?
I can't upgrade on the old server to 7.2 because 7.2 isn't supported on that version of Windows or SQL. I can't move the 7.1 install to the new server, despite it being on patch G, because the SP2 installer won't install to SQL 2012.
Speaking with support, they tell me I need an intermediary step of moving the system to a Windows 2008 R2 system with SQL 2008 R2. This suggests the customer has to fork out for another server (or licence if they make a VM, plus Windows and SQL software). The answer is always a flat "No" and I don't blame them.
The only way I can see an upgrade path being made is for Sage to create a 3rd service pack for 7.1 which includes the rollup of at least patch G to allow the installer to work with SQL 2012.
Unless anyone else has anything to add that I may have missed?