Home
Web CMS (TeamSite)
Migrating to another SQL server.
pjalani
Hi All,
We are using Mediabin 4.5.3 and SQL 2000 Server. We are migrating database to another SQL server. I am not involved in database migration process but I need to make changes on application side.
I assumed that I need to change SQL server name.
Please advice me what are the other parameters that I need to change ?
Do I need to create new System DSN or we can modify the existing one ?
Hope to see response soon.
Regards
Priya
Find more posts tagged with
Comments
Spiff
The basic steps for migrating the MediaBin repository database are:
1. Backup the database from the old SQL Server.
2. Restore the database to the new SQL Server.
3. Remove access of the MediaBinSQLUser account to the new database.
4. Add back access of the MediaBinSQLUser account (with db_owner priviledge) to the new database.
5. Remove the MBReportReader role from the new database.
6. Remove all views with names starting with 'Report'.
7. Restore report views by executing the script report.sql which can be found in the SQL sub-directory under the MediaBin server installation directory.
8. Modify the existing ODBC System DSN by changing the SQL Server name and the default database.
Some caveates:
a. The database access account name and password must remain the same across both SQL Servers.
b. While database accounts may look identical, they are in fact distinguished by a hidden ID. When a database is transfered from one SQL Server to another, user accounts are required to be removed and then added back.
c. The above steps are relevant to moving the MediaBin server's repository. Other MediaBin applications (e.g., DA) utilizing database storage may have other steps or requirements.
Migrateduser
The easiest method to migrate Deployment Agent would be to back up your database from the original SQL Server (which I'm sure you've done).
When you've brought the new SQL server online:
- reinstall Deployment Agent, first the service then the DA web client
- stop the Deployment Agent service
- restore the original Deployment Agent database to the new one
- restart the service.