>>However, I have a few with "SELECT *" and 50-75 fields involved, and only 1 or 2 critical GROUP BYs in the SQL.
>>
>>Anyone have a good recommendation for me to handle these?
>
>
>Split the SQL in parts.
>
>Get all the ids and "group by" fields grouped in the first SQL and run a second sql to get the rest.

Thanks, I think I see your idea. Let me go try it on on of these big SQLs.