• Gail may have already spotted the problem. If you're just running the SELECT and there's no filter on the data, it's doing a scan of all data across all the tables involved in the query. It's just going to take how long it takes. You might be able to speed up aspects of it such as the joins, with indexing, but overall... you might be in trouble.

    "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