I'm using Azure SQL Data Sync, i'm seeing current smallest interval for sync is 5 minutes, can i get option to set this to between 1 and 4 minutes or a continuous synchronization.
not..if you use azure portal to setup the sync, 5 minutes are the least interval time. however you may use Powershell scripts or Azure SQL RESTApi to trigger the sync manually from your application level.
It does not appear that it is possible to do data sync below 5 minutes, from the documentation.
You can read about your other options for Data Replication and Synchronization here.
Related
I have a website that need a database to store some user information and a blob storage to save some files.
I want to minimize the cost as much as possible so I played around in Microsoft Azure Pricing Calculator with a Azure SQL Database. For the database I think that over it's hole lifetime 2GB of storage would be enought.
I arrived to 2 options that where dirt cheap but I don't really understand what it gives me.
First is with a serverles computer for 3600 seconds (of runtime?)
Is that time the time that my database is processing the request? For example if I have a select statement that takes 1 sec to complete I'll be left with 3599 sec for that month?
If that's the case what happens if I run out of time?
Second option is using a Hardware Type: Gen 4
but for this one I don't have any other options to configure my needs. Is this obsolete? Can I rely on it for production?
If you need a very cheap one use the Basic or S0.
Keep in mind that Basic are very slow: try to connect to it through SSMS.
Serverless is for databases that you pause for 3/4 of the day. It might be the case for you but keep in mind that when you use them they will cost a lot. I don't think this will be suitable for you.
I'm trying to achieve live (instantaneous) data synchronization between two SQL databases [3 source tables to 1 target table], the synchronized data come from 3 different tables in the source database and should go into one table. I have looked into some options and had those disadvantages:
1 - Azure Data Sync:
a- 5 minute intervals of synchronization
b- Synchronization between tables happen on a 1 to 1 bases.
2 - Azure Logic App:
a - SQL connector throttling issues
Is there a better way to achieve this?
I think you can consider using Azure data factory to incrementally syncing data on-premise to Azure SQL. This post also introduces in detail how to implement the whole process.
There are two main ways of incremental loading using Azure and Azure Data Factory:
One way is to save the status of your sync in a meta-data file. In this file you would save the row index of the table and thus the ID of the last row you copied. Every time you want to add the newest data to the cloud, you look up the progress (latest row) and start from there (e.g. row IDs bigger than X). This process is out of scope in this article but is extensively explained in the Microsoft documentation. (Use a meta-data file when your table doesn't have an 'updated timestamp'.)
Another way to do it is by using tumbling windows. Tumbling windows are time windows that do not overlap and are completely inclusive. As the image below shows, this means that every window will start at the end of the previous window.
I'd like to increase the database Max Size while the application utilizing the database is running.
Will scaling it up have any noticeable impact? This is a small scale application; a minute of down time would be OK. More than that and I'd have to push off the upgrade to outside of business hours. Thank you.
As you said, a minute of down time would be OK. Scaling the database took you 20 seconds, I think this latency is within your acceptable time range.
The document Scale single database resources in Azure SQL Database only can give you the reference max time : "Typically, less than 5 minute".
The latency usually depended on the current Azure SQL database price tier and the target server price tier which you want scale up to.
We can not calculate the specific latency time for you. It's all happening in Azure background.
Hope this helps.
I have an Azure SQL Managed Instance and have noticed that database creation and deletion not only takes a long time, 3 minutes to create a new database and up to 5 minutes to then delete that database, but that those times can also fluctuate a lot too. What is the reason for this?
When a new databases are created their files are initialized on Azure Premium storage (which is remote storage) including initial backup so they can be ready for HA, and also they need to be registered in Azure Management Service that controls availability of database. This is not instant, but in most of the cases it should be under a minute. I'm frequently creating databases and I don't remember any case when it was longer than 10-15 sec.
For delete operation you can expect up to 5 minute delay, because we are waiting for the last log backup to be taken (log backups are taken every 5 minutes). In the future we might initiate tail log backup immediately when the DROP DATABASE is executed, but in the current version Managed Instance waits for last backup.
I currently have an Azure S2 database running via the new Azure Portal.
I notice my billing was higher than it should be and after investigating further, I noticed there were new databases appearing every day then disappearing.
Basically, something is running a CreateDatabase and DeleteDatabase event every evening, and I'm being charged an extra hour each day.
Microsofts response is:
"Our Operations Team investigated the issue and found that these databases did indeed exist in a 1 hour windows at midnight PST every day. It looks like you may have some workload which is doing this unknowingly or an application with permissions which is unknowingly creating these databases and then dropping them. "
I haven't set up any scripts to do this, and I have no apps running that could be doing this.
How can I find out what's happening?
Regards
Ben