Don't know if it still works in 2005 but you'll get the idea :

EXEC sp_MsForEachDB 'EXEC ?.dbo.sp_MyWork'

Or just use straight dynamic sql and you'll be fine.

I got to save this answer... it will come in handy someday.

Thanx GF .

Still have or still don't have?

Care to formulate a more complete idea?!?!?

Obviously... but my point was that validation is not an option and should always be performed before the error occurs not after the user comes in and says something doesn't...

It's the exact same query except for the order by part.  In your sample results you seem to require the data to be returned by fruit name which is what...

"Abbout the only query that will definatly, without exception use the NC index is a query of the form

SELECT MyDate from MyTable Where MyDate = '2006/01/01'

because it can be...

Also you might find this read very helpfull!

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=236&messageid=215144&p=1

Or actually >>

1 - Load data into working table

2 - Find bad rows

3 - Clean / delete / move them out of the way

4 - Begin transfer and behold, works...

I C.  I never had to do this but why not keep all the queries on the application side?  You just have to make sure that the user can only...

Why would this one not use the index (besides the fact that it could return too many rows for a seek to be usefull)?

Select * From MyTable Where MyDate Between...

I could, but that could take some time .

I know there's something fishy here but again I never said the design was right.  So what I'd like to see now is what solution mr helpfull can come up...

I'm not saying that the design is right nor wrong.  But this seems to be a case where the tool used to get the data out is not the right...

Old code... didn't have time to rethink and rewrite.  But I'm sure you already have the "good" answer ready so what not just post it already