At Springboard, we know how to get you a job in data science. With Springboard’s Data Science Career Track, you’ll master data science with a curriculum built by industry experts. You’ll work on real projects, and get 1-on-1 mentorship from a data scientist.
Deploying SQL Server database backup into the new server environment with same name but different IP address
Hi People,
I'm in the process of migrating couple bunch of SQL Server 2005 Databases from the old hardware server into a virtual machine that I will be building with the exact same name but different IP address. (in other words it is using P2V (Physical to Virtual conversion).
Existing application connect by using Database2005 (IP 192.168.15.22), the new server will be the exact same name DATABASE2005 but with different IP 10.1.1.54.
How to make sure that the back end application can still talk to this newly created database without any issue ?
is there any caveats that I need to know or check before hand ?
Thanks in advance.
I'm in the process of migrating couple bunch of SQL Server 2005 Databases from the old hardware server into a virtual machine that I will be building with the exact same name but different IP address. (in other words it is using P2V (Physical to Virtual conversion).
Existing application connect by using Database2005 (IP 192.168.15.22), the new server will be the exact same name DATABASE2005 but with different IP 10.1.1.54.
How to make sure that the back end application can still talk to this newly created database without any issue ?
is there any caveats that I need to know or check before hand ?
Thanks in advance.
Who is Participating?
Are these in the same forest of in AD? Or, is this on your private network?
If you are dealing with the same forest in AD, your machine names will need to be different (DNS isssues, tombstones, etc.).
HTH..
If you are dealing with the same forest in AD, your machine names will need to be different (DNS isssues, tombstones, etc.).
HTH..
as long as the application connects to the server name, and not via the ip address, and as long as you also put in place the same logins/permissions the application uses, it will continue to work just fine.
the best way to know is to test this, with a DIFFERENT name, so you can review & test the application configuration with a test database/server ...
the best way to know is to test this, with a DIFFERENT name, so you can review & test the application configuration with a test database/server ...
Thanks kent,
the domain will still be the same only the AD site is different
Guy,
what do you mean by "as long as you also put in place the same logins/permissions" ?
does the Backup of the Database object in SQL Server 2005 also includes the Security & logins as well ?
the domain will still be the same only the AD site is different
Guy,
what do you mean by "as long as you also put in place the same logins/permissions" ?
does the Backup of the Database object in SQL Server 2005 also includes the Security & logins as well ?
I don't see any issue as long as your SQL server hostnames are same and configured in applications, U don't have to worry
Just ensure that DNS host(A) record points to correct IP in advance
Also if there is network \ software firewall in between SQL and application ensure that SQL static port (1433) or dynamic ports (If SQL is configured to listen on dynamic ports) are opened between SQL and application
You can check from application server whether connection to SQL is successful or not hopefully
Mahesh.
Just ensure that DNS host(A) record points to correct IP in advance
Also if there is network \ software firewall in between SQL and application ensure that SQL static port (1433) or dynamic ports (If SQL is configured to listen on dynamic ports) are opened between SQL and application
You can check from application server whether connection to SQL is successful or not hopefully
Mahesh.
Different AD site means separate/delegated?
To transfer login (sql server logins), http://support.microsoft.com/kb/918992
The issue deals with maintaining the same SIDs
sql server has logins and each database has the login account reference with the requisite security rights on the database.
The reference between the server login and the database account uses the SID.
To transfer login (sql server logins), http://support.microsoft.com/kb/918992
The issue deals with maintaining the same SIDs
sql server has logins and each database has the login account reference with the requisite security rights on the database.
The reference between the server login and the database account uses the SID.
Arnold,
The different is referring to the AD site when you issue Nltest /dsgetsite command.
But the domain is still in the same name.
The different is referring to the AD site when you issue Nltest /dsgetsite command.
But the domain is still in the same name.
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.
All Courses
From novice to tech pro — start learning today.
-
Course of the Month11 days, 9 hours left to enrollMonitoring and Operating a Private Cloud with System Center 2012 R2 273 lessons
so, you shall need to migrate the logins first, and after the restore you may need to "map" the user back to the login...
http://technet.microsoft.com/en-us/library/ms176060.aspx
ALTER USER ... WITH LOGIN ...