Sage 100

Question on premium - is there a architecture guide that talks about what code is executing in each layer (client / application / sql server) and what the latency requirements between each layer are if they are installed on separate machines?

------------------------------
Madeline Stefanou
RKL eSolutions, LLC
------------------------------

I don't think so. I had a customer call Sage asking this type of question and they don't appear to have gotten very far. This is too bad because as Sage 100 ages the customers are becoming larger in size and more technical. These customers are starting to ask more technical questions and Sage does not seem prepared to answer these questions.

I have the same question in the area of user rights. Sage has no detailed explanation of exactly what rights are required for the installation and use of various versions. ( Sage does provide limited guidance in the back of their installation guide however it appears at least partly out-of-date and Sage support is not helpful in providing additional information)

------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990
------------------------------

I don't know of a guide either. When Sage began with MAS 200 for SQL many years ago there was a certification class that I attended at BDO Siedman outside of Detroit.  We had a manual for the class.  Some 90 Minder may have saved it. I doubt if the concepts have changed much. The instructor mentioned that if all possible keep the SQL server on the same physical hardware as the programs.  Of course the SQL server should not be on the same partition as the OS and the transactions logs should be on separate physical drives from the database. Based on my experience this is true. If IT insists on the SQL server being on a separate physical server as the Sage 100 programs then you should recommend they have a dedicated fiber backbone between the servers.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Assistant to the Traveling Secretary
------------------------------

It would be hugely beneficial to have such a document that not only made these recommendations but also provided the "Why" behind them. I can count on half of one hand the number of customers who would ask me these technical questions and NOT want to know "why".

The money to be made with Sage is with the more sophisticated sites that have many users and need to be on a more advanced edition like Premium/SQL. These sites also tend to ask quite a few questions and they aren't impressed when there are no answers ( especially if they pick up the phone to call Sage and don't get anywhere ).

More of this type of inquiry is moving online so I suspect Sage City could continue to grow if they dedicate some resources to answering questions. As it stands now Sage City has a lot of questions that can go unanswered for days and this also does not impress the larger more sophisticated type of customer.

------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990
------------------------------

Original Message:
Sent: 02-20-2020 12:06
From: Doug Higgs
Subject: Premium Guides

I don't know of a guide either. When Sage began with MAS 200 for SQL many years ago there was a certification class that I attended at BDO Siedman outside of Detroit.  We had a manual for the class.  Some 90 Minder may have saved it. I doubt if the concepts have changed much. The instructor mentioned that if all possible keep the SQL server on the same physical hardware as the programs.  Of course the SQL server should not be on the same partition as the OS and the transactions logs should be on separate physical drives from the database. Based on my experience this is true. If IT insists on the SQL server being on a separate physical server as the Sage 100 programs then you should recommend they have a dedicated fiber backbone between the servers.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Assistant to the Traveling Secretary
------------------------------

​thank you both.   I actually still have that manual from the v4.45 SQL Fundamental Training Course.  I should go pull it out to see if it has any useful details.  Thank you.

------------------------------
Madeline Stefanou
RKL eSolutions, LLC
------------------------------

Original Message:
Sent: 02-20-2020 12:06
From: Doug Higgs
Subject: Premium Guides

I don't know of a guide either. When Sage began with MAS 200 for SQL many years ago there was a certification class that I attended at BDO Siedman outside of Detroit.  We had a manual for the class.  Some 90 Minder may have saved it. I doubt if the concepts have changed much. The instructor mentioned that if all possible keep the SQL server on the same physical hardware as the programs.  Of course the SQL server should not be on the same partition as the OS and the transactions logs should be on separate physical drives from the database. Based on my experience this is true. If IT insists on the SQL server being on a separate physical server as the Sage 100 programs then you should recommend they have a dedicated fiber backbone between the servers.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Assistant to the Traveling Secretary
------------------------------

I never saw any such document, but for clients who were interested in going to Premium we would run a test migration using our NFR keys and then run before and after tests (so they could go in with their eyes open)... Not sure if this answers your question but we found that standard work table based reports like AR Aging ran 1.5-2 times slower, data entry was a tad bit slower, VI jobs were slightly slower as well as other import routines (i.e. Mapadoc). Of course any other form of data extraction, even BI Explorer views, lookups, ODBC queries, and custom Crystal were lightning fast in comparison.

