Re: New Procedurs With Version# In Name
Date: Thu, 11 Mar 2010 08:44:33 -0800 (PST)
Message-ID: <17d9d927-6e81-4af8-88a3-c056e48ae944_at_b30g2000yqd.googlegroups.com>
On Mar 11, 12:07 am, "jeffchi..._at_gmail.com" <jeffchi..._at_gmail.com> wrote:
snip
> So when my developers need to make a change to a procedure, instead of
> just recompiling the procedure they want to create a new procedure
> named like sp_procedure2 and then use the new procedure in their
> application.
> They want to do this so that they don't mess up any other application
> that might be calling the same procedure. And then when they can get
> around to updating the other applications they will use the new
> procedure. I was wondering if anybody else does this and what you
> guys think. I am against it but I am getting overruled. My database
> will look confusing, source safe will be confusing, and now I have to
> maintain multiple procedures when something needs to change.
Getting overruled by who exactly?
Is there any kind of change control team in your company? Received on Thu Mar 11 2010 - 10:44:33 CST