You'd think they'd have this sorted out by now, considering it's one of the first things anyone upgrading from SQL 2K to 2K5 on a new server would need to...