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
Ryan Creps has alerted me to the fact that there are Tessitura functions that I should have been using for this: dbo.FS_USER() and dbo.FS_LOCATION().
Gawain Lavers said:functions that I should have been using for this: dbo.FS_USER()
...which does a substring(... 1,8) for you. :-)
Oh! I just used it in our Live DB (pre RAMP changes) and it gave me 'dbo', so I thought it was just returning that as a default if it didn't match to T_METUSER, but I see that it is just truncating, and that's bad, because any admin user will appear as 'KRIOSTES'.
I wound up creating my own function: it's nothing fancy, it allows you to override the returned id (I use "admin", not a username we have, to set apart updates created by scripts: hope to make it do something more clever in the future).