• Status: Solved
  • Priority: Low
  • Security: Public
  • Views: 67
  • Last Modified:

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.
0
rayluvs
Asked:
rayluvs
  • 5
  • 3
  • 2
3 Solutions
 
David Johnson, CD, MVPOwnerCommented:
yes there will be a conflict with the computername
1
 
rayluvsAuthor Commented:
Is there a workaround?
0
 
David Johnson, CD, MVPOwnerCommented:
if you are only accessing the database locally (on the pc) there is no problem.. from another computer then you'd have to use ip address\instance name.. having 2 computers on the same network with the same name is always problematic
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
rayluvsAuthor Commented:
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')' it gave the NOW name of the computer.

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
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
Please follow this MSDN article to fix the server name change.
What about the IP Address? A network doesn't accept two identical IPs on it.
0
 
rayluvsAuthor Commented:
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?
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
Mind that "(local)" can only be used inside the server. Remote connections do need the server name or IP address.
0
 
rayluvsAuthor Commented:
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?
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
If the only purpose is that, then the answer is no.
0
 
rayluvsAuthor Commented:
Thanx!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Amazon Web Services - Basic

Are you thinking about creating an Amazon Web Services account for your business? Not sure where to start? In this course you’ll get an overview of the history of AWS and take a tour of their user interface.

  • 5
  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now