asked on

SQL 2012 Linked Server

Hi all,

I am setting up linked servers in our new 2012 environment.
I am wanting to give the Linked Server an Alias which I have done so, I have also kept the "Named Instance" Linked Server as a comparison. Have a look at my attached picture, which is the output from running

SELECT *
FROM dbo.sysservers

Open in new window

With the named instance examples... the XXXXX\DataWarehouse and XXXXX\OLTP the svrproduct is SQL Server.
With the aliased example.... OLTP, the svrproduct is SQLNCLI

All Providernames are SQLOLEDB.

So, my questions revolve around the svrproduct.

Is there a ramification to me using the aliased example?
This will shorten my 4 part naming conventions throughout my code, but I won't use it if there is a downside.

Also, why is the SSMS GUI for changing these Linked Servers so bad? The GUI doesn't populate the fields. Been like it now forever as I recall, SQL 2000, '05, '08 and now 12.

Thanks in advance.

T
SQL-Linked-Server.jpg

Ryan McCauley

Are you using a SQL Client Alias? If so, there's no impact at all to you using an alias as opposed to a "properly-named" connection. It's effectively exactly as the same as overriding DNS by using your local HOSTS file - it has no impact at all on the connection.

If you're doing your alias using another method, can you elaborate?

Tony303

ASKER

Hi Ryan,

No, I am not using any SQL Client aliasing.
I am just looking at the bottom 2 linked server items in my attached .jpg.
The "aliasing" there works too.

I can get data from OLTP and XXXXX\OLTP linked servers.

I can't see any fishhooks on the face of it if I use the OLTP.DB.dbo.TABLE 4 part naming conventions in my code.

Is there something I have missed?

Thanks
T

ASKER CERTIFIED SOLUTION

Ryan McCauley

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Tony303

ASKER

Thanks Ryan