There may be a time when you need to move your Sage 100 database from one SQL server to another without also moving the server that the core Sage 100 is installed to.
Fortunately, this is not a big project. Sage has documented the steps in their knowledgebase.
What you’ll need to do is create MAS_USER and MAS_REPORTS on the new SQL server, backup and restore the data to the new server from the old server and then run a Sage utility to point Sage 100 to the new SQL Server location.
Follow this link to the Sage knowledge base for the details on how to move your Sage 100 SQL server database from one SQL server to another SQL server while keeping Sage 100 Premium installed to the same underlying server.
Sage 100 Premium ( aka SQL ) is available as a no-cost upgrade from most users who are on Sage 100 subscription. The migration from Standard or Advanced is well documented. The primary benefits of using a SQL database with Sage 100 are (a) security over data tables ( which are all protected by SQL security ) and (b) significantly faster external reporting ( your standard Sage 100 reports on the menus will typically be about the same speed but anything attached directly to the SQL database will report much quicker).
If you’ve been pondering a move from Sage 100 Standard or Advanced to Sage 100 Premium ( SQL ) then you may wish to review my Sage 100 Premium FAQ which outlines in more detail the pros and cons of using a SQL database attached to Sage 100.