0

One of my clients have been receiving this error that is causing issues in their process. Basically, they are thinking the error is related to replication of stored procedures that they assume I messed up. I had to drop some stored procedures that was part of replication and in order to do that I had to remove them from replication and I did generate a new snapshot for synchronizing with the subscriber and it was from then on they saw this error popping up in one of their stored procedures which happened during the same day, but then later on Sunday it happened again for other stored procedures. Now, my question is this related to replication or there is something else to it. Client already mentioned that they did not make any changes at their end.

6
  • Nobody will know know for sure if this related to replication unless you provide more information. Is the store procedure related to replication? Is it happening on multiple stored procedure or just one? Look at sys.objects and check created/modified date. Commented Jun 12, 2017 at 18:33
  • Look at the created date on the stored procedures' properties--see if that date matches up with the time the errors occurred. Commented Jun 12, 2017 at 18:38
  • @SqlWorldWide - It is part of replication and so are the other stored procedures. It is also happening on other stored procedures as well. I will look into sys.objects and check the details.
    – Feivel
    Commented Jun 12, 2017 at 18:54
  • @SqlWorldWide - Looked at the date and I see the modified date changed but it was due to the fact that they had to recompile the stored procedure but it does not give me any details on why would it throw an error in the first place.
    – Feivel
    Commented Jun 12, 2017 at 19:59
  • 1
    @SqlWorldWide - Yes you are right. I verified with the team and they said that they actually altered the stored procedure in order to fix the issue. Are there any other pointers as to what would have caused it to throw such an error on the publisher side.
    – Feivel
    Commented Jun 12, 2017 at 20:26

1 Answer 1

1

Modifying my answer based on the comment by @sepupic. Thank you for pointing out my mistake.

This error is generated if stored procedure definition changes while it is running.

1
  • Modifying "any object referenced in the stored procedure" is not the same as modifying stored procedure definition. The error above is caused by modifying the text of sp, not by "changing o dropping the index" which yes can invalidate the plan and cause statement recompile, but NOT cause the error above. The error tells about the object that was COMPILED and changed, so it says about module, not about table, index, ecc, referenced by module
    – sepupic
    Commented Jun 13, 2017 at 8:59

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.