Upvotes: 10<=-=Sep 7 2016 4:29AM=-=>
+1 Upvote, this looks very similar to an issue I am experiencing: http://stackoverflow.com/questions/39367634/sql-azure-integrated-authentication-with-a-cloud-only-azure-active-directory-fai
This is to announce that log shipping with NORECOVERY is now available as a part of an external service LRS (Log Replay Service ) that can be used to move databases to SQL MI. Official docs link here: https://aka.ms/mi-logreplay-service
955 votesunplanned · AdminSQL Database feature voting forum admins (Product Owner, Microsoft Azure) responded
This is not currently planned at this time. Will keep this item open for voting and comments.
Thank you for using Azure Feedback and sharing your thoughts and feedback on enabling Polybase functionalities in Azure SQL Managed Instance.
We started working on it, and happy to announce our first milestone:
Private preview of querying external data (Parquet files) in Azure Data Lake Service (ADLS) Gen2 from Managed Instance. You can learn more about the currently available functionalities from the onboarding guide:
If you are interested in trying it, or would like to share more detailed feedback on the Polybase support, contact us by following instructions from the onboarding guide.
Azure SQL Polybase team
1,502 votesunplanned · AdminSQL Database feature voting forum admins (Product Owner, Microsoft Azure) responded
Not planned at this time. Will keep this item open for future review.
An error occurred while saving the commentJohn Q. Martin commented
The answer here is not to burden SQL Server with the 'functionality' but rather design applications in the correct way to handle transient connection failures. There is a wealth of material and .NET libraries that will help with this.