Yes it's been a while, but I've gotten pulled into database design, and this group has always been the best place to turn to for technical knowledge.
The team here inherited a crap database, over 200+ tables for an unexciting claim system, and is now adding new features. Yes, views are better than straight SQL in the code in the case of many tables for your query. Maybe I've just been out of the game, but the team is using stored procedures to build queries to output data on a page, which seems odd to me. Maybe it is fear of the outer join, unions, subqueries. But do I have a case for pushing the funky view SQL versus running stored procedures? The case here is nothing exceptional, we are getting data for the list of all documents related to a claim and then the one record for form fields for a single document for a claim. Thanks! Mary-Catherine
