[Database] - Using non-default OpmanagerDB name goes wrong.

[Database] - Using non-default OpmanagerDB name goes wrong.

Hi, I'm working on "resetting" my whole opmanager setup by installing on a new server, I'm creating a complete new Opmanager setup from scratch on a new MSSQL Server.
 
      I created a new "normal" setup with the default database, wich will be my next production Opmanager.
 
      I created a second opmanager database on the same server but the apps files are on a Virtual PC, on wich I plant to test the things I do instead of testing on the production server, so I dont get stuck with test values like device templates or other configuration issue that I might want to test and such... So for the second database, when setting up MSSQL info, I put the name OpmanagerDBVirtual so I know where it is (I want it to be in MSSQL since this is how my production server is set up. And I wish it to be on the same MSSQL server because of the same reason, have the most "clone-like" setup so what I test in the virtual can be transposed on the production.
      The database have been created and it seemed fine, however, the url parameter in database_params.conf remains pointed to "OpmanagerDB", only in the SMSServer.conf does the "OpmanagerVirtual" configuration is taken, and after looking at the MSSQL connections, the Virtual opmanager connects to OpmanagerDB, not OpmanagerVirtual.
 
      I tried changing only the line in database_params.conf and it seem to be fine, but I wanted to know if there was something else I had to do for this to work correctly. Because I want to change my "current" opmanager database to put it on the new server with a new name, but I dont want to loose everyting, so I want to confirm that the "URL" setting in the database_params.conf is the good thing to change since this is meant to be a test environment, I want to make sure that the environment is good to start with ;-).
 
       So the issue to check is : When setting a non-default OpmanagerDb name in the original configuration "wizard", the specified name, even if the non-default named database is created, is not used. This should be corrected I think. (It MAY be specific as when an "OpmanagerDb" database already exist on the MSSQL server, I did not try removing the normal database and having only non-default names)
 
       A question I look answer for is : Is the "URL" setting in the database_params.conf is the only thing to change for this configuration to works correctly.
 
Raphaël LEMIEUX

                  New to ADSelfService Plus?