Hi,
	I think it depends on what you are willing to trade. More indexes can  
mean using up more disk space, and potentially longer calculation  
time, but more efficient access on the client side (e.g. I'd get the  
two fields I wanted instead of 20). So it depends on your application:  
do you pay through the nose for storage, do you expect a lot of  
updates (and hence a lot of view indexing) or are things fairly  
static, do you have 1 client process of millions....
	I tend to try and have a view that indexes one piece of information  
and then reuse that as much as possible with grouping, reduce=false,  
include_docs etc. I'll only add a view when I know that one of my  
existing ones can't be bent to my will. Not sure if that's the best  
way to go so YMMV...
Cheers
Simon

On 7 May 2010, at 17:03, Chris Hicks wrote:

>
> If I have a DB of lets say 100K+ documents, with each document  
> having 20 fields, would it be more efficient to have a view that has  
> indexed each document and simply run more complex queries over them  
> or would it be better to have a number of smaller views, each  
> covering only a few fields, and running much simpler queries on each  
> of these views for whatever data might be needed at that moment. As  
> with most things the answer is probably "it depends." If there is no  
> easy answer could anyone tell me what the pros and cons are to each  
> of these approaches?
> Chris Hicks 		 	   		
> _________________________________________________________________
> Hotmail has tools for the New Busy. Search, chat and e-mail from  
> your inbox.
> http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_1