Sage 100

I have a customer running Sage 100 and SQL on the same server. The IT group installed another instance of SQL but named both of the SQL instances have similar names. Is this going to cause any issues when I installed another version of Sage on this server and both Sage versions are running in parallel? I want to verify what I was told about SQL instances running on the same server needed to have different names. Was I told the correct information by Sage Support? I'm just not sure if I got bad information and wanted to verify with the experts of the SQL world before I upgraded this client. TIA.

Sage 2020 is pointed to SSP-SAGE

Sage 2023 will be pointed to SSP-SAGE\MSSQLSERVER2019

(attached screenshot....they say a picture is worth a thousand words:)

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

That should be fine

------------------------------
Phil McIntosh
President
Friendly Systems, Inc.
------------------------------

They're correct that different instances require different names, and having two instances is actually required when migrating one Premium version to another.

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

I would say about 50% of my Premium customers can get so far as spelling SQL and setting up a default instance. It would be really helpful to have background information to provide to those less technical customers about SQL and the various ways that it could be configured - starting with perhaps whether the customer should buy the SQL through Sage or not (and why) and what type of reference material is available about creating another instance of SQL and how/why that's needed.

It's a lot better if this information comes from their Sage partner as opposed to the customer calling Sage who sometimes knows and other times doesn't. 

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT
------------------------------

Original Message:
Sent: 09-13-2023 08:58
From: Carmen Cruz
Subject: Sage Premuim question about SQL instances

The client can have as many instances of SQL on a server as they want. However, it's a stupid idea because it's going to put a lot of pressure on the server. Both Sage and the database on the same server can be an issue depending on user traffic. But, that's up to the client. 

	Carmen Cruz Sage Consultant carmen.cruz@compudata.com 215-969-1000 Ext. 279 www.compudata.com Work Smarter... Together
CompuData, Inc. • 325 Chestnut St, Ste 700 • Philadelphia • PA • 19106

Original Message:
Sent: 9/13/2023 9:59:00 AM
From: Wayne Schulz
Subject: RE: Sage Premuim question about SQL instances

I would say about 50% of my Premium customers can get so far as spelling SQL and setting up a default instance. It would be really helpful to have background information to provide to those less technical customers about SQL and the various ways that it could be configured - starting with perhaps whether the customer should buy the SQL through Sage or not (and why) and what type of reference material is available about creating another instance of SQL and how/why that's needed.

It's a lot better if this information comes from their Sage partner as opposed to the customer calling Sage who sometimes knows and other times doesn't. 

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT
------------------------------

Thanks everyone for your help!

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

Original Message:
Sent: 09-13-2023 10:27
From: Carmen Cruz
Subject: Sage Premuim question about SQL instances

Would you guys like for me to write up some kind of instructional that explains SQL instances, and when and why they would be needed?

	Carmen Cruz Sage Consultant carmen.cruz@compudata.com 215-969-1000 Ext. 279 www.compudata.com Work Smarter... Together
CompuData, Inc. • 325 Chestnut St, Ste 700 • Philadelphia • PA • 19106

Original Message:
Sent: 9/13/2023 9:59:00 AM
From: Wayne Schulz
Subject: RE: Sage Premuim question about SQL instances

I would say about 50% of my Premium customers can get so far as spelling SQL and setting up a default instance. It would be really helpful to have background information to provide to those less technical customers about SQL and the various ways that it could be configured - starting with perhaps whether the customer should buy the SQL through Sage or not (and why) and what type of reference material is available about creating another instance of SQL and how/why that's needed.

It's a lot better if this information comes from their Sage partner as opposed to the customer calling Sage who sometimes knows and other times doesn't. 

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT
------------------------------


Original Message:
Sent: 09-13-2023 08:58
From: Carmen Cruz
Subject: Sage Premuim question about SQL instances

The client can have as many instances of SQL on a server as they want. However, it's a stupid idea because it's going to put a lot of pressure on the server. Both Sage and the database on the same server can be an issue depending on user traffic. But, that's up to the client. 

	Carmen Cruz Sage Consultant carmen.cruz@compudata.com 215-969-1000 Ext. 279 www.compudata.com Work Smarter... Together
CompuData, Inc. • 325 Chestnut St, Ste 700 • Philadelphia • PA • 19106

Ideally I would love to see this document updated and expanded. Perhaps the FAQ type items ( aka SQL Instances ) could be added to this?  Premium is going to become more important in the future as additional customers migrate. And my prediction is Sage will have far fewer technical resources to support Premium or even answer general questions ( FAQs ).

https://docs.google.com/document/d/1_y2wlmQSZGVtew4zVctpQKZKnQX0kl-lcTWUZ8UdIKM/edit?usp=sharing

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT
------------------------------

Original Message:
Sent: 09-13-2023 10:27
From: Carmen Cruz
Subject: Sage Premuim question about SQL instances

Would you guys like for me to write up some kind of instructional that explains SQL instances, and when and why they would be needed?

	Carmen Cruz Sage Consultant carmen.cruz@compudata.com 215-969-1000 Ext. 279 www.compudata.com Work Smarter... Together
CompuData, Inc. • 325 Chestnut St, Ste 700 • Philadelphia • PA • 19106

Original Message:
Sent: 9/13/2023 9:59:00 AM
From: Wayne Schulz
Subject: RE: Sage Premuim question about SQL instances

I would say about 50% of my Premium customers can get so far as spelling SQL and setting up a default instance. It would be really helpful to have background information to provide to those less technical customers about SQL and the various ways that it could be configured - starting with perhaps whether the customer should buy the SQL through Sage or not (and why) and what type of reference material is available about creating another instance of SQL and how/why that's needed.

It's a lot better if this information comes from their Sage partner as opposed to the customer calling Sage who sometimes knows and other times doesn't. 

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT
------------------------------


Original Message:
Sent: 09-13-2023 08:58
From: Carmen Cruz
Subject: Sage Premuim question about SQL instances

The client can have as many instances of SQL on a server as they want. However, it's a stupid idea because it's going to put a lot of pressure on the server. Both Sage and the database on the same server can be an issue depending on user traffic. But, that's up to the client. 

	Carmen Cruz Sage Consultant carmen.cruz@compudata.com 215-969-1000 Ext. 279 www.compudata.com Work Smarter... Together
CompuData, Inc. • 325 Chestnut St, Ste 700 • Philadelphia • PA • 19106