Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

How To Setup Server Side Only Alias (No Client Config Needed) For Named Instance Only SQL Installs Expand / Collapse
Author
Message
Posted Monday, August 27, 2012 12:18 PM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Tuesday, November 18, 2014 12:05 PM
Points: 892, Visits: 1,559
How (if possible) can I setup a Server Side alias for a named instance on a server that has SQL 2005 and SQL 2008 R2 installed and install of SQL Server uses a named instance (No Default instance) and do it so that no client side alias setup/configuration is necessary?

BACKGROUND: For a number of years we’ve been running SQL 2005 with the DB it hosts (that is used by our primary application) set to a compatibility level of SQL 2000. We now have to upgrade the DB to work with SQL server 2008 R2. The problem is that we must move the DB to the new DB server before we are ready to upgrade to SQL 29008 R2. We will need to run the DB under SQL Server 2005 in the new DB Server for 1 – 2 months. We have but 1 DB server to do this move.

To meet all the needs listed above I installed SQL 2005 and SQL 2008 R2 both on the new DB Server installing each as a named instance with no DEFAULT instance. As of current the server DBSERVER09 has a SQL 2005 instance named SS205 and a SQL 2008 R2 instance named SS2008R2.

DBSERV09\SS2005
DBSERV09\SS21008R2

THE ALIAS: In order to simplify all of this for the user so that they need only remember a single server name I was going to setup a server alias that would point to the SQL2005 instance for now and then after we upgraded the DB to SQL 2008 R2 I would update the Server alias to point to SS2008R2. A server only alias is an alias that requires setup/configuration on the server only. This way any client on the domain a valid username & password can connect to the server thru the alias without having to do any setup/configuration on the client system.

So Far I can’t get this to work and I am testing the connection via the alias name from both the DB Server itself (I am connected into it via Remote Desktop) and a client system and neith works when specirfying the server alis name but both work when using the proper instance name.

Is this doable and if so how?

Thanks


Kindest Regards,

Just say No to Facebook!
Post #1350519
Posted Monday, August 27, 2012 12:33 PM


SSCrazy Eights

SSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy Eights

Group: General Forum Members
Last Login: 2 days ago @ 11:54 AM
Points: 9,294, Visits: 9,492
What facility is the "Server only Alias"? Can you point me to the doc for it?

The only way that I've heard of anything like this was through the SPN's, is that what you mean?

Thanks,


-- RBarryYoung, (302)375-0451 blog: MovingSQL.com, Twitter: @RBarryYoung
Proactive Performance Solutions, Inc.
"Performance is our middle name."
Post #1350528
Posted Monday, August 27, 2012 12:38 PM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Tuesday, November 18, 2014 12:05 PM
Points: 892, Visits: 1,559
RBarryYoung (8/27/2012)
What facility is the "Server only Alias"? Can you point me to the doc for it?

The only way that I've heard of anything like this was through the SPN's, is that what you mean?

Thanks,


BY server olny alias I mean configuring an alias at the server and not at the client so that if you have 1 server and 100 clients you need configure the alias just once, at the server and then all 100 clients can use that server alias. I'm asking if that kind of thing is possible? Or do you have to configure a server alias on every client that will need to use it?

ANother way:

SQL Server\Instance: WDSERV09\SS2005

If I want to configure it so that all 100 clients can connect to WDSERV09\SS2005 using the server alias dbserver do I need to configure the alis at all 100 clients (a client being a workstation on the domain) or can I do it at just the SQL Server?


Thanks


Kindest Regards,

Just say No to Facebook!
Post #1350531
Posted Monday, August 27, 2012 3:08 PM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Today @ 9:30 AM
Points: 4,613, Visits: 11,016
I guess something like a DNS name + reverse proxy can do that.
I'm not sure you can forward to different ports based on the "alias" name, but it's worth giving a try.


--
Gianluca Sartori

How to post T-SQL questions
spaghettidba.com
@spaghettidba
Post #1350613
Posted Wednesday, September 5, 2012 10:08 AM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Tuesday, November 18, 2014 12:05 PM
Points: 892, Visits: 1,559
Thanks to everyone who took tike to reply. AT this point thsi looks like a no-go in as far as doing it without imnpelemnting some kind fo work-around that may not work for all clients/scenarios.


Luckily the bulk (about %90 or more) of the users connecting to the BD do so thru an IE managed web based application which stores the Server anem & DB requiring that the user need only provide tehir login info so we don;t have to worry about tehir getting the right server name + alias. Only our outside users who come in outside this web based app will need to specify the server name. For those we can get a client side alias setup for them to use if need be,

Thanks again


Kindest Regards,

Just say No to Facebook!
Post #1354721
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse