The only SQL tip that I can think of is, "Try to create a cut down version of the bug." Just start finding chunks of SQL that can be removed, and remove them until you find out exactly what is necessary to reproduce the bug.

This will lead to a much clearer bug report, and also a clear idea of what you need to do to work around the problem in the meantime.