Sage 100

Any ramification to using SQL to move the database from one server to another if we have sufficient performance. Any configuration changes in Sage?

According to this KB https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=42996&sliceId=1&cmd=displayKC&dialogID=96116&docType=kc&isLoadPublishedVer=&stateId=96130&docTypeID=DT_Article&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl you have to migrate it, but that includes moving the installed program files as well as the database. I believe somewhere Sage does recommend keeping them on the same server, maybe because some of the data is still in ProvideX files?? If just moving the database, I would think that the SQL settings utility would let you change the database location Sage 100 is looking for. After moving the databases, you will need to make sure that MAS_User on the new SQL server is the actual owner of them. In SQL Management studio on the new server: EXEC sp_changedbowner 'MAS_User' for each Sage 100 database. Note that I have not actually done this, so test it and leave yourself a way back...

I've done it a few times. Stop the service, create DB backups, restore the backups (making sure you put the mdf / ldf files where you want them), deal with the permissions (don't forget about MAS_Reports) and use the Sage utility to re-point the service to the the new instance. Any external connections will have to be moved too (silent DSN's, excel queries...). Once tested we disable the old SQL instance when we do this to force people to use the current database. If something goes wrong, the old SQL instance is still there, and you just reverse the Sage settings to point back to the original server.

Just for clarity we are not moving to a new server or SQL instance. The install was put to the C drive when installed and we are just moving the databases to D. We are then also going to set the defaults so any future databases will go to the D drive.