Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 6 replies
  • Subscribers 1 subscriber
  • Views 2083 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Upgrade from SEC 4.7 to SEC 50

BudgetHelp

Hi - I need to know how to upgrade SEC 4.7 to 50 but more so on the database side

We have the following set up:

Windows_ServerA running SEC4.7 and Update Mgr

Windows_ServerB running SQL 2008 Server with SOPHOS47 database

I can upgrade the SEC console no problem, but need advise on how to upgrade the SOPHOS47 DB to SOPHOS50 ?

On the SEC server to talk to the remote database, we modified this key:

Provider=SQLOLEDB;Integrated Security=SSPI;Initial Catalog=SOPHOS47;Data Source=<serverB>;

:19561


This thread was automatically locked due to age.
Parents
  • 0
    Can't check the details as I'm at home. When you "manualy" moved the database - did you run the installer on the SQL server? Normally if you do so, then export and uninstall the DB on the management server, import on the database server and then start the console it will ask you for the database location. Entering the correct database will take care of the registry keys (and make subsequent upgrades simple).
    There should be a more specific error in the installer log why the connection failed. On the long run using only the installer(s) makes life easier. Some time ago I've played with moving around the database (including making the local database a remote one). As long as you have a current export nothing bad will happen. So you could just try to install the 4.7 database using the installer, re-import it and then try the 5.0 installer (which, as Jak said, would then "just" create the new databases).

    Christian
    :19615
Reply
  • 0
    Can't check the details as I'm at home. When you "manualy" moved the database - did you run the installer on the SQL server? Normally if you do so, then export and uninstall the DB on the management server, import on the database server and then start the console it will ask you for the database location. Entering the correct database will take care of the registry keys (and make subsequent upgrades simple).
    There should be a more specific error in the installer log why the connection failed. On the long run using only the installer(s) makes life easier. Some time ago I've played with moving around the database (including making the local database a remote one). As long as you have a current export nothing bad will happen. So you could just try to install the 4.7 database using the installer, re-import it and then try the 5.0 installer (which, as Jak said, would then "just" create the new databases).

    Christian
    :19615
Children
No Data