We are planning to migrate our self hosted MongoDB database to Azure CosmosDB with Mongo API. We have 186 GB of data. Server-less CosmosDB is our plan. But as we dig in to the documentation we find that, Azure Data Migration Service (DMS) don't support migration to a server-less CosmosDB.
So our plan is to create a provisioned Service of CosmosDB then migrate our data there and from that provisioned service we will migrate to a server-less CosmosDB and then finally we will delete the provisioned CosmosDB service.
But how can we achieve the second stage of our migration.? is there any particular service provided by azure for that?
And we are good if we can migrate in Online mode. Because our service can't bear a large downtime. We know that the first stage of migration (ie. From Native Mongo server to provisioned CosmosDB via DMS) can be done in Online way. But is it possible to parallelly do the online migration from Provisioned CosmosDB to a server-less CosmosDB?
If Online migration isn't possible we are OK with the offline mode as well, unless it don't requires a large downtime of the application. Is there any estimation on the time for migration?
Please shed some light to these concerns. It will be so much helpful for us to do the task. CosmosDB is a great service provided by Azure. We can't wait to see our database there.
There is a way to do an offline migration using Spark. You can learn more by reading this article.
That said you can't use serverless anyway because it has a maximum storage capacity of 50 GB.
Update: Clarified data is not 186 GB for a container so serverless is ok.
Related
I'm looking at creating a web app in portal azure but I came across this option. Create Web App + Database.
My question is if I select the DB engine to be SQL Azure. How big is the database?
Also, what's the difference between the Basic and Standard hosting plans?
Thanks in advance.
How big is the database?
The SQLAzure option refers to the Serverless Azure SQL Database offering. Source
Like most of Azure's managed SQL offerings, it scales up based on how much data you throw at it over time, but it appears the limit for storage is 2TB. Source
Also, what's the difference between the Basic and Standard hosting plans?
This is pretty explicitly addressed on the App Service Pricing page. Among other differences, the Standard plan comes with more disk space for your app and supports auto-scaling of the underlying resources.
I migrated from sql server to Azure db.
While migrating I found a job named syspolicy_purge_history, do I also need to implement it on Azure db?
As I found the syspolicy_purge_history job is targeting msdb, but I could not found msdb on Azure. A guidance will be highly appreciated...
You can implement syspolicy_purge_history job in case of azure database and msdb not available for Azure SQL Data Warehouse in your case its applicable and supported all version of msdb database
Syspolicy purge history is the default job that deletes data that is older than the number of days specified in the HistoryRetentionInDays property of Policy Management. This prevents unnecessary space consumption in the MSDB system database.
For your Reference:
sp_syspolicy_purge_history (Transact-SQL)
Migrate SQL Server to Azure SQL Database
As similar to app service plan, can we autoscale pricing tier of azure SQL database? Currently, my database is in standard S2 tier and I want scale out it's tier in S3 when CPU utilization reached up 80% and similarly want to scale in when it's down to 60% to S2.
I was going through many links and found this is old question/answer but wanted to check if we have any options available for the same.
Autoscaling Azure SQL Database
Single Azure SQL Database supports manual dynamic scalability, but not autoscale. For a more automatic experience, consider using elastic pools, which allow databases to share resources in a pool based on individual database needs. However, there are scripts that can help automate scalability for a single Azure SQL Database. For an example, see Use PowerShell to monitor and scale a single SQL Database.
I have site deployed on Azure. I am using Cloud Services, Storage, SQL Database.
I want to have High Availability and Disaster Recovery for our Azure Website.
My question is that how can we provide this feature on Azure? Is it already managed by Azure or we need to use any services from Azure for the same.
Thanks in Advance
Well, I don't think DR is needed, since everything you use is PaaS Service, so if you trust Azure - it will handle everything for you, if you don't. Well, if you don't it won't help you ;)
So, in my opinion best way to achieve what you are looking for is using build-in HA for Cloud Services (increase instance count), while Storage and Azure SQL are HA by design.
If you really-really want DR, you can implement Traffic Manager with extra copy of your Cloud Service in another Azure region and implement Storage Replication and Azure SQL Replication.
I won't be giving link to documentation, as all of those are found in under 5 minutes in and search engine.
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.