We have a client this is doing some work with test with SQL 2014. There are some actions that need to be taken to at least get it running. They haven't completed their regression testing at this point, so I am not sure if there are other issues:

• SQL DMO was Discontinued in SQL 2012 (msdn.microsoft.com/.../ms144262.aspx) . The workaround for this is installing the SQL Backwards compatibility for SQL-DMO. This link from Dell has a download link to the Microsoft SQL Backwards Compatiblity installer support.software.dell.com/.../113663. At Arrowhead this allowed us to install the DB Utilities, run DB Sync and register.
• In 2012 triggers with the “with append” clause were discontinued. I read that his clause was around from early days of SQL where you could only have one trigger per trigger type. So the with append allowed you to add code to the “insert” trigger for instance. The change affects running create trigger scripts against the DB, not existing triggers in the DB. The “With Append” just needs to be removed from the script.
• In 2012 the Raiserror syntax changed. There was an undocumented version that Sage uses with the syntax of RAISERROR @MsgNumber @MsgText. This undocumented syntax was discontinued in SQL 2012. It needs to be replaced with RAISERROR(‘<message text>’, Severity, State). This needs to be fixed in both Sage code and custom code. So far it looks to only be in Sage DB objects and not embedded in VB6.0 code.

Thanks for the input.

So far, I've also found that the Sage 500 2014 DB Utilities install cleanly and will synchronize/register a 7.4 DB. However, compares/upgrade script generation fails (possibly due to the SQL-DMO compatibility?)

Side note, the 2014 DB Upgrade will only (attempt to) upgrade a 7.4 DB to 7.5, and not to 7.6 directly?

Also, connecting to 7.4 on SQL 2014 is possible, but most tasks seem to generate form errors when actually inputting data. This probably correlates to what you've found (and thanks for that).

jlputtman

Are your clients testing with 7.4, or later versions?

The specific client that I am working with is actually on 7.2.

It will be interesting to see what Sage supports and doesn't. SQL 2016 is coming out at some point (I'm guessing before the end of this year) but it's only CTP right now. I know that a lot of shops don't want to move off of SQL 2008R2 because of the increased licensing costs from Microsoft. They jumped quite a bit. They also changed some of the architecture in SQL 2012 which reduces the available memory SQL will use if on the standard version.

Apparently MS raised the memory limitations to 128 GB on SQL 2014 Standard (from 64GB). Which makes it more compelling to move past SQL 2012, if possible.

msdn.microsoft.com/.../dn169381(v=sql.15).aspx

Per Linda Cade,

"We have tested the Sage 500 ERP 2016 Release with Microsoft SQL Server 2014.  It is compatible."