I've setup a system DSN to connect to a snowflake server.
When I do something as basic as using the SQL Import/Export wizard to transfer the contents of a single table from snowflake to an on-prem SQL server, why does snowflake execute the challenge request 6 times!?
Have you tried the connection caching feature? I've heard good things if your team would be willing to test, perhaps first with a non-prod account.
Related
I am looking for the connection string to connect to SQL server on Azure Cloud
used below string to connect to SQL user
OLEDB;Provider=SQLOLEDB;Data Source=#DATASOURCE#;Initial Catalog=#CATALOG#;UID=userid;Password=pwd;
this is working fine. but when I try connecting with windows user I need to update the connection string as
ODBC;Driver={ODBC Driver 17 for SQL Server};Provider=SQLOLEDB;Data Source=#DATASOURCE#;Initial Catalog=#CATALOG#;Encrypt=yes;TrustServerCertificate=no;Authentication=ActiveDirectoryInteractive;UID=myemailid
Is there a way I can use OLEDB driver to connect using windows authentication?
thanks in advance for help
No, we can't. Azure SQL database doesn't support Windows authentication for now.
Azure SQL Database only supports two types of authentication: SQL Authentication and Azure Active Directory Authentication.
No matter which driver you use to connect the Azure SQL database, the windows authentication won't work.
For more details, please ref this document: Authorize database access to SQL Database, SQL Managed Instance, and Azure Synapse Analytics
Somehow I cannot find it anywhere on the internet. Currently we are running an on premise version of SQL Server. We are looking for the possibility to migrate to the azure cloud for our databases.
However one of our databases heavly runs query using an openedge odbc linked server solution to query an progress database.
I cannot find if it is possible to create a linked server in the azure cloud to allow connections to that progress database.
Does anyone knows if it is possible?
No, Azure SQL Database Managed Instance only support SQL Server/SQL Database linked Servers, Single Database and Elastic pool doesn't support linked servers.
You may check the features that supported by Azure SQL Database here:
https://learn.microsoft.com/en-us/azure/sql-database/sql-database-features
We are trying to evaluate possibility of migrating our in-house SQL DB server to Azure SQL as a PaaS.
Our legacy windows application which is written in VB6 and now running on VB.NET Framework 4.5
Clarifications I need if I migrate only DB server to Azure:
We use both trusted / credential based SQL connection from our desktop application to connect to SQL DB. If we migrate to Azure SQL, will it support trusted connection which should authenticate current organizations NT user?
We have lot of cross DB queries, do we need to face any challenge to use the queries as it is?
Run time we take a DB backup / restore for some business cases. Does this work?
Are there any restrictions on number of admin users on Azure DB?
Probably yes if you sync your local AD with an AAD (See: Use Azure Active Directory Authentication for authentication with SQL Database, Managed Instance, or SQL Data Warehouse)
Azure SQL Database (PaaS) doesn't support cross DB queries by default - you have to setup / use Elastic Query for that.
Yes, you can take a DB backup at runtime and also restore it. There is also a point-in-time restore feature available. See: Learn about automatic SQL Database backups.
I think you can only specify one server administrator (at least within the portal) but I doubt you will reach any limit on db users.
Instead of using the single database SQL Server PaaS service you should also consider using Managed Instance (preview)
You will have to extend your active directory to Azure active directory to keep using trusted connections. You will learn how to do it on this documentation and this one.
On Azure SQL Database you have elastic queries that allow you to run cross database queries. Learn how to create elastic queries here.
You can create bacpacs (export your databases) to Azure Storage or to on-premises location very easy.
You can configure one Server Admin or one Azure Active Directory Admin (it can be a group) for your Azure SQL Server. However, at the database level you can add many database users to the dbmanager role. You can have more information about this topic here.
I am trying to create a .bacpac file of my SQL 2012 database.
In SSMS 2012 I right click my database, go to Tasks, and select Export Data-tier Application. Then I click Next, and it gives me this error:
Error SQL71564: Element Login: [myusername] has an unsupported property IsMappedToWindowsLogin set and is not supported when used as part of a data package.
(Microsoft.SqlServer.Dac)
I am trying to follow this tutorial so that I can put my database on Azure's cloud:
http://blogs.msdn.com/b/brunoterkaly/archive/2013/09/26/how-to-export-an-on-premises-sql-server-database-to-windows-azure-storage.aspx
How can I export a .bacpac file of my database?
SQL Azure doesn't support windows authentication so I guess you'll need to make sure your database users are mapped to SQL Server Authentication logins instead.
I found this post referenced below which seems to answer my question. I wonder if the is a way to do this without having to delete my user from my local database...
"... there are some features in on premise SQL Server which are not
supported in SQL Azure. You will need to modify your database before
extracting. This article and several others list some of the
unsupported features.
This blog post explains how you can use SQL Server Data Tools to
modify your database to make it Azure compliant.
It sounds like you added clustered indices. Based on the message
above, it appears you still need to address TextInRowSize and
IsMappedToWindowsLogin."
Ref. http://social.msdn.microsoft.com/Forums/fr-FR/e82ac8ab-3386-4694-9577-b99956217780/aspnetdb-migration-error?forum=ssdsgetstarted
Edit (2018-08-23): Since the existing answer is from 2014, I figured I'd serve it a fresh update... Microsoft now offers the DMA (Data Migration Assistant) to migrate SQL Server databases to Azure SQL.
You can learn more and download the free tool here: https://learn.microsoft.com/en-us/azure/sql-database/sql-database-migrate-your-sql-server-database
As of 9/2018, there is a new tool called the Data Migration Assistant that can help with the task of migrating an existing on-premise SQL Server Database to Azure. While the tool will NOT resolve the issue of migrating Windows Logins, it will at least help you get your database schema and data migrated up to Azure.
Here is the overview of the tool: https://learn.microsoft.com/en-us/sql/dma/dma-overview?view=sql-server-2017
You can download the Data Migration Assistant here:
https://www.microsoft.com/en-us/download/details.aspx?id=53595
Once you have migrated your database up to Azure, you can configure an AD Administrator on the SQL Server, then create contained users in your database to allow users to login to your SQL Database with their Windows accounts.
I was wondering if someone could help. I have a SQL database hosted on a remote server (internet hosting company) and i want to sync my azure database.
any ideas how i could do this? eventually, i would like to transition over to sql azure.
thanks in advance.
i prefer using SQL Database Migration Wizard: http://sqlazuremw.codeplex.com/ for one time migrations. it has the option to do some analysis to check for things that are not supported in Azure SQL Database.