---------------------------------
Andrew Hagenbach

Hagenbach Solutions, LLC
---------------------------------

I found a KB article which seemed to imply that the standard reports on the Sage menu could have their connection replaced with one that read directly from SQL.

Wondering if that has any speed impact.

---------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990
---------------------------------



Original Message:
Sent: 02-22-2020
From: Andrew Hagenbach
Subject: RE: Premium Guides

I never saw any such document, but for clients who were interested in going to Premium we would run a test migration using our NFR keys and then run before and after tests (so they could go in with their eyes open)... Not sure if this answers your question but we found that standard work table based reports like AR Aging ran 1.5-2 times slower, data entry was a tad bit slower, VI jobs were slightly slower as well as other import routines (i.e. Mapadoc). Of course any other form of data extraction, even BI Explorer views, lookups, ODBC queries, and custom Crystal were lightning fast in comparison.

---------------------------------
Andrew Hagenbach

Hagenbach Solutions, LLC
---------------------------------

@Madeline Stefanou contact @Carmen Cruz in our group.  She may have this information.  ​​​

------------------------------
Moira Goggin
Executive Director
90 Minds, Inc.
------------------------------

Original Message:
Sent: 02-22-2020 15:53
From: Wayne Schulz
Subject: Premium Guides

I found a KB article which seemed to imply that the standard reports on the Sage menu could have their connection replaced with one that read directly from SQL.

Wondering if that has any speed impact.

---------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990
---------------------------------




Original Message:
Sent: 02-22-2020
From: Andrew Hagenbach
Subject: RE: Premium Guides

I never saw any such document, but for clients who were interested in going to Premium we would run a test migration using our NFR keys and then run before and after tests (so they could go in with their eyes open)... Not sure if this answers your question but we found that standard work table based reports like AR Aging ran 1.5-2 times slower, data entry was a tad bit slower, VI jobs were slightly slower as well as other import routines (i.e. Mapadoc). Of course any other form of data extraction, even BI Explorer views, lookups, ODBC queries, and custom Crystal were lightning fast in comparison.

---------------------------------
Andrew Hagenbach

Hagenbach Solutions, LLC
---------------------------------

Good point @Wayne Schulz. An OLE DB connection is lower level than an ODBC connection and should be more efficient.  You may consider changing the data source on any custom reports when using Premium.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Assistant to the Traveling Secretary
------------------------------

Original Message:
Sent: 02-22-2020 15:53
From: Wayne Schulz
Subject: Premium Guides

I found a KB article which seemed to imply that the standard reports on the Sage menu could have their connection replaced with one that read directly from SQL.

Wondering if that has any speed impact.

---------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990
---------------------------------




Original Message:
Sent: 02-22-2020
From: Andrew Hagenbach
Subject: RE: Premium Guides

I never saw any such document, but for clients who were interested in going to Premium we would run a test migration using our NFR keys and then run before and after tests (so they could go in with their eyes open)... Not sure if this answers your question but we found that standard work table based reports like AR Aging ran 1.5-2 times slower, data entry was a tad bit slower, VI jobs were slightly slower as well as other import routines (i.e. Mapadoc). Of course any other form of data extraction, even BI Explorer views, lookups, ODBC queries, and custom Crystal were lightning fast in comparison.

---------------------------------
Andrew Hagenbach

Hagenbach Solutions, LLC
---------------------------------

Hi Wayne.  Indeed the reports in Premium do use the native SQL client and run much quicker that SOTAMAS90 ODBC.   Has to use this connection as there are only a handful of Providex tables in Premium, everything else is in SQL.

------------------------------
Bob Osborn
Consultant
ACI Consulting
------------------------------

Original Message:
Sent: 02-22-2020 15:53
From: Wayne Schulz
Subject: Premium Guides

I found a KB article which seemed to imply that the standard reports on the Sage menu could have their connection replaced with one that read directly from SQL.

