With Ima::DBI, the SQL statements are created when they are needed, and no earlier. So it's kinda hard to get at the SQL directly except through exercising the SQL statement. The closest and convenient enough thing I use is:

DBI->trace(3)
[download]

which spews out lots and lots of things that DBI does, but also everything up to where I get the error :). Ima::DBI does sprintf-interpolation for some stuff, this can easily bite you if you're doing LIKE '%foo' statements.