Change sql server connection properties in cloned server
Hi Experts, I was given a cloned copy of a live sql server to do some testing with one default instance. I was under the impression that the cloned server would be an independent server. But while doing the testing i realised that the sql instance is still pointing to the live server instance so any change in the cloned server instance is reflected in the live instance. Having then looked at the connection properties of the cloned instance i realised that the server name and computer name is that of the live server. I then created a named instance on the clone and it seems to point at the current cloned server. My question is how can i change the connection properties in the sql instance of the cloned server to point to the cloned server rather than the live server. Both the servers are in the live domain .
Hi John, Thank you for your reply. Sorry I was not clear. A third party application is to be upgraded. For this they need us to upgrade SQL 2012 to SQL 2016. As we don't have a test server for this application I asked for a test VM to be cloned from the live VM so that I could test the upgrade to 2016 and the users could test the reports before upgrading the live server. On the test VM, the sql server name is the same as the live. I suppose it should be the same as the VM is cloned. I thought that both VMs were independent of each other as I was told it was a full clone so no linked server. But if I take a backup of a database in the cloned VM, I cannot see it in the backup folder of the cloned VM but can see in the live VM. Similarly if I create a database in the test VM Management Studio, it can be seen in the Live VM Management Studio. So though they are two separate VMs, they are connected. So the purpose of having a test machine is defeated. I can’t get more information on this as the person who created this is on leave for 4 days. So I will have to either wait or try to sort this out. Thanks