No we won't learn

Not more than a couple days of dealing with an obscure OSQL parsing bug (see link) that we should have known about, we QA-catch another that we already knew about.

If you fully qualify a table in another database and give it an alias, OSQL command parsing will not use the alias. That is you cannot

SELECT something FROM foobarDB.dbo.footable AS otable WHERE otable.someColumn IS NULL

The "otable.xxx" will cause an error as it cannot find that alias.
2005 et.al. seem to be fine.