Well, I never said parameterized views were some kind of rule and Naomi never said it, either. I try to use the right technique depending on the requirements of the job. Do I use a lot of PVs? Sure, because they are a great tool, but I wouldn't advocate them for every situation. I also create SQL statements with the WHERE clause generated on the fly and I would say that anyone that doesn't use that technique when appropriate is missing out.

>BIAS? Where'd that come from. I have a bias against people picking some idea out of a hat and making it some kind of rule. Parameterized views are such a defacto "rule". I keep an open mind a evaluate every "rule".
>
>SPT can be made to perform pooly, but at least they retain the flexibility that lets me improve their performance.
>
>Take a simple view
>
>select * from table where nID = ?lnID and Name = ?lcName
>
>The user can't use that view for much so it is extended to...
>
>select * from table where nID between ?lnLow and ?lnHigh and name = ?lcName
>
>Well now it's wasting time Rushmore optimizing on the nID when the user wants to search on the name alone. That's far worse than dragging Deleted tag info across the lan.
>
>This goes for any parameterized view with multiple parameters where the parameters are optional.
>
>That is a fundamental flaw. Building the where clause dynamically is faster because it will only involve the tags that are needed for the user's query.