Hi,
We've been having some trouble setting up pre-production environments based on clones of our live environments. The thought was that we could use a copy of the live server, rename it and bring it online as a pre-production server and rename anything on the SQL side to re-establish any links. I believe it would follow the below process;
https://docs.microsoft.com/en-us/sql/database-engine/install-windows/rename-a-computer-that-hosts-a-stand-alone-instance-of-sql-server?view=sql-server-ver15
The issue is that after the host rename, the SQL services all stop running and cannot be started, so the above cannot be completed as there's nothing to connect to and run the T-SQL. Are we missing something in the order we are completed this or our understanding of creating these copies? Or could it be the username against the service since we've changed host names? We use windows authentication if that makes a difference to the process/settings.
I know we could create a server from scratch, install SQL server, and use replication to copy and maintain the data as this is pretty much how we have been creating a Developer environment - however the goal is to make sure the pre-production environment as (ideally) an identical copy to live in every way - including the build/install and not just the data.
We were concerned this method might leave us having used different install options or components to the live version that could cause issues later on when work is deployed to live as there could be more variables. If this is the correct/only method then could there be a report that can be run on live to establish these options and components to allow us to manually build an accurate copy?
As you may guess, there was no previous management of this and we have no documentation for any environments.
Thank you for any help and advice.
We've been having some trouble setting up pre-production environments based on clones of our live environments. The thought was that we could use a copy of the live server, rename it and bring it online as a pre-production server and rename anything on the SQL side to re-establish any links. I believe it would follow the below process;
https://docs.microsoft.com/en-us/sql/database-engine/install-windows/rename-a-computer-that-hosts-a-stand-alone-instance-of-sql-server?view=sql-server-ver15
The issue is that after the host rename, the SQL services all stop running and cannot be started, so the above cannot be completed as there's nothing to connect to and run the T-SQL. Are we missing something in the order we are completed this or our understanding of creating these copies? Or could it be the username against the service since we've changed host names? We use windows authentication if that makes a difference to the process/settings.
I know we could create a server from scratch, install SQL server, and use replication to copy and maintain the data as this is pretty much how we have been creating a Developer environment - however the goal is to make sure the pre-production environment as (ideally) an identical copy to live in every way - including the build/install and not just the data.
We were concerned this method might leave us having used different install options or components to the live version that could cause issues later on when work is deployed to live as there could be more variables. If this is the correct/only method then could there be a report that can be run on live to establish these options and components to allow us to manually build an accurate copy?
As you may guess, there was no previous management of this and we have no documentation for any environments.
Thank you for any help and advice.