Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2001-03-27 : 10:23:19
|
Sql beginner writes "Hi,
The project that I'm working on now has all the business logics built into the storedproc's and we have over 500+ storedproc's. Administrating these 500+ storedproc's is already a headache for us because SQL 7.0 does not provide category feature for storedproc. It is all depended on naming convention to differentiate them.
Further more, we have more than 3 developers working on these storedproc's and we need to keep track of changes and versions. Like all other source files we use CVS to store these storedproc's. The problem is, it is very awkward to do so.
Our solution is :
break all the storedproc's into categories and place them into different .sql files like so:
products.sql -- all product related storedproc's are stored here
orders.sql -- orders related (place order, retrieve, void)
user.sql -- user profile related (register, add, remove, modify)
..... etc.
All these sql files are stored in the repository.
When a developer needs to add/modify storeproc, he has to find out where this storeproc should go and checks out the .sql file to his local drive.
He works on the development machine. After unit testing is done he has to copy the code and replace correpsonding section in the sql file.
The whole process really slows us down. Compare this with asp pages / C++ component source files, we only need to check out the file to the developer machine, edit and test it, and check in the file in when done. We are all very frustrated about having to reason where the stored proc should go (for example, a storedproc that deals with both the order & product table) and the extra steps required for locating the section in the sql file, copy & replace the code from sql server to the source file, then check it in.
So this is really two questions:
What should we do to categorize storeproc's systematically using sql 7/2000.
What's the best way to use CVS to archive these storedproc's?
I'm just wondering if anyone out there have a better / more elegant solution for this.
Thanks,
Sql beginner" |
|
|
|
|
|
|
|
Software Management System / Version Control