It strikes me as quite odd that the order of columns in the resultset wouldn't be the same as the order of columns in the query. But you don't seem to be using DBI, as you call ->Sql and ->FetchRow methods which are not part of the DBI API, so whatever sits in between your code and DBI might screw things up there.

If all else fails, you can use DBI's Slice => {} option to have queries return hashes with the keys being the column names and the values being the associated query results for each row.