General information
Category:
Coding, syntax & commands
Title:
Too many stored procedures
Environment versions
Network:
Windows 2003 Server
This is more of an opinion question. I'm currently working on a new Sales Order Entry using VFP9. I've gotten to a point where each item I add to an order has to go through a series of validations...tax, discounts,in stock,and so on. My boss decided that each module should be written as a stored procedure. I wasnt to sure on the idea, I wasnt thrilled about coding this in T-SQL but I've gotten through it. Now I dont see much of a speed problem with them individually but when all 6 are tied together it kinda worries me. Do you think this is a good idea, or should they have been done as maybe com objects or methods.
There is a lot of data involed with each stored procedure and my boss's arguement is that its cloer to the data adn thus faster. I just didnt think 6 stored procedures in a row was such a good idea.....
Opinions appreciated!!!TIA!!!
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only