[sims] Discover database to new server. process?

[divadiow]

Hi,

 

have moved SIMS and FMS databases onto a new server OK, but am now wondering what the correct process for moving a DISCOVER database is. Have tried to attach the database using dbattach, but it just complains the ldf log file is missing, presumably because the file name is discover_log.ldf and not discover.ldf? Renaming and trying again produces a different error.

 

I have tried to transfer data into a new DB, as if it was a fresh install, but at the moment the Discover Configurator is sat at waiting for service to respond. I am not sure if this is a separate issue or if something in the SIMS database from the old server already references a discover database and that's halting it.

 

What's the correct procedure here?

[matt40k]

Use the Discover "Backup" tool in your SQL BINN folder, "backup" the data, install Discover on the new server - import the "backup".

 

Pretty sure that's it.

[divadiow]

ah yes, I can see the backup gui in the summer release applications. We have yet to deploy the summer release.

 

The database has been detached from the original server, so I'm not entirely surely how to export it to be imported into this new setup...

[matt40k]

Been told Discover shouldn't hold anything that can't be re-imported from SIMS. Not sure how true that is, I guess you'll find out.

[vikpaw]

I thought it stored all your config and customisations, preferences, rules, groups etc. I haven't installed it, just heard.

[woodham]

Did you ever get this to work as im in the process of doing this at the moment ?

[matt40k]

DBAttach won't attach discover or SOLUS3 .mdf and .ldf. Nor will it be able to restore a MSSQL backup.

 

For discover, do a export using the Discover "backup" tool, install discover, import discover "backup"

 

For SOLUS3 (i'm told):

1) Shut down the old ds.

2) Copy the S3 DB

3) Installing the new ds and ds ui (if required)

Existing ui's system config screen would need updating to the new ds machine name

Existing ui's connection string would need to be modified by the connection string editor

4) Re-registering the site so the security keys are sent to the new ds

5) Updating DNS so that serverA redirects to serverB

6) Shut down an online agent - check the status is set to offline

7) Start the agent - check the status is set to online

8) Uninstall the old ds.

 

PS: I know you didn't ask about SOLUS3, but unless you fancy upgrading Discover manually each time, you'll need to use SOLUS3

[woodham]

cool that worked for discover thanks

 

Andy