April 6, 2009 at 1:31 pm
Long story short : Someone in my shop backed up a sql 7.0 database and restored it to a sql 2005 server per the software vendor's request. The compatibility level is 7.0 but I can't "see" the database in the maintenance plan wizard to do backups. What's the harm or risk in changing the compatibility level to a higher version to get around this problem ?
April 6, 2009 at 1:37 pm
I would not advice you to upgrade a 7.0 database to 2005 with backup and restore so you need to use SSIS to move your 7.0 to 2005. The reason 7.0 comes without DRI and other features so if you use SSIS it can take care of most structural issues.
Kind regards,
Gift Peddie
April 6, 2009 at 1:49 pm
I would start with the Upgrade Advisor on the SQL 7.0 instance. You should be at least at SQL 7 SP4 to be able to upgrade.
April 7, 2009 at 9:53 am
I had to use Maint. scripts instead of Maint. Plans for my 7.0 upgraded databases (stayed on SQL 2005 server in 70 mode)
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply