ansaurus

Question

Answer 1

+1 A:

The View editor in Management studio (and enterprise manager before it) is, shall we say, rather limited, and prone to exploding the number of references to a table/view if there are complex conditions.

It's much to be preferred that you learn to write CREATE/ALTER VIEW statements in query windows (there are options to script VIEWs to a new query window as ALTER, if you're wanting to update an existing view).

Alternatively, you can add the linked server using, say, the "Microsoft OLE DB Provider for SQL Server", "SQL Native Server", or any of a number of other providers, rather than using the "SQL Server" provider, and then you can specify a different name for the linked server. (We do this in my shop so that our test servers refer to their partners using the same names as are used on our production servers)

E.g.:

EXEC master.dbo.sp_addlinkedserver @server = N'ALIAS', @srvproduct=N'ACTUALSERVER', @provider=N'SQLOLEDB', @datasrc=N'ACTUALSERVER'

Damien_The_Unbeliever 2010-10-28 12:21:58

In a programming situation where precise-ness is such a key part of what we do, I do love when the answer is "Yeah, just lie to the computer about what you're doing and it'll stop bugging you about it." No sarcasm intended, here, I just love the irony of it.

Frosty840 2010-10-28 15:31:18

@Frosty840 - and yet you're happy to rely on the imprecision of the view designer (which is causing your main problem), rather than writing SQL directly :-|

Damien_The_Unbeliever 2010-10-28 19:13:04

Oh, I'm not happy about any of it. The difference is, I'm writing the linked server bit. Some other eedjit used the View Designer.

Frosty840 2010-10-29 07:32:15

ansaurus

tags:

views:

answers:

Aliasing a linked server?

related questions