![]() ![]() In a true database move you will have placed the copied database data and log and other files in new locations. When you have copied the database to a new SQL Server instance, usually on a new database server, you must then make the database active. Therefore if you want to move a database from one server to another, you must either unlock those files or else create a backup copy and prevent any further changes to the database while you are moving the copy. When SQL Server has an active database, it locks the underlying data files and they cannot be copied. In my next installment I’ll discuss the dependencies and additional related objects that you must also move along with the database data. In this article I’ll describe the methods for moving the database. While you can choose from many methods to accomplish these steps, it can be difficult to complete the move given all the database’s dependencies. ![]() It takes essentially three steps to move a database from one server to another: take the database out of production, copy it to another server, and then bring the copy back into production. Investigating the types of moves ahead of time can make planning for a database migration easier. But there are various methods for moving a database, and some have more advantages than others. Moving a SQL Server database from one server to another is simple-initially.
0 Comments
Leave a Reply. |