Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • Thanks Keneth. It turned out that after closing SQL Management Studio and opening it again it worked. It seems like it kept a cached copy of the SP in memory. Commented Aug 8, 2013 at 16:45
  • @FedericoGiust I would recommend you to wrap in transaction as if something goes wrong, then you can rollback. This is more dangerous to do. Or you can just have print statements and then check them and then execute them once confirmed. Commented Aug 8, 2013 at 16:49