Some work associates and I have been discussing the differences, pros, and cons of using synonyms as opposed to what we refer to as transparency views. For example if you have 2 databases, Accounting and HumanResources, you many want to reference data in one from the other and vice-versa. Typically, we have done this similar to the following:
--In Accounting
CREATE VIEW Employees as SELECT * FROM HumanResources.Employees
--In HumanResources
CREATE VIEW Expenses as SELECT * FROM Accounting.Expenses
This effectively accomplishes the same thing as a synonym with just slightly different syntax. However, my understanding is that synonyms are less subject to binding errors if the underlying table changes. Is this accurate? Any other reasons to use one vs. the other? Any performance implications?
[Noelle Mallory - MSFT] Please post questions to the MSDN Forums at
http://forums.microsoft.com/msdn. You will likely get a quicker response through the forum than through the Community Content.