Sage 100

I'm getting ready to upgrade a client from v2019 to v2022 with the current servers in place. The client requested that I upgrade the current install rather than building out new servers. Currently sage premium and SQL are on different servers.

My questions are:

1. When it says in the documentation "New SQL Instance" what does this mean....create a new database inside of SQL server or brand new install of SQL?

2. When your upgrading Sage premium on the same server is this the best KB to follow from the Sage knowledgebase? (How to upgrade to Sage 100 premium 2015 or higher) - KB 62630 attached below. I was told by support to follow these directions when it come to upgrading premium on the same server. 

3. Normally I run clients in parallel mode with the standard and advanced versions so they can test everything with third party software before they go live. I was told you can run parallel for premium clients as long as it's on separate servers with a separate instance of SQL. Is this correct from sage support?

I'm new to this as you can tell and I have so many questions because I strive to have smooth upgrades for my clients. I don't have access to a DBA. I'm trying to gain better knowledge because I don't have a programming background and limited resources when the upgrades are schedule after hours or over a weekend. I appreciate everything who has helped me in the past with my prior posts.

------------------------------
Shannon Stanley
Sage 100 Consultant
Ardent Consulting LLC
------------------------------

1) You'll have to have a second SQL Server Instance (meaning another install), but the good news is that you can run multiple Instances on a single server. You'll just have to use a new Named Instance (i like "Sage2022")
2) The directions seem fine, though it's missing the first step: install a second SQL instance. When installing, I always use SQL Authentication to connect to the instances (it'll default to Windows Authentication)
3) You can do a MAS 90 Mode with Premium (see second section of this page) though they still have the limit of only being in one at a time.

I find it very easy to get confused which SQL Instance you're working in, so make sure to have backup/snapshot of the databases and MAS90 folder before beginning.

------------------------------
Steve Iwanowski, NextStep Technology Advisors, aka DSD Lancaster PA ¯\_(ツ)_/¯
------------------------------

As Steve said you need a 2nd instance for the install and migration... but it can be temporary.  If the customer wants to move things back to the original SQL instance (to run Live from the same SQL environment...) after the migration data processing, that is possible if the versions of SQL are identical (down to the patch level) and work for both versions of Sage 100 involved in the upgrade.  Same server, same SQL instance for running Live, but the install / migration needs another SQL install.
(There is the merge method, but it is much more complicated and risky than the regular migration process).
This shows 3 SQL installs on one machine.
The first one is the default "unnamed" instance, aligning with the bottom connection below.  Otherwise you connect with servername\instancename as the SQL server.


------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
------------------------------