We're hoping to upgrade shortly to v14, and we have a very, very large corpus of custom objects in our database, so my primary concern with the upgrade is if anything in our customizations is going to not be compatible with SQL Server 2014.
I know this happened during the last SQL Server upgrade for us: a large number of reports, agent jobs and the like caused all sorts of curious havoc, and it came down to 2008 not allowing implicit truncation of strings.
We are on a brutally tight upgrade schedule, so I was hoping to hear from any early adopters if they'd run across any big differences between SQL versions such as that example.
Thanks,
Gawain
So far there's only been on major SQL incompatibility, spread over a number of extremely old procedures: SQL Server 2016 no longer supports the old RAISERROR syntax of
RAISERROR [error level] [error string]
(Looks like it actually ended in 2012, but was still available in 2008)
The "RAISERROR" errors were a surprise to me, too. Documented somewhere, I think, but as usual not in the docs I read. ;-)