Does the user really need to know what is happening under hood? If everything works, probably not. Personally I like to know what is going on but you don’t get that for other actions either. If someone really wants to check the DB changes themselves, there are other tools for this.
We are not talking about average users (like visitors or editors) here. We are talking about admins with at least some developers skills. Those people like to have detailed output, such that they have a starting point to investigate errors. It is not only about the problematic installation, as you will likely never see the verbose output, but rather to be table to compare it to a clean state.
Without the verbose output of queries, one need to dig into the code, piece together the puzzle and then start trying to understand where things go wrong, whereas one could have simply run the query from a clean installation on the failing DB and have a look.
What other tools for DB changes are you talking about? The only thing that comes to my mind here is a query log, that is likely going to slow down the whole DB.
I would prefer that the checkbox becomes a general verbose output option, depending on the upgrade wizard. Queries should be printed without values. The values should be shown separately. At least that is what I do when I am debugging queries.
I personally really hate it if tools do not provide a verbose output option, start failing and you are none the wiser why. Most notable Microsoft products that output the very distinctive error message “There was an error”, even on a shell admin utility. No way to trace the error. No way to find out what a successful run does and what might have possibly gone wrong.