January 29, 2020 at 9:08 pm
Planning to upgrade the DB from SQL 2012 to SQL 2016. However, the application is depended on other DB which wont be part of this DB upgrade, so of the data as views is used from the other DB that still needs to be on SQL 2012. Until this db is upgraded i was thinking to create Linked server but performance would not be that grate or Replicate/ETL. Does that sounds a better approach or any other thoughts?
January 29, 2020 at 9:23 pm
How is this other DB not a part of the upgrade? Does it reside on a separate system now - and if so, how does the application access that database currently?
If the database resides on the same server - then how and why is it going to be excluded from the upgrade? Are you creating a new instance - and keeping the old instance just for that one database and redirecting the application to use the new instance?
Is there another application that maintains this database? If so - are these internal applications or third-party applications? If in-house, then you should be able to validate that the database can be upgraded and kept in 2012 compatibility (if needed).
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
January 29, 2020 at 9:34 pm
Currently they both reside on same sql server 2012. So one application is okay to upgrade to SQL 2016 the other one has to stay on SQL 2012. I would be creating new instance and keeping the old instance until all other DB's are upgraded. It is a internal applications. The other application team don't want to upgrade at this point so i don't want to hold because of this.
January 29, 2020 at 10:24 pm
You should be able to upgrade both and leave the problematic database in 2012 compatibility mode - have you investigated this? It would save you a lot of trouble.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
January 30, 2020 at 6:37 pm
How you address this issue will depend on how that database is accessed. If there are a lot of queries that join to tables in the other database - then using a linked server may be the only option, even if it is slow.
If the tables being referenced are small - or there are a small number of tables/objects accessed it might be easier to extract the data and load. That will also depend on how often those tables are updated and whether or not 'current' data is required for those queries.
As Phil pointed out - review with the internal team that supports that application and find out if there are any known issues with compatibility mode. Either way, I would plan on testing that application with the database upgraded on the new system to identify any issues anyways - that testing still needs to be done.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply