How to move the OperationsManager DataBase to a new SQL server
I am currently testing with moving the OperationsManger database, OperationsMangerDW database, and the reporting services role to new servers.
the two databases will be moved to a new SQL server under a new name. And the reporting services role will be moved to its own server serperate from the SQL server. I will post all three manuals that I have created out of this here.
how-to-move-the-operationsmanager-database-to-a-new-sql-server
Comments
2 Responses to “How to move the OperationsManager DataBase to a new SQL server”
Got something to say?
You must be logged in to post a comment.
Hi Brad,
First, thanks for all the articles, they’re really useful.
A question about moving the OpsMgr databases: If you started off with the DBs on the same server as the SQL Server instance, but then wanted to move them to a SAN for added resilience, at what point in the restore would you specify the new locations for the DBs and Logs, assuming you followed best practice and put the DBs and Logs on separate drives?
Regards,
Chris
Hi Chris,
You will have the chance to change the path when you re-attach the database. At this point the wizard will place all your DB files into that location. If you have a test environment, you should run through once as well. Even if you don’t have a test server with a SAN, it would still be helpful for you to go through the process of moving the database itself.
However, not being a SQL guy myself don’t take this as the right approach. But if you are planning on using the same drive letters for your SAN attached drive. Then you may not need to detach and reattach the database. You might be able to simply stop your sql services, copy the database over to the new drive, change the drive letters on the SAN drive to match the original. And restart the database.
Let me know what you do, I am curious.
Brad