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.
rayluvsAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
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
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.