SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Best way to get rid of Linked Servers for Migration to Azure SQL?


Best way to get rid of Linked Servers for Migration to Azure SQL?

Author
Message
rafferty.uy
rafferty.uy
SSC Journeyman
SSC Journeyman (98 reputation)SSC Journeyman (98 reputation)SSC Journeyman (98 reputation)SSC Journeyman (98 reputation)SSC Journeyman (98 reputation)SSC Journeyman (98 reputation)SSC Journeyman (98 reputation)SSC Journeyman (98 reputation)

Group: General Forum Members
Points: 98 Visits: 19
Hi all,

We have a spider-web of SQL queries and SQL Servers joined by Linked Servers. We want to get rid of these so that we can migrate to Azure SQL.
I need suggestions/ideas/opinions on the best practice nowadays? I believe that Linked Servers are no longer a widely used practice (correct me if I'm wrong) and I wonder how others got rid of it.

What we are thinking is to create an API layer and use APIs to call multiple DBs and aggregate the data. This is a lot cleaner than calling a stored procedure that is dependent on multiple DBs via Linked Servers.

However, this approach takes a lot of effort as one would imagine (changing the architecture, coding effort for both the API and SQL stored procedures, etc.). Therefore, I would just like to validate if this is the best approach to go forward with.

Opinions and suggestions please? Smile
Grant Fritchey
Grant Fritchey
SSC Guru
SSC Guru (221K reputation)SSC Guru (221K reputation)SSC Guru (221K reputation)SSC Guru (221K reputation)SSC Guru (221K reputation)SSC Guru (221K reputation)SSC Guru (221K reputation)SSC Guru (221K reputation)

Group: General Forum Members
Points: 221084 Visits: 33551
Linked servers are, unfortunately, a very widely used practice. They're not a very widely recommended practice because of all the issues that they cause. However, they're so very convenient, making it so you don't have to move data around or duplicate it, that they get used all the time.

If you want to move to Platform as a Service SQL Database (as currently configured, changes are coming), you just have to unpick the threads of cross server queries. You have to assume no queries between servers (there is a way to do cross-database queries, but it's a little bit of work). Then do what's necessary. I'd suggest not picking a single approach for everything. In some cases, duplicating data will be better. In others, setting up a service so that the app can cross-connect data is a good choice.

----------------------------------------------------
The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood...
Theodore Roosevelt

The Scary DBA
Author of: SQL Server Query Performance Tuning and SQL Server Execution Plans
Product Evangelist for Red Gate Software
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum








































































































































































SQLServerCentral


Search