Working with Synonym on Scalar Functions

  • Hi all,

    I Have a bit unusual environment and have some problems with Synonyms.

    I have a main productions Server (2005 ENT).

    That server uses Mirroring to copy data to a second server.

    Since the DBs in the second server are on Restoring state, I created Snapshots on those DBs for the DEV & QA dept.

    Each Dept. owns her own DB on the second server, and for the need to retreive data from the snapshot (through scalar functions), I created Synonyms to those functions.

    The only problem is when I try to run the function through the Synonym, I get an error message:

    Cannot find either column "dbo" or the user-defined function or aggregate "dbo.'SynonymName' ", or the name is ambiguous.

    I tried to use prefix (schema name before the Synonym name), tried to use DB Name and nothing!

    I can't use the function through the Synonym (I must say that Synonyms pointing to tables, work just fine).

    Is there anything I should know when creating or using Synonyms to functions?

    Please help.

    THank you,

    Oz

  • No one knows?!

    There must be a solution for creating Synonyms on functions.

    :ermm:

  • Never mind... I found the problem and the solution.

    Thanks anyway,

    Oz

  • whats your solution?Can you post.I have similar such problem.Will check whether your solution can be used.

  • I had the same problem, but have not found a solution yet

    The cause

    http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=370335

    If someone has found a workaround I'd appreciate them posting it.

    I'm currently using OPENQUERY(LinkedServerName,'Select [DatabaseName].[SchemaName].[UDFName](ParameterValue)') as a workaround, but would prefer to access to the linked servers to be in Synonyms for consistency.

  • anyone found this solution? I am stuck with this issue and really need some fix soon.

    Thanks!

  • can u post the solution its very urgent!!!!

Viewing 7 posts - 1 through 6 (of 6 total)

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