January 16, 2019 at 12:06 pm
Hi,
Today I went exploring the Azure Elastic Query, but I find the solution MS is giving, too much off an hassle, when we're talking about databases with dozens of queries. Of course our system doesn't need to use that much of cross database queries, but having an additional "external table" setup, creates a dependency for us, that we don't like to have to have it. Also the fact that it still doesn't support AD users, makes us not really like this a even more.
So I was thinking, do you guys know any kind of alternative to this, when we're talking about Azure SQL?
Thanks,
Nuno
January 17, 2019 at 7:03 am
Nope.
The only current "alternative" is to go to a Managed Instance. These allow for traditional three part naming to do cross database queries.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 30, 2019 at 4:40 am
Thanks for the reply.
I'm actually exploring it. Having some login issues using Azure AD, but I have a ticket open in Microsoft.
Thanks again!
January 30, 2019 at 4:57 am
nunopedrosilva - Wednesday, January 30, 2019 4:40 AMThanks for the reply.I'm actually exploring it. Having some login issues using Azure AD, but I have a ticket open in Microsoft.
Thanks again!
Happy to help. I'd also offer to help with Managed Instances, but I haven't been able to touch one for over a year, so my knowledge is very limited.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply