I ask of those who know.....
-
To Make a short story long, I need to inquire from those who know, the Ideas/Problems behind moving (physically the Box and DBs) an SQL server (MS2003 serve with SQL2K) from one network envoronment to another. Let me explain…
I am in the position where our Business is looking to bring in an SQL Server on MS 2003 for support of a New Application, into our current Novell Server Environment for which we have dual authentication to Novell for Print/File Share and a WAN Active Directory Domain for application connectivity. After about 3 months time our Business is cutting over all Servers , Switches, Routers, and other associated network Hardware software, including but not limited to Applications accessed through the AD domain. When the cut happens, or shortly there after, our AD domain will switch over as well to a local Domain controller with a different box and naming scheme.
So in short if anyone has done this, or can think of the problems that may arise, I would like to hear your thoughts. While I can not speak on the SQL side of the issues that might arise (SQL Administration and Programming Classes start in 2 months), I have a list of apparent Networking issues that I have come up with, and would like to hear yours as well, SQL, Networking, or both….
Thank you for your time….
-
OK, so I forgot one important Item....
I was offering the Idea to the Department for which the New (SQL needed) Application is for, that it would be easier to wait until we are up and running in our new environment, rather than bring it up on our Current outdated Network now, and have it be the only piece we bring over into the New Network envoronment. My thoughts are forward thinking on the Issues we may be hitting by rushing it, having the SQL server establish relationships with the other server and items in place now, and that when we cut over, and they can no longer be seen, the problems we could face by doing this now rather than wait 3 or 4 months.
Sorry for any head scratching on if I was actually asking a question above,,, Just under the gun so to speak..
Thanks again,
-
Permissions. The services (SQLServerAgent and MSSQLServer) all run under either the local admin or domain admin account. Will that account change with the change of the domain? Probably.
IP Address. Will the IP address of the server change? If so, that changes how the client machines (ODBC, etc) connect.
Logins. Are you using Windows Authentication ONLY? If so, the 'trust' might be broken. The domain SQL Server is on must be able to authenticate the users trying to login. This usually means a common domain controller (everyone on the same domain as SQL Server or Active Directory being used and domain controllers on each domain replicating their info to each other).
That's all I can think of....anyone else?
-SQLBill
-
Thanks SQLbill, yes this is just what I am looking for...
The permissions will change, as the Domain we connect to now will not only physically change as it will be brought onto our LAN, the Naming for our Domain will change as well as the IP address.
IP addressing will be changed for all networking pieces to a different segment address for the "New" network all together, and you are correct the Address of the Client and Servers would both change as well as routers and switches.
Logins, currently we are duel, local to Novell and WAN to our AD (Active Directory) domain. When change is complete, 3 maybe 4 months, we will only login to a Single AD domain and all of the Novell pieces of our network will be gone.
To add to the fun, it's looking as if we will be moving from (forgive me, I know we waited to long) from static IP addressing to DHCP. I am begining to wonder why the ASP would even consider bringing in their product until we were finished...
Thanks again for the info, and yes please keep it coming....
-
Correct me if I am wrong but I think what SQLBill asked about permissions was about SQL Service Account that run SQLServerAgents and MSSQLServer. If it was setup to use by local admin, it will be a lot easier to move the box because that means sql server is not much tight into other servers. If it is set to use by domain account, then you have a lot more to worry about such as DTS packages, Jobs, etc.
How many SQL Servers that you need to move? Is there any other server that has relation with the SQL Server? How does the SQL server backup?
Also when SQLBill asked about Logins, SQLBill meant SQL Server Authentication. SQL Server has an option to use both Windows account and SQL Server account or Windows account only.
Since I don't know much bout Novell, I can't give you much about that but please don't say that you folks are going to use DHCP even for SQL Server. It will be nightmare unless there are something that you know that I don't know about it.
Good luck~
-
Thanks, I will need it... Oh, and not much chance of me knowing more than anyone on SQL… Not yet at least…
Knowing what the settings are could be an issue as the box is not setup yet. It will start with (1) SQL box to begin with, (1) installed product requiring the SQL Server, and it will be the only one we move from our current network when we upgrade. The box will have mixed mode authentication, and from what I have seen, I will be working to make sure its setup to use by local admin.
I am still aquiring more information on final setup.
Please feel free to close this subject; I have a feeling that I have enough to present on the issue we are looking at, after a call with the IT side of the product support, the networking issues are going to be as much of an issue as the SQL possibilities.
Thanks again for your knowledge, Great Site!
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply