Well you've got a number of options. You could just make the first query a View in SQL Server and then have your 2nd query reference the view. Or if you are using it in code (I'm not sure how you are using this: Visual Basic, SQL itself, ?) you can just have the queries within recordsets (client-side cursor preferred) and then destroy the objects when you are done. I've always liked the idea of temp tables but I've never come across an occaion when I actually had to use them. I guess it really depends on what you are going to do with them, how often you are going to do it, and where/what enviorment you are doing it in.