are Synonyms possible in MS SQL SERVER 2000

Question

are Synonyms possible in MS SQL SERVER 2000

Garg Manoj

SSC Veteran

Points: 229
More actions
September 10, 2005 at 10:20 am

#89023

Hi all,
is concept of synonym like Oracle is supported in SQL Server2000.so that i can map a four part name [server].[database].[owner]. to a smaller name.
any kinda help is most welcome.

Thanks.

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

Jeff Moden SSC Guru Points: 1004642 More actions · Answer 1

Create a view? Nah... bad idea...

The 4 part naming convention is only a pain if you don't know how to use table aliases in your FROM clause or you're writing correlated sub-querys all over the place.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Garg Manoj SSC Veteran Points: 229 More actions · Answer 2

actually i am working on distributed database.

and i want to have location transaparancy at my application level.

Jeff Moden SSC Guru Points: 1004642 More actions · Answer 3

For reads, a "surrogate view" will give you that transparency. The view would just do a SELECT * from the 4 part name. (Just gotta be careful that you're not creating views of views of views... get's kinda slow). For updates of the remote data... I've had much better luck running the update on the remote server where it pulls data from the local server using another surrogate view instead of trying to push the data from the local server.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)