can there be conflict ms sql when pc is cloned
After cloning a computer that run MS SQL server, can there be a problem with the SQL instance running as the cloned device? We were informed that there is computer name and the instance name and if cloned could be conflict to the cloned. Please advice.
David Johnson, CD
yes there will be a conflict with the computername
ASKER
Is there a workaround?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The process has been done (the computername has been changed so it would not conflict with the original computer - both will be on the same network).
Did noticed that the new cloned computer servername is the same as the source computer SQL servername (using 'select @@ServerName'). But ran 'select serverproperty('ServerName
So when used, we place "(local)" instead of the servername and it works, but it's ok to leave it like this? Or better yet, change the SQL instance server name?
Please advice
Did noticed that the new cloned computer servername is the same as the source computer SQL servername (using 'select @@ServerName'). But ran 'select serverproperty('ServerName
So when used, we place "(local)" instead of the servername and it works, but it's ok to leave it like this? Or better yet, change the SQL instance server name?
Please advice
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Different IPs.
Since we have to clone the computer for other purposes, we must go into each cloned-computer and change the server-name as-per-your-link to that cloned-computer name?
Also, if we don't do the renaming and keep using the cloned-computer (we one cloned computer running with "(local)"), is they any negative effect?
Since we have to clone the computer for other purposes, we must go into each cloned-computer and change the server-name as-per-your-link to that cloned-computer name?
Also, if we don't do the renaming and keep using the cloned-computer (we one cloned computer running with "(local)"), is they any negative effect?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Understood, that is how we are using it "inside the server" (the sole purpose is to work locally not being access remotely - this is a temporary task we have to do in these cloned-computers).
Prior closing, say after cloning we keep using "(local:, and it seems to work, is there any negative effect if we don;'t the renaming sql-server-name?
Prior closing, say after cloning we keep using "(local:, and it seems to work, is there any negative effect if we don;'t the renaming sql-server-name?
If the only purpose is that, then the answer is no.
ASKER
Thanx!