SQL Server 2000 Database Backup File Missing Indexes when Restored? 2

[fuzzyocelot]

Hi everyone,

When we back up SQL Server 2000 databases, we use the following t-sql statement. Does anyone see anything majorly wrong with it?

BACKUP DATABASE [MyDB] TO  DISK = N's:\ MSSQL\Backup\MyDB.dat' WITH  INIT ,  NOUNLOAD ,  NAME = N' MyDB backup',  SKIP ,  STATS = 10,  DESCRIPTION = N' MyDB complete backup',  NOFORMAT

The reason I ask is because we sent a vendor a backup file for a database. He’s claiming that the .dat file doesn't restore the same way as a .bak file and that many of the constraints and indexes are missing. We've never had a problem with our .dat files. Does anyone know how some of the constraints or indexes could be missing? This does not make any sense to us.

Thanks!

 

[JayKusch]

The file exetension of the backup file does not matter. In fact I have backups with the extensions of .BAK, .TRN, .DIFF and .DIFF_FULL to let me know what kind of backup I am dealing with.

The only thing of interest would be if the indexes of your DB where in a seperate file group than your data BUT doing a full backup on the DB should cover that issue.

Thanks

J. Kusch

 

[aalmeida]

If the indexes are on another file or on another drive you must specify where to restore those on the new server assuming the file structure is not the same.

AL Almeida
CIO

http://www.artdigitalonline.com/

May all those that come behind us, find us faithful

 

[fuzzyocelot]

I didn't think the extension mattered. Also, there are no separate files or file groups other than the default ones. Thanks!