This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(304, 63%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECK%3C/text%3E%3C/svg%3E)
Is there any way to migrate 1 TB database with 10 minutes downtime
Additional SQL Server features and topics not covered by specific categories
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
yes maybe, but...it's complicated
set up a log-shipped copy of the database and make sure that backups are going across successfully. Set the backup/restore interval to something like 10/15 minutes maybe less if the instance is very dynamic, so the restore will be quickish
when you are ready do a final backup of primary and set offline
copy and restore the backup on the log-shipped database and open it
map users and check the user passwordss are up to date.
If you make sure the connect string from the application is setup using a dns alias and port you can change the dns cname to point to the new database (same port). otherwise you'll need to change the application connect string, maybe on every client!!
Stop and start the application and it should connect to the migrated database, and test
Take a full backup
Check stuff like firewalls, instance permissions won't be copied with the user, TLS might be a problem if the app is old, jobs, linked servers, monitoring, backups etc
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(227.2, 60%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESM%3C/text%3E%3C/svg%3E)
What is your current setup - do you have AlwaysON?
Migrate means, from 1 cluster to another or with in the same cluster?
DB migration can be performed in few ways and the choice is based on your setup.
Detach-Attach
Backup-Restore
Replication or add new node in AG etc.,
What is your current setup - do you have AlwaysON?
Migrate means, from 1 cluster to another or with in the same cluster?
DB migration can be performed in few ways and the choice is based on your setup and the bandwidth.
Detach-Attach
Backup-Restore
Replication or add new node in AG etc.,
Hi @Chaitanya Kiran,
There are several ways to copy a database:
Copy Databases to Other Servers
Regards，
Zoe Hui
If the answer is helpful, please click "Accept Answer" and upvote it.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(236.8, 79%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ER%3C/text%3E%3C/svg%3E)
Migrating a 1 TB database with only 10 minutes of downtime is a challenging task.
It's important to note that the amount of downtime required for a migration depends on a variety of factors, including the size of the database, the complexity of the schema, and the available resources. It's a good idea to test the migration process in a non-production environment and carefully plan the migration to minimize the amount of downtime required.
Are you migrating from On-premise to SQL VM or Azure SQL or Managed instance. Please elaborate your scenario.
Thank You!
Migrating from Onprem server 1 to Onprem server 2
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(35.2, 24%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENR%3C/text%3E%3C/svg%3E)
If that is a local database, the quickest option would be detaching the database on the source server, copying MDF and LDF files to the destination server, and attaching the database there. In this case your downtime will depend only on the time you need to copy the files over. That is usually the quickest option if we try to stay simple and not involve any kind of replication and failover strategies.
If that database is located in Azure, please check the following guide https://www.starwindsoftware.com/blog/azure-migrate-your-sql-server-databases for step-by-step instructions.
I hope that helps.
You haven't mentioned any detail, so difficult to say.
Migration from where to where?