On 4/9/07, MB Software Solutions <[EMAIL PROTECTED]> wrote: > Larry Bradley wrote: > > I just put my stored procs in the database as the tables they are messing > > with. But I only have a dozen or so. I can't think of why I might want to > > put them elsewhere. > > > > > I would agree. Putting them elsewhere adds to the burden of > management. The trick comes in to how to handle change management > (source code control) with SPs.
I use SQL scripts to load my SPs, and apply the source code control to the scripts. Since they're plain text they play nice with svn or what have you. Having everything scripted also makes it easy to shift between development and production servers. dt -- Dave Thayer Denver, CO _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
