January 19, 2017 at 5:18 am
Hi, I have one db per instance with information/logging data for the whole instance.
How should I code this to scale out to multiple instances? It´s about 15 tables.
It´s enough if it´s collected once per day.
Should I use linked servers ? SSIS packages ?
Today I use linked servers, but this doesn´t scale very well. I can see in the future that we will have > 100 instances worldwide.
January 19, 2017 at 5:43 am
magnus.tengmo - Thursday, January 19, 2017 5:18 AMHi, I have one db per instance with information/logging data for the whole instance.
How should I code this to scale out to multiple instances? It´s about 15 tables.
It´s enough if it´s collected once per day.Should I use linked servers ? SSIS packages ?
Today I use linked servers, but this doesn´t scale very well. I can see in the future that we will have > 100 instances worldwide.
SSIS sounds like it would do the job just fine.
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
January 19, 2017 at 8:09 am
Phil Parkin - Thursday, January 19, 2017 5:43 AMmagnus.tengmo - Thursday, January 19, 2017 5:18 AMHi, I have one db per instance with information/logging data for the whole instance.
How should I code this to scale out to multiple instances? It´s about 15 tables.
It´s enough if it´s collected once per day.Should I use linked servers ? SSIS packages ?
Today I use linked servers, but this doesn´t scale very well. I can see in the future that we will have > 100 instances worldwide.SSIS sounds like it would do the job just fine.
IF you are using SSMS 2012 or Greater you can setup Registered Servers and then query across all the servers at once with one query. You can maintain the list of Registered Servers and Export and Import the Server list to share with coworkers.
Regards,
Matt
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply