February 20, 2009 at 6:43 pm
Recently we had a situation where one of our database servers moved from machine A to machine B. This meant the SQL Server returned "machine B" to SELECT @@SERVERNAME. Of course, this required the odbc.ini on our Solaris Application server to be modified. As luck would have had it, the App admin was elusive and the production schedule was closing on.
As the network administrator was available, and since machine A could be taken off the network, I suggested we could "throw in" a DNS alias of "machine A" for "machine B" (perhaps not a good way of saying it). This suggestion drew severe criticism from the SQL DBA. I would like to know from the experts here what the ill-effects are of this approach.
Of course, I would share the DBA's arguments, but honestly I did not feel they were genuine and I would want to know what the "unbiased" experts on this forum have to say about this proposed solution.
Thanks in advance!
February 24, 2009 at 4:26 pm
I would be curious to hear what the reason was for a DNS alias being a bad idea.
I have used DNS aliases several times when migrating between SQL servers. There are servers which have been migrated years ago and certain users still access them via the DNS alias even after my repeated tries to have them use the new server name.
From a DBA standpoint I can't think of an issue but maybe from a Network Admin perspective it might get messy to have a bunch of aliases out there.
February 24, 2009 at 5:40 pm
Good that you asked ..I almost forgot ... see we did ask the administration staff the feasibility of "calling the new machine the old name" and here's what we got back -
-------------------------------------------------------------------------------------------------
AS THE DBA, renaming a fully configured SQL Server is not advisable. In addition to registry hacks which must be made we would officially have to rerun diagnostics and testing.
Additionally, SSIS variable overrides would have to be changed and tested. I’m sure XYZ will be interested in knowing about the added cost to ABC.
-------------------------------------------------------------------------------------------------
Unfortunately, this kind of a response is typical of the confrontational admin support we have .... sitting down to discuss objectively the options of a win-win is out of question ...
I am grateful to be a member of SSC as this forum opens otherwise closed doors to knowledge and options toward working an optimal solution
Thanks to you all for your help
February 24, 2009 at 5:42 pm
I meant to clarify - that response tells one of 2 things about the staff -
1. they aren't as well informed to know of the option of an alias (which I doubt 'coz I have seen them do this on other occasions)
2. they just dont want to do it
February 24, 2009 at 5:54 pm
leonp (2/24/2009)
AS THE DBA, renaming a fully configured SQL Server is not advisable.
Renaming a SQL server and putting a DNS alias out there are 2 different things.
I guess maybe if an IP address was hardcoded in some code instead of the server name that would cause and issue.
February 24, 2009 at 9:08 pm
See Edd you are "reading" - cant say the same about my staff here .... this is one of those times you feel having knowledgable people isn't always enough ....
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply