November 1, 2013 at 12:54 pm
Hi everyone,
We are required to move off of some old hardware due to warranty expiration. It is turning out to be a long and unfun process because when the databases were built, the application connect strings were pointed to specific FCI names. I don't want to go through this level of application coordination again so I'm thinking of a better way to set them up this time.
Whenever possible, when we can migrate the databases to SQL Server 2012, I'll make a listener but this doesn't always work because not all databases need a secondary replica.
There are some databases where the vendor does not support 2012 so we have to stick with 2008 R2. Is it better to create CNAMES for each of these applications that point to an A record for the SQL Server or is it better to make multiple A records to the SQL Server IP? CNAMES seem easier but I am not sure how Windows authentication would react to being redirected that way.
Does anyone have experience setting this up?
Thanks much,
Howard
November 4, 2013 at 12:50 pm
Is there by change another more appropriate forum where I can post and where people can share their experiences?
November 4, 2013 at 2:44 pm
Sounds like you have a couple of questions bundled in there. But to your main point yes, you should be able to use a DNS alias to point to a different machine.
Here's an old thread that may answer some of your questions.
http://www.sqlservercentral.com/Forums/Topic748728-146-1.aspx
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply