New Procedurs With Version# In Name
From: <jeffchirco_at_gmail.com>
Date: Wed, 10 Mar 2010 21:07:50 -0800 (PST)
Message-ID: <9f750f7d-13ab-4ca9-90ff-916bc130358c_at_k6g2000prg.googlegroups.com>
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. Received on Wed Mar 10 2010 - 23:07:50 CST
Date: Wed, 10 Mar 2010 21:07:50 -0800 (PST)
Message-ID: <9f750f7d-13ab-4ca9-90ff-916bc130358c_at_k6g2000prg.googlegroups.com>
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. Received on Wed Mar 10 2010 - 23:07:50 CST