Difference between On-Prem SQL and Azure SQL - sql-server

I am working on POC to move production databases from existing on-prem SQL Server 2008 into Azure SQL.
Details and links on identifying the differences are most welcome!

You can find latest info on what is in Azure SQL Database and how it matches up with SQL Server here : What's new with SQL Database

Related

How to migrate Logins from SQL Server to Azure SQL DB

I want to migrate SQL Server logins to Azure SQL.
I tried using SQL Server Integration Service "Transfer Logins Links" but it throws "Keyword or statement option 'default_database' is not supported in this version of SQL Server."
create a user in master database and set new password for the login.
No matter which ways migrate SQL Server to Azure SQL(single database), DMA or DMS, they all don't support migrate the logins or uses.
We must re-create the logins/users manually in the new Azure SQL database. There isn't a way can achieve that for now.
If you migrate SQL Server to SQL Server on Azure Virtual Machines(managed instance), you can reference this documnet: Migrate SQL Server logins with Data Migration Assistant.
Hope this helps.

Online replication/Mirroring/Migrating Oracle and SQL Server Database to Azure

I am trying to replicate the source database (Oracle 11g and MS SQL Server 201x) to Azure SQL Database. Initially I thought of using Azure DMS(Database Migration Service) to do a full load + Change Data Capture for changes. After started to work on this, I learnt that the DMS requires Control Server privileges on the SQL Server Database and DBA Role on Oracle. We might not get these permissions on the source databases as they are managed by third party company (SaaS model). However, we have read permissions on the source database/tables.
We have to achieve the following :
Replicate data from Oracle Source System to Azure SQL Database and
Replicate data from SQL Server 201x to Azure SQL Database.
What should be the approach?
Azure SQL Data Sync? I read on the forum that it actually writes/creates tables in the source database. This won't be acceptable.
Transactional replication for SQL Server? - Has any one tried? Can you please share your experience?
Third option I thought was to use Attunity Replicate (however, not sure about the licensing costs)
Can someone please help with approaching this business problem?
Regards,
JE
You said, you have read permissions on the source database/tables(Oracle and SQL Server). I suppose that you just have the read-only permission.
Then the answer is no, we can not copy the data or migrate the database(Oracle and SQL Server) to Azure SQL database without the CONTROL SERVER permission.
Data sync can help you sync the data from SQL server to Azure SQL database, but you need have permission to Azure SQL too. Create the table with same schema and so.
If you don't the permission on SQL server, the Transactional replication also doesn't work.
For Attunity Replicate, I don't know much it, sorry that I can't answer you.
For your questions:
1.Replicate data from Oracle Source System to Azure SQL Database
Please reference this Azure Database Migration Guide: Migrate Oracle to Azure SQL Database.
This scenario describes how to migrate an Oracle instance to Azure SQL Database.
2.Replicate data from SQL Server 201x to Azure SQL Database.
Reference: Azure Database Migration Guide:Migrate SQL Server to Azure SQL Database.
This scenario describes how to migrate a SQL Server instance to Azure SQL Database.
We also could use bellow way to migrate the database with SSMS:
Create a dacpac file and import to Azure SQL.
SSMS Deploy database to Microsof Azure SQL database.
For details, please see: Learn how to Migrate a SQL Server database to SQL Azure server.
Hope this helps.

How can i import a db from SQL Server to Azure db?

I have a db in sql server 2014 and i am trying to deploy the database to Azure db using Tasks-> Deploy database to Azure SQL Database.
I installed DAC framework but still i am not able to. When i try to connect to my local Azure server from SQL Server i am able to connect to it. Is there anything else that i am missing ?
Keep in mind that Azure SQL PaaS was quite immature in 2014.
Please upgrade your SSMS version to 17.x. This will work fine with your SQL 14 databases but have all the upgraded tooling for Azure SQL included.

Azure SQL Management instance - restore db different version

Actually we have Azure SQL Management instance I got a backup but I cannot restore our VM SQL Server owing this has a SQL Server version less SQL Azure (Azure Team updated SQL Server a couples week ago), so We cannot update QA Server to last SQL Server Version and we need to recovery the backup a soon a possible.
Do you know any way to recover this backup from SQL Azure to this server getting a less version?
Thank you!
You can also use bcp to export the data from Azure SQL Database and then use bcp again or Import/Export Wizard or SSIS to import the data on the SQL Server VM.
You can use Azure Data Factory (ADF) to export tables to your SQL Server VM. ADF will create those tables and copy the data.

Selecting data from SQL Server 2005 DB to Azure SQL staging DB table in Azure

I was wondering if this is possible: I want to create 2 tables in an Azure SQL database which I want to use as staging tables for some data selected from a SQL Server 2005 database on an on-premise server.
Is there any good way of doing this?
Update:
Followed the Linked-Server Guide and got this error: I need to add a linked server to a MS Azure SQL Server
The weird thing is i just managed to login to the Azure DB on with Those exact credentials. Am i missing some security configuration somewhere?
You don't necessarily need to create a linked server to move data from an on-premise SQL table to Azure SQL. Tools like SSIS come to mind, where a linked server isn't necessary. Or a tool like SSDT where you could use the Data Compare feature to move data. There is also Azure Data Factory.
Support for linked servers and distributed queries against a SQL Azure Database is a feature available since September 2012 as explained here. On my tests it does not work correctly on SQL 2012 and does not work on SQL Server 2008 R2 and earlier versions. You may need to upgrade to SQL Server 2014 to create a fully functional linked server.
Hope this helps.

Resources