> Finally, regarding migrating CFQUERY calls to stored procedures, there is so > much misinformation about this that I've already broken fifteen sticks by > shaking sticks at it. You can actually do *tremendous* damage to > performance by moving all your CFQUERY calls to stored procedures due to the > way selectivity metrics stick to query plans and how those query plans are > used to choose indexes (or not). You won't hear about this on CF-Talk or > just about anywhere else in the ColdFusion arena because people just keep > repeating the same misinformation they hear from others, so if you repeat > what I've said to just about anyone in the community they'll say I'm full of > it, but I can prove it to you by teaching you how database servers work > under the covers. It's complicated (one reason why it's not talked about), > but it will make sense once I teach it to you. >
You're not full of it - it's why I encourage most CF developers to keep SQL code when building data-access tiers and make proper use of prepared statements when possible. There are definitely times when stored procedures are 100% appropriate, but too many people think of them as a "fire and forget" without ever really looking at what they do under the hood. -Joe -- Get Glued! The Model-Glue ColdFusion Framework http://www.model-glue.com ********************************************************************** You can subscribe to and unsubscribe from lists, and you can change your subscriptions between normal and digest modes here: http://www.productivityenhancement.com/support/DiscussionListsForm.cfm **********************************************************************
