synonym

Is it valid to do something such as CREATE SYNONYM [dbo].[MyTable] FOR [AnotherDatabase].dbo.[MyTable] and then modify Entity Framework's edmx file to read this object like it would any other table? I did a quick sample test and it seems to work fine for selecting and updating, but I wanted to know if there was any reason why I shouldn't be doing this I am getting the table definition by creating an edmx file pointing to the 2nd database, building out the entities there, then copy/pasting the definition into the 1st database's edmx file. UPDATE If anyone is interested, I wrote up what I did to

I'm familiar with the issue behind ORA-01775: looping chain of synonyms, but is there any trick to debugging it, or do I just have to "create or replace" my way out of it? Is there a way to query the schema or whatever to find out what the current definition of a public synonym is? Even more awesome would be a graphical tool, but at this point, anything would be helpful. As it turns out, the problem wasn't actually a looping chain of synonyms, but the fact that the synonym was pointing to a view that did not exist. Oracle apparently errors out as a looping chain in this condition. If you are