Upgrading Sage 100 Premium 2019 to 2021 ending in the same default SQL instance

I have a client using Sage 100 Premium for core accounting for 200 companies installed in the default instance. I need to upgrade for 2019 to 2021, what is the procedure to keep using the default instance on a single server? Ideas? There are multiple .NET integrations and the are compiled using the default server instance \\SERVER\MSSQLSERVER:1433.

Parents
  • 0

    Do the full upgrade using a new / temp SQL instance (using the exact same version / patch level as the existing SQL). 

    Then after the migration / conversion is done you can move the databases back to the original instance, correct the permissions, and use the Premium SQL configuration tool to point new Sage to the right place (while manually ensuring the old Sage is completely disabled).

  • 0 in reply to Kevin M

    Hey Kevin - I'm about to do the same thing - upgrade 2019 to 2022 Premium.  We are not upgrading application server or sql server.  My plans are to create a temporary instance on the same SQL server and migrate to that.  When the migration/conversion is complete, I'll copy (MAS_XXX, MAS_SYSTEM) them from temp instance overriding our current instance, eventually removing the temp and disabling the old Sage residing on the application server.  When you suggest "...use the Premium SQL configuration tool..." is that within SQL?  

  • 0 in reply to RRUFF

    It's a program that gets added to the Start Menu on the Sage server.  That is where you tell Sage 100 to find the SQL database (and set passwords for the SQL accounts used by Sage).

    Be careful with Test Connection.  (I've had that crash on me in some versions).

    After moving the databases, before using the above utility to point Sage at the moved databases, run this script against each one (including MAS_System).

    use MAS_###;

    exec sp_changedbowner 'MAS_User';

    exec sp_dropuser 'MAS_Reports';

    exec sp_grantdbaccess 'MAS_Reports';

    exec sp_addrolemember 'db_datareader', 'MAS_Reports';

  • 0 in reply to Kevin M

    Makes sense.  Always appreciate your insight!

Reply Children
No Data