Hi Nico 

Certainly, please open this link for a detailed article on your query.

http://kb.pastel.co.za/article.php?id=4807

Kind regards

Bennie 

Hi Bennie,

Thanks for the reply.  Do you have a list of Database Schema Changes that were made in 9.2 (any release notes on the 9.2. version as well) so that we can look into the impact that this upgrade could have on our 3rd-Party Integration (heavily use the SDK Developer kit?  We are very worried that this will break some of our key downstream systems, working off Sage 200 Evolution 7.2...

I was also wondering...we are running SQL Server 2017 Standard Edition.  What Compatibility-mode should we run the databases in, following the backup and restore.  We're currently running the databases in Compatibility-mode of 100 (SQL2008) and we have tried to change it, but it has impacted performance severely.

Thanks again,

Nico

Hi Nico

Apologies for the late response as I had some technical difficulties in attaching a PDF guide on this post.

However, within the Sage Evolution version 9.20 install folder (that you can download form the Sage FTP website), you should find the Release Notes folder.

In here open the Release Notes that include all the changes made since the previous version of Evolution.

Of course, when it comes to SDK integrations we always recommend a test upgrade and run some extensive and careful testing on the test environment first.

With regards to your second query:
We always recommend setting the Compatibility level in MS SQL Management Studio to be the highest available.

Else, please let us know if you're observing slowness in the company if the setting is on the highest.

Regards

Bennie 

Thanks Bennie, thanks for the response.

I've found the 23-page PDF.  Not quite what I was looking for...for example, in our testing thus far, it's been highlighted that the ItemGroup-column was removed from the StkItem-table.   I was wondering, where was that moved to?  Is there an updated Data-Dictionary available on 9.2?  Also, die backup-restore route won't work entirely, because like for example with the ItemGroup-column being removed, that data needs to be migrated to the "new" location...so, this upgrade will break all of our SDK integration as well as our BI Reporting...

Yes, so currently Sage Evolution 200 v7.2 is running in compat-mode 100 on SQL 2017...we tried to change the compat-mode to 140, but it basically degraded performance to such an extent (CPU 100%, drastically reducing response times), we had to switch it back to compat-mode 100.  Hopefully, this was part of the changes in v9.2, with the queries on the db-side re-written to take into account the new cardinality estimator changes in the newer version of SQL supporting the native/highest compat-mode level - but I can't find any evidence in the release notes quoted here.

Lastly, can you please confirm how much longer we can "safely" remain on v7.2?  I'm looking for some official reference material from Sage, for example this from Microsoft: https://support.microsoft.com/en-za/lifecycle/search?alpha=sql%20server%202017

Microsoft is very clear on Mainstream Support and Extended Support End Dates - thus, we're able to plan our upgrade plan and strategy going forward. What is the official corporate response from a Sage regarding Evolution 200 v7.2 please?  Because this upgrade from v7.2 to 9.2 is massive with major risk at what cost...

Hi Nico

I think the best way forward will be to open a new official query incident on our side to properly research and respond to your queries above.

Since we don't prefer clients state their e-mail addresses on this platform, please send all of the the above to [email protected] for my attention as requested by myself.. I will then formally research from the newly created incident.

Regards

Bennie 

you get any support on this 

Regards

Hi Chisanga

Is there perhaps anything specific I can assist with here?

Kind regards

Bennie