Multiple SP Versions

Hi,
I have a database, the interface to which is completely implemented as a set
of stored procedures. I want the application which uses the database to use
side-by-side versioning, i.e. there may be more than one version of the
application current and needing to access the database.
As you can imagine, over time and versions the interface to the database may
change, so I will need to have a set of stored procedures for each version
of the application that is current. What I am thinking about is, for each
version, to have a "shell" database on the same server which only has the
stored procedures which acess the tables on the "real" database... hence
keeping separate the interface for each version of the application.
Does anyone have any comments on the performance of this arrangement? Or a
better way to go about it?
Regards
Greg BacchusHi
Stored procedures can contain a verson number see "; number" in http://msdn.micros
oft.com/l...e=tr
ue. I would not call the stored procedure through the application but not by
using dynamic
SQL everywhere.
You may well have serious maintenance issue with running more than a few ver
sions of a stored procedure, therefore you may want to think about a more fo
rmal upgrade process.
John