Wondering if that has any speed impact.

---------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990
---------------------------------




Original Message:
Sent: 02-22-2020
From: Andrew Hagenbach
Subject: RE: Premium Guides

I never saw any such document, but for clients who were interested in going to Premium we would run a test migration using our NFR keys and then run before and after tests (so they could go in with their eyes open)... Not sure if this answers your question but we found that standard work table based reports like AR Aging ran 1.5-2 times slower, data entry was a tad bit slower, VI jobs were slightly slower as well as other import routines (i.e. Mapadoc). Of course any other form of data extraction, even BI Explorer views, lookups, ODBC queries, and custom Crystal were lightning fast in comparison.

---------------------------------
Andrew Hagenbach

Hagenbach Solutions, LLC
---------------------------------

Hi Madeline,
I apologize for my delay in response.  Premium guides for all version of installation were uploaded for 90 Minds and are extremely detailed.  There is also OFT files uploaded that are Office templates specific to flavor of Sage to address performance issues.  Let me know if you have any questions for me.

------------------------------
Carmen Cruz
Senior Specialist, Technical Consultant
SWK Technologies Inc.
Carmen.Cruz@SWKTech.com CA
973-437-3984
------------------------------

Fabulous!  Thanks for posting @Carmen Cruz
​

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Assistant to the Traveling Secretary
------------------------------

Original Message:
Sent: 03-04-2020 22:33
From: Carmen Cruz
Subject: Premium Guides

Hi Madeline,
I apologize for my delay in response.  Premium guides for all version of installation were uploaded for 90 Minds and are extremely detailed.  There is also OFT files uploaded that are Office templates specific to flavor of Sage to address performance issues.  Let me know if you have any questions for me.

------------------------------
Carmen Cruz
Senior Specialist, Technical Consultant
SWK Technologies Inc.
Carmen.Cruz@SWKTech.com CA
973-437-3984
------------------------------

Tip:
When moving databases between SQL instances (without the parallel migration tool), after creating MAS_User and MAS_Reports (password set using the Sage utility), the database permissions need to be configured.  Instead of going through the menus in SSMS, a simple script (run on each MAS_* database) can make that easier.


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

Original Message:
Sent: 03-04-2020 22:33
From: Carmen Cruz
Subject: Premium Guides

Hi Madeline,
I apologize for my delay in response.  Premium guides for all version of installation were uploaded for 90 Minds and are extremely detailed.  There is also OFT files uploaded that are Office templates specific to flavor of Sage to address performance issues.  Let me know if you have any questions for me.

------------------------------
Carmen Cruz
Senior Specialist, Technical Consultant
SWK Technologies Inc.
Carmen.Cruz@SWKTech.com CA
973-437-3984
------------------------------

Another important consideration when installing SQL server is less obvious, with a requirement buried in the install guide:

You can verify this is set correctly, in the SQL Server properties.  I do this as part of my pre-install checklist for Premium.


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

Original Message:
Sent: 03-05-2020 10:19
From: Kevin Moyes
Subject: Premium Guides

Tip:
When moving databases between SQL instances (without the parallel migration tool), after creating MAS_User and MAS_Reports (password set using the Sage utility), the database permissions need to be configured.  Instead of going through the menus in SSMS, a simple script (run on each MAS_* database) can make that easier.

use MAS_###;

exec sp_changedbowner 'MAS_User';

exec sp_dropuser 'MAS_Reports';

exec sp_grantdbaccess 'MAS_Reports';

exec sp_addrolemember 'db_datareader', 'MAS_Reports';

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


Original Message:
Sent: 03-04-2020 22:33
From: Carmen Cruz
Subject: Premium Guides

Hi Madeline,
I apologize for my delay in response.  Premium guides for all version of installation were uploaded for 90 Minds and are extremely detailed.  There is also OFT files uploaded that are Office templates specific to flavor of Sage to address performance issues.  Let me know if you have any questions for me.

------------------------------
Carmen Cruz
Senior Specialist, Technical Consultant
SWK Technologies Inc.
Carmen.Cruz@SWKTech.com CA
973-437-3984