Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 9 replies
  • Subscribers 1 subscriber
  • Views 3363 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

Remote SQL Server and 4.0 -> 4.5 Console Upgrade

Dean_F
Ok, so I ran the upgrade adviser tool and it flagged my current 4.0 system because I have a remote SQL server. I get the warning, "Non-Sophos databases have been added to the SOPHOS instance. Applications relying on these databases may stop working after the upgrade." Of course there are other databases, it's an SQL Server. Will this warning affect me and will my other DB's really encounter problems if I were to continue? I had a heck of a time getting the 4.0 db to load on a real SQL Server.
:3920


This thread was automatically locked due to age.
Parents
  • 0

    Hi,

    The upgrade works by creating a "empty" SOPHOS45 database, this should be done first in the upgrade step of a distributed install.  This is either created by running the installer on the machine or running installDB.  Once the "empty" SOPHOS45 database is created, you then run the installer on the management server machine, as part of this install the tool UpgradeDB.exe is called and moves the data from SOPHOS4 to SOPHOS45.

    Thanks,

    Jak

    :4080
Reply
  • 0

    Hi,

    The upgrade works by creating a "empty" SOPHOS45 database, this should be done first in the upgrade step of a distributed install.  This is either created by running the installer on the machine or running installDB.  Once the "empty" SOPHOS45 database is created, you then run the installer on the management server machine, as part of this install the tool UpgradeDB.exe is called and moves the data from SOPHOS4 to SOPHOS45.

    Thanks,

    Jak

    :4080
Children
No Data
Unfiltered HTML