When restoring a backup made in SQL Server 2005 to a SQL Server 2008 environment, you don’t see the underlying upgrade of the on-disk physical version in the UI (you only see the percentage completion moving from 0% to 100%).
When performing the same on the command-line you can actually follow the physical version gets updated:
C:\SCRIPT>"%sqlcmd%" -S . -E -Q "RESTORE DATABASE [MyDBA] FROM DISK = N'C:\BACKUP\MyDB.bak' WITH REPLACE, STATS = 10, MOVE N'MyDB' to N'C:\DATA\MyDB.mdf', MOVE N'MyDB_log' to N'C:\DATA\MyDB_log.ldf' ;" 19 percent processed. 29 percent processed. 39 percent processed. 49 percent processed. 59 percent processed. 69 percent processed. 78 percent processed. 88 percent processed. 98 percent processed. 100 percent processed. Processed 1296 pages for database 'MyDBA', file 'MyDB' on file 1. Processed 2 pages for database 'MyDBA', file 'MyDB_log' on file 1. Converting database 'MyDBA' from version 611 to the current version 655. Database 'MyDBA' running the upgrade step from version 611 to version 621. Database 'MyDBA' running the upgrade step from version 621 to version 622. Database 'MyDBA' running the upgrade step from version 622 to version 625. Database 'MyDBA' running the upgrade step from version 625 to version 626. Database 'MyDBA' running the upgrade step from version 626 to version 627. Database 'MyDBA' running the upgrade step from version 627 to version 628. Database 'MyDBA' running the upgrade step from version 628 to version 629. Database 'MyDBA' running the upgrade step from version 629 to version 630. Database 'MyDBA' running the upgrade step from version 630 to version 631. Database 'MyDBA' running the upgrade step from version 631 to version 632. Database 'MyDBA' running the upgrade step from version 632 to version 633. Database 'MyDBA' running the upgrade step from version 633 to version 634. Database 'MyDBA' running the upgrade step from version 634 to version 635. Database 'MyDBA' running the upgrade step from version 635 to version 636. Database 'MyDBA' running the upgrade step from version 636 to version 637. Database 'MyDBA' running the upgrade step from version 637 to version 638. Database 'MyDBA' running the upgrade step from version 638 to version 639. Database 'MyDBA' running the upgrade step from version 639 to version 640. Database 'MyDBA' running the upgrade step from version 640 to version 641. Database 'MyDBA' running the upgrade step from version 641 to version 642. Database 'MyDBA' running the upgrade step from version 642 to version 643. Database 'MyDBA' running the upgrade step from version 643 to version 644. Database 'MyDBA' running the upgrade step from version 644 to version 645. Database 'MyDBA' running the upgrade step from version 645 to version 646. Database 'MyDBA' running the upgrade step from version 646 to version 647. Database 'MyDBA' running the upgrade step from version 647 to version 648. Database 'MyDBA' running the upgrade step from version 648 to version 649. Database 'MyDBA' running the upgrade step from version 649 to version 650. Database 'MyDBA' running the upgrade step from version 650 to version 651. Database 'MyDBA' running the upgrade step from version 651 to version 652. Database 'MyDBA' running the upgrade step from version 652 to version 653. Database 'MyDBA' running the upgrade step from version 653 to version 654. Database 'MyDBA' running the upgrade step from version 654 to version 655. RESTORE DATABASE successfully processed 1298 pages in 0.738 seconds (13.736 MB/sec).
Ain’t command-lines cool :-)
A few notes on version numbers:
655 – 2008
661 – 2008 R2
http://www.sqlskills.com/BLOGS/PAUL/post/Search-Engine-QA-13-Difference-between-database-version-and-database-compatibility-level.aspx
http://www.sqlskills.com/BLOGS/PAUL/post/SQL-Server-2008-R2-bumps-the-database-version.aspx
http://serverfault.com/questions/58039/sql-server-2008-2008r2-backup-compatibility
http://social.msdn.microsoft.com/Forums/en/sqldatabaseengine/thread/f8f8db38-3c20-45e4-ae8b-4cc097eb7f0d
–jeroen
The Wiert Corner - irregular stream of stuff 