General Consultant Discussion

We have a client with 70 GB of data in their MAS_XXX folder. They are on Sage 100 Standard with 10 user licenses but usually have about 7 users in the system. What are the considerations or flags to move a client to Advanced or Premium? They are not complaining about performance except when printing some of the custom crystal reports because there is a lot of data for the report to filter. Recommendations would be appreciated. Thank you!

Last I heard, they could move to Sage 100c and at the same time move to Sage 100 Advance, for the same price. It may be the perfect time for them to consider a move such as this.

Wow, that is a lot of data. Do you want to make a sale or just speed things up for them? If you move them to subscription, don't they get to move at NC? Can they purge some of their data? that would speed things up. If only a few reports are slow, consider Pass Through Queries via and Access database. I have had some clients run the SAME Crystal report 10X faster simply by using Access. Did you write the Crystal reports for them? @ThereseLogeais has rewritten some for me that are now screaming fast for the client. DSD has a SQL mirror product that might work for them.

Just to free up some space, I would suggest you delete the temporary work files that the application creates. This may help improve processing speed for those few crystal reports. *wrk*1*.m4t *wrk*0*.m4t *work*1*.m4t *work*0*.m4t *.old *.new *.nwt

One other file type I try and keep clean are the *.rp_ for Crystal report/form conversions.

What @MadelineStefanou said but typically only if there is an observed speed concern or Sage 100c maintenance < Sage 100

Thanks for your comments. Can you give me a reason to move to Premium versus Advanced? Is one product much better than the other? Also, this client has payroll. Can they even use Premium?

Having any non-framework modules (or EBM) rules out Premium. The pass-through query idea can be done with SQL Express as well with better control over security and unauthorized changes than with Access. Be sure to install the 32bit SQL for ODBC compatibility.

I've used 64-bit SQL to query Providex DSN's using the 64-bit ODBC driver (but only the version that comes with 2014 or later).

The reporting bottlenecks can probably be removed by pruning old invoice and IM-related data. Leave the full amount in an archive db, and use the pruned db (say, 2yrs of data) for operational going forward.