Skip to main content
Database Administrators

Return to Question

edited body
Source Link
Lumpy
Lumpy
  • 2.1k
  • 9
  • 33
  • 43

When using RESTORE FILELISTONLY to restore a database using code the logical_name for the files is coming back as 349423.

However when I do a manual restore of the database the logical file name appears to be 3497.

I'm running SQL Server 2008 R2. Has anyone run into anything like this before? How do I repair this?

When using RESTORE FILELISTONLY to restore a database using code the logical_name for the files is coming back as 349.

However when I do a manual restore of the database the logical file name appears to be 3497.

I'm running SQL Server 2008 R2. Has anyone run into anything like this before? How do I repair this?

When using RESTORE FILELISTONLY to restore a database using code the logical_name for the files is coming back as 423.

However when I do a manual restore of the database the logical file name appears to be 3497.

I'm running SQL Server 2008 R2. Has anyone run into anything like this before? How do I repair this?

Source Link
Lumpy
Lumpy
  • 2.1k
  • 9
  • 33
  • 43

SQL Server FILELISTONLY command providing incorrect logical database name

When using RESTORE FILELISTONLY to restore a database using code the logical_name for the files is coming back as 349.

However when I do a manual restore of the database the logical file name appears to be 3497.

I'm running SQL Server 2008 R2. Has anyone run into anything like this before? How do I repair this?