Error while taking BackUp of a database in SQL Express 2005

I installed MSDE2000 initially, and later upgraded to SQL Express 2005.

Then I created a database"CGQA00032" in SQL Express 2005.

On taking the BackUp of the database using T-SQL command:

BACKUP DATABASE CGQA00032 to disk = 'CGQA00032.bak'

I got the following Message when I run this query in Managemant Studio :

<<<<<<<<<<<<<<<<<<<<<<<<<<<

Processed 672 pages for database 'iwdm_CGQA00032_V4', file 'iWDM_CGQA00032_V4_Data' on file 4.
Processed 1 pages for database 'iwdm_CGQA00032_V4', file 'iWDM_CGQA00032_V4_Log' on file 4.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'mirror_count'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_password_protected'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'mirror'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_password_protected'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'recovery_model'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'has_bulk_logged_data'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_snapshot'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_readonly'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_single_user'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'has_backup_checksums'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_damaged'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'begins_log_chain'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'has_incomplete_metadata'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_force_offline'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_copy_only'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'first_recovery_fork_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'last_recovery_fork_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'fork_point_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'database_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'family_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'differential_base_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'differential_base_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'state'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'state_desc'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'create_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'drop_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'file_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'read_only_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'read_write_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'differential_base_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'differential_base_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'backup_size'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'filegroup_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_readonly'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_present'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'state'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'state_desc'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'create_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'drop_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'file_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'read_only_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'read_write_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'differential_base_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'differential_base_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'backup_size'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'filegroup_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_readonly'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_present'.
Msg 3009, Level 16, State 1, Line 1

Could not insert a backup or restore history/detail record in the msdb database. This may indicate a problem with the msdb database. The backup/restore operation was still successful.

BACKUP DATABASE successfully processed 673 pages in 2.141 seconds (2.575 MB/sec).
2

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

1. What is the problem with msdb database?

2. Is it a problem of upgrading through a previous version of SQL Server?

3. Is there any Service Pack available to overcome such problem?

Please help ASAP.

Best Regards,

Vishal Gawai

Moving to Engine forum|||

It seems that when you upgrade MSDE to SQL Server Express 2005 RTM the msdb database is not upgraded.

See: http://support.microsoft.com/kb/914781/en-us

The columns you are seeing complained about are columns added to the backup* tables in msdb in SQL Server 2005.

Apparently this was addressed in SP1 so you need to apply either SQL Server Express SP1 or SQL Server Express SP2 to your SQL Server Express installation.

|||

Thank you for ur help.

I would like to know one more thing:

When I tried the above problem on French version of SQL Server 2005 Express Ed.

I recieved SQL server native error 4035 . (Message :: Processed 672 pages for database........)

Is this because of the above reason as explained?

Becasue this error does not occur on English version of SQL Server 2005 Express.

Regards,

Vishal

|||

vishalg wrote:

I recieved SQL server native error 4035 . (Message :: Processed 672 pages for database........)

This is a confusion where the word error is used for any messages. If you look at the severity of the message you will see that it is 10. This means that it is an informational message and not an error at all.

As for why you don't see the error in the French version.

Checking at the download site. The English edition of SQL Server 2005 Express Edition was released 7 November 2005. The French edition was released 25 January 2006. They probably included available critical fixes in the release (ahead of SP1) and this problem was probably both picked up quite quickly after release, and relatively easy to address (as the update code for msdb was available just not enabled/included).