I have a SQL Server 2008 instance that is running on "LiveServer" our production database (ProdDB) - and we need to upgrade to 2014. In order to do some upgrade testing, I spun up a VM with the same version of SQL server on the test VM (TestServer), did a backup of the production DB from the live server, and restored it to TestServer under a different name (ProdDBUA).I then installed SQL2014 Upgrade advisor onto TestServer, and ran it, checking all the boxes (reporting services etc..) and it all came back clean - no issues whatsoever - not a single warning even. I'm under the impression that stored procs/functions etc... all reside within the DB, so a backup will include those. Is that correct?The problem is, I know I have stored Procs, functions and views that use deprecated joins in that LiveServer.ProdDB. What do I need to do/configure/check in order to make sure that the Upgrade Advisor is actually checking through all that T-SQL that has deprecated code? I want to have a list to give to my report writers of procs/functions/views that need to be rewritten prior to the upgrade going live.I'm not a DBA by any means, I'm a business analyst that works in the IT Department - so I know a bit about how the data flows, can read SQL, and understand the concepts of SSRS, SSIS and relational database design - I'm just not as technical as the rest of my department.Anything I need to do? Suggestions? If there is a modification that needs to be run on the TestServer.ProdDBUA, a cursor to change the path etc, I can get one of my guys to do it.Edit: I just kind of got thrown into this position, so I now have a reason to belong to a SQL forum. Hi! I'm pretty active on the MS PowerBI forums, so I look forward to learning a lot while I'm here as well. Thanks in advance for helping a newbie out.Edit2: DB is running in Compatibility mode 90.
↧