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.

Required fields*

5
  • 12
    If you don't know what stored procedures to update when you change your database, that's not a problem with stored procedures, it's a problem with whoever's in charge of the DB Commented Nov 19, 2009 at 8:00
  • I was thinking the same thing, but didn't have the heart to tell him. Commented Nov 19, 2009 at 8:02
  • 1
    'View Dependencies' works pretty well for me, as does interrogating the system tables. Much easier than trawling for application code for an UPDATE statement that's composed on the fly. Commented Nov 19, 2009 at 8:19
  • @Sem, it does have that. As Code said, view dependancies. I work on an application with somewhere in the range of 1000 stored procs, and I don't have any problems figuring out what I need to change during schema evolution. Commented Nov 19, 2009 at 8:32
  • Why can't you search your source control system for dependencies? I know the dependencies tables aren't always complete. Commented Apr 18, 2010 at 20:48