I've been trying to figure out if I can run my DBs using PaaS for a specific application.
The bit I can't quite find an answer to is if Azure DBs on PaaS supports running as a Transactional Publisher?
I've seen an article that says a DB in Azure is capable of being a subscriber, but can't find anything regarding the other way round.
Today SQL DB doesn't support transaction replication if the SQL DB database is the publisher.
Related
Is it possible for me to insert some data from one database to another in Azure sql?
Let's say I have a trigger in db1 that updates some values in db2.
I read about elastic queries but it seems like they are read-only so they don't solve my problem.
You can't use cross-database in Azure Sql Server because databases can't see eachother physically , you could use elastic pools but they are Read Only.
A solution is to use SQL Managed Instance to upload your instance . This supports cross-database queries but it was expensive.
There was some previous discussion here about doing similar:
C# Azure Function trigger when SQL Database has a new row added without polling
There is also the Azure SQL Bindings for Azure Functions but they are input bindings and not triggers and they're still in preview and limited to C#, JavaScript and Python.
Azure SQL bindings for Azure Functions overview (preview)
There was a new announcement last week after MS Build however for Azure SQL Database External REST Endpoints Integration (hopefully they don't refer to it as ASDEREI) but this is currently in preview under Early Adoption Program (EAP).
Announcing the “Azure SQL Database External REST Endpoints Integration” Early Adoption Program
I need to migrate my mysql 5.6 DB to sql server.
Trying to decide wether I should use Azure "SQL Database" as an instance, or should I create a VM with SQL SERVER installed.
This is the SQL database I can create using azure services:
Or use one of these virtual machines:
any tips ?
Azure SQL would save you from the hassle of managing everything by yourself compared to the IaaS, SQL Server VM. However, this comes with tradeoffs like size limitation, sharding limitations etc. I think you'd appreciate a table comparison of the two to decide. Kindly find below article for a comparison of the two in terms of both business motivation and limitations.
Hope this helps!
https://azure.microsoft.com/en-us/documentation/articles/data-management-azure-sql-database-and-sql-server-iaas/
Recently I was informed that Azure SQL V12 now supports
databases that use encryption. I have tried all methods documented here,
https://azure.microsoft.com/en-us/documentation/articles/sql-database-migrate-ssms/
When attempting to migrate a database I get these kind of errors:
[dbo].[someitem] cannot be deployed as the script body is encrypted
Here is a recent response from an Azure AMA,
https://www.reddit.com/r/AZURE/comments/3o1ea9/ama_azure_app_service_team_109/cvu7xco
what am I doing wrong to get this feature working? As I believe I have performed all the steps as documented.
Azure SQL Database V12 supports two types of encryption:
Transparent Data Encryption as documented here: https://msdn.microsoft.com/en-us/library/dn948096.aspx.
Cell Level Encryption: https://msdn.microsoft.com/library/ms179331.aspx and http://blogs.msdn.com/b/sqlsecurity/archive/2015/05/12/recommendations-for-using-cell-level-encryption-in-azure-sql-database.aspx
Which of these are you trying to use?
Do you need to migrate the database between 2 different Azure SQL DB servers or between an on premise SQL Server and Azure SQL DB?
Between 2 Azure SQL DB servers, you can do a true backup restore via CREATE DATABASE ... AS COPY OF... syntax (https://msdn.microsoft.com/en-us/library/dn268335.aspx). This works because the key is in the database backup.
Between SQL Server and Azure SQL DB, there is no term plan to support moving of encrypted procedures or views.
If you could elaborate why you are encrypting procedures and views, that would help us understand the problems you are trying to solve. Many of the scenarios we've encountered in the past where customers desired procedure and view encryption with SQL Server don't apply to Azure SQL Database, but we're always learning of new challenges people have protecting their databases.
Scenario: I have a server farm to deploy my web site. I want to try to add one server from Azure platform. Every host has a replication from one database server. I have tried to add the replication database but I got this message error:
Microsoft SQL Server Management Studio is unable to access replication
components because replication is not installed on this instance of
SQL Server. For information about installing replication, see the
topic Installing Replication in SQL Server Books Online. (New
Subscription Wizard)
After this message I suppose that something is missing in the sqlserver database Azure side.
I have googled something to solve my problem but without luck.
I have found one tool (Azure SQL Data Sync) and tried something to solve the problem but it didn't work.
From the Azure documentation, I have found that until V12 of the azure database replication wasn't available.
But what about v12?
Questions:Am I missing something with the version of the database? Should I change the database plan in Azure subscription?
Should I use some external tool that allow me to maintain sync my database server with the replication?
Replication is not yet available according to the MSDN even on V12. You can use https://azure.microsoft.com/en-us/documentation/articles/data-factory-introduction/ and https://azure.microsoft.com/en-us/documentation/articles/sql-database-get-started-sql-data-sync/. You can write your own sync logic with change tracking, Service broker and linked servers / safe CLR but better use the existing tools.
Maybe Azure Data Factory Service could be a solution for you?
https://azure.microsoft.com/en-us/documentation/articles/data-factory-introduction/
We are investigating moving to a cloud model and the Microsoft Azure PaaS platform.
Our current data layer is written using LINQ to SQL. Will it be compatible with SQL Azure?
Yes LINQ to SQL is compatible. But you have to keep 2 things in mind:
SQL Azure is not a dedicated machine for you alone. Your databases will run on machines with other customers. You may be throttled, you can encounter transient exceptions, ... That's why you should implement a retry policy. There's an article on TechNet explaining how to do this with LINQ to SQL.
Since SQL Azure is not a real SQL Server there are some limitations. Read all about those limitations here: General Guidelines and Limitations (Windows Azure SQL Database). If you're planning to move an existing database (with or without data) to SQL Azure, consider using a tool that supports SQL Azure like the SQL Database Migration Wizard (SQLAzureMW).