1. Make a new server with a new name

2. Install SQL

3. Backup and restore the databases from old to new

4. Run Sage database setup to select the new server

I would like to be able to just use the existing system but take it from the backup.  So my backup software can do CDP so I can have an up to date system in backup form.  I would like to bring those online (with networking off) and start up the backup sage 300 server and backup sql server and rename the physical servers and the sql instance.

Do you think that is actually more work than just creating a new server and installing sql and then bringing up the backup Sage 300 server?

Thanks

You can't rename SQL instances, and you can't have two servers with the same name.  I don't know why you're going through all this, I don't see the benefit, unless you're just doing a disaster recovery test.

yes, sorry, that is exactly what I am doing.   I am doing disaster recovery testing and then once it is up I am also going to do a few configuration changes and see what they do and if they do what I want I would do them in the live version.

I found out that you can do it:

"it is possible to rename the named instance of SQL server 2K, first use sp_dropserver and sp_addserver (drop the old server name and add new server name in sysservers table). Turn down the instance and create the same folder structure as the old installation folder for this renamed instance, both for installation folders and data folder appropriately i.e $OldInstanceName to $NewName, also search and replace this old instance name in registery.

then run the "rebuildm" utility for rebuilding the system databases now reboot the system and make sure SQL server is running under new name. Then detach and attache the user databases to the new location (new folder i.e $NewName)"

But why would you want to.  The path you have specified seems the best.  

So if I plan to restore sql, then just uninstall and reinstall and import the tables ( which I have from backup )  is it a problem to restore the Sage 300 and point that to my new instance if I change the sage 300 server name.  Or do I need to do more changes than just the server name for Sage 300 to work correctly?  (other than running sage database setup)

Thanks for your time and patience with me.  It is appreciated.

You are W-A-A-A-Y overthinking this.  With Sage, you do a full SQL backup, then a simple restore, that's it. There's no moving tables around, and don't bother with incremental SQL logs.

You are W-A-A-A-Y overthinking this.  With Sage, you do a full SQL backup, then a simple restore, that's it. There's no moving tables around, and don't bother with incremental SQL logs.

Ok, so could I do a full sql backup, then restore the db as a different name and just point my new Sage 300 server at that restored DB and not even restore the db server?

sorry, I am new to Sage 300, this has been placed in my to do basket, I am a linux and web admin.

No, you can't change the DB name.  You backup OLDSERVER..MYDAT, restore to NEWSERVER..MYDAT, then run database setup to change from OLDSERVER to NEWSERVER.  

Ok, got it.  I will keep it simple as you have suggested.  Thank you very much for your help.