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

    This is not MSDE or SQL Express this is the full version of Microsoft SQL Server 2005 Standard Edition on another server. There are no "instances" in the full SQL Server that I'm aware of. That's all related to one of the tweaks I had to make to get 4.0 running with a remote, full Microsoft SQL Server 2005. Here's my current DatabaseConnectionMS in the registry that actually WORKS:

    Provider=SQLOLEDB;Integrated Security=SSPI;Initial Catalog=SOPHOS4;Data Source=SERVERNAME;

    To get the database connection, I had to remove the "\INSTANCE" name that all the documentation talks about. The "Initial Catalog=SOPHOS4" is the database name and "Data Source=SERVERNAME" refers to only the name of my server.

    :3924
Reply
  • 0

    This is not MSDE or SQL Express this is the full version of Microsoft SQL Server 2005 Standard Edition on another server. There are no "instances" in the full SQL Server that I'm aware of. That's all related to one of the tweaks I had to make to get 4.0 running with a remote, full Microsoft SQL Server 2005. Here's my current DatabaseConnectionMS in the registry that actually WORKS:

    Provider=SQLOLEDB;Integrated Security=SSPI;Initial Catalog=SOPHOS4;Data Source=SERVERNAME;

    To get the database connection, I had to remove the "\INSTANCE" name that all the documentation talks about. The "Initial Catalog=SOPHOS4" is the database name and "Data Source=SERVERNAME" refers to only the name of my server.

    :3924
Children
No Data
Unfiltered HTML