It’s old news by now that SQL Server 2008 R2 is NOT even closely related to SQL Server 2008. It’s a complete version upgrade. More annoying, though, is that because it is a complete upgrade, the backups (and MDF/LDF files that you attempt to detach/attach) are not compatible. If you are just taking a casual glance, it seems that SQL Server is not compatible with itself.
If it’s upgrade enough to break the backward compatibility, then it ought to have a version number and name that reflects that fact. Or at least make it clear:
“Microsoft SQL Server 2008 R2
(“R2” NOT COMPATIBLE WITH “”)
But what really winds me up is the message you get when you attempt it:
The database was backed up on a server running version 10.50.1600. That version is incompatible with this server, which is running version 10.00.2531. Either restore the database on a server that supports the backup, or use a backup that is compatible with this server.
Like, maybe they could preface that whole thing with the words “Hey, moron: ”
It’s not really a nice idea to ridicule the customer. Especially when you’ve given them a false sense of security by naming the two completely different products so close in name that you’d have to excercise more than due dilligence to catch it. I don’t expect version 2008-dot-anything to be completely incompatible with 2008-dot-anything-else.
And I must say that a whole 0.5 version upgrade is hardly excuse enough to break ties with the previous version.