• Yeah, that a was kind of badly worded statement. Apologies.

    What I meant was, treat every query as a separate entity rather than try to use what looks like, from a coding standpoint, a valid object for code reuse such as a view.

    Hopefully that makes more sense.

    If you can, post the query and an execution plan (save the xml as a .sqlplan file). One of us is sure to jump on it and see if there are tuning opportunities.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning