We are trying to upgrade our SQL Server from 2012 to the SQL Server 2017, the main problem we are facing is one of the legacy reporting tools can't connect to SQL Server 2014 or higher.
Long story short, we can't upgrade this legacy product and it's will be too time consuming to migrate all the existing reports to another reporting tool.
Since reports are read-only, we are considering upgrade the main SQL server to SQL Server 2017, then setup a SQL Server 2012 instance and let it use linked server connection and point to tables/views needed by the reports.
Therefore this SQL Server 2012 instance will contain no actual data, just a lot of views/synonyms that have the same database & object names which linked to the primary SQL Server 2017 server.
The main concern with this setup is all the join statements used by reports will become link-server joins and we will run into query performance issues (some of the underlying tables used by reports are huge).
Is there any other way to work around such problem?
Long story short, we can't upgrade this legacy product and it's will be too time consuming to migrate all the existing reports to another reporting tool.
Since reports are read-only, we are considering upgrade the main SQL server to SQL Server 2017, then setup a SQL Server 2012 instance and let it use linked server connection and point to tables/views needed by the reports.
Therefore this SQL Server 2012 instance will contain no actual data, just a lot of views/synonyms that have the same database & object names which linked to the primary SQL Server 2017 server.
The main concern with this setup is all the join statements used by reports will become link-server joins and we will run into query performance issues (some of the underlying tables used by reports are huge).
Is there any other way to work around such problem?