I like database design and I am currently developing one in SQL Server 2008, the one thing that I dislike He is making all the simple processes like 'person_exist' or 'get_person_data' how do you manage tasks and processes related to database data? Based on OP's comment:
Think of the set when writing your process!
Look for ways to make your processes in such a way that they will need loops to use them. If the only process in the loop has to be nulled in order to achieve the application then the performance will be greatly reduced if the application can make a call and set the entire single result data. Think, to get a process call header data and to get the details of all the children in a call (not a call loop for each child).
This is a common problem, I see that many people fall when designing "API" type stored procedures.
Comments
Post a Comment