Server Management - Systems Insight Manager
1832977 Members
3450 Online
110048 Solutions
New Discussion

Moving MSSQL off CMS

 
SOLVED
Go to solution
Bill Slobodnik
Frequent Advisor

Moving MSSQL off CMS

I currently have HPSIM and MSSQL2000 residing on the same server. I would like to move SQL off the CMS to it's own server. Is there any documentation available? I have read the doc on moving HPISM at http://h18004.www1.hp.com/products/servers/management/hpsim/infolibrary.html, but my scenario is not covered there. Specifically, I am inquiring about how to get HPSIM to point to the DB after the DB is migrated.

5 REPLIES 5
Joel Rubenstein
Honored Contributor
Solution

Re: Moving MSSQL off CMS

If you move the database to another server you need to edit the database.props file and change the following lines

hp.Database.hostName=AETDL580
hp.Database.instance=AETDL580\\

Just replace with the name of the new database server and restart the SIM service.
Bill Slobodnik
Frequent Advisor

Re: Moving MSSQL off CMS

Thanks for the quick response. Would the hp.Database.username="servername"\\"username" line also need to be changed?
Joel Rubenstein
Honored Contributor

Re: Moving MSSQL off CMS

You would not need to change the username if you are using a domain account. If you are using a local account (systemname\\username) that does not exist on the remote SQL server you would need to change that entry. If you change the username you will need to modify the database user password stored in SIM

mxpassword -m -x MxDBUserPassword="newpass" this command is case sensitive.
Eric Kass
New Member

Re: Moving MSSQL off CMS

I have a question about moving the HPSIM database. When trying to move it it tells me that files are in use. What exactly do I need to shut down, or services do I need to stop to free that up and allow it to be moved to a different drive?
Bill Slobodnik
Frequent Advisor

Re: Moving MSSQL off CMS

I detached the database, copied the LDF and MDF files over to the new SQL server, and attached the DB. I tried moving the DB first but ran into all kinds of errors. Using Detach and attach database was seamless.