SQL Server Performance

Error in Transaction Replication

Discussion in 'SQL Server 2005 Replication' started by tfakih, Mar 6, 2007.

  1. tfakih New Member

    Dear Friend,
    I m using SQL Server 2005 Standard Edition SP1.

    I am doing Transaction Replication between my production Server & standby server. Standby Server is in same Domain. When I ran the snapshot agent first time I got the following error.
    "An insufficient number of arguments were supplied for the procedure or function db0.fnBRK_AccountSecurities".

    It is showing that there is an error in function db0.fnBRK_AccountSecurities
    but it is working on my production server nice....
    What to do to remove the error?
    Please guide me.
    Thanks
    Regards,
    TFakih

  2. satya Moderator

    Avoid this error from happening, always make sure that you pass the same number of arguments that a stored procedure or function is expecting.

    Satya SKJ
    Microsoft SQL Server MVP
    Writer, Contributing Editor & Moderator
    http://www.SQL-Server-Performance.Com
    This posting is provided AS IS with no rights for the sake of knowledge sharing. The greatest discovery of my generation is that a human being can alter his life by altering his attitudes of mind.
  3. tfakih New Member

    Dear Mr.Satya,
    This UDF is working allright in my Production Server...there is no error.Then why it is giving error in replication...? Or I m missing some steps?
    Pls.guide me.
    Thanks,
  4. MohammedU New Member

    Why the snapshot agent executing the FUNCTION?
    Snapshot copies/creates all the objects and copies the data to the destination but will not execute the functions/procedure...or am I missing something??

    Run the sql profiler to see what is the problem at the standby server...

    MohammedU.
    Moderator
    SQL-Server-Performance.com
  5. tfakih New Member

    Thanks Mr.Mohammed,
    U got my point.Let me try to find out....
    TFakih
  6. kiza17 New Member

    Try removing the comments from the code. (especially /* ... */).
    I think that SQL on the subscriber is trying to recompile the function.

    It happended to me before. An removing the comments seemed to work.

    Cheers,

    Zoran

Share This Page