Once you've restored the database as below, I'd suggest building another
empty database that's big enough to hold the data, and then transferring the
contents from the restored database to the empty database.
The reason is that LOAD DATABASE only knows that the database being loaded
into needs to be at least x MB in size. It doesn't know how much of that x
MB was data, and how much was log, and whether the database was expanded at
any point. In other words, it doesn't know the segment mappings of your old
This is bad, because the load database statement basically just does a
page-for-page copy. If the data and log segments aren't set up in the new
database the same way they were set up in the original database, it will
likely copy data pages onto log space, and log pages onto data space. Your
loaded database will work all right, but you might end up filling up your
log with data, or your data with log, and thus getting a lot of 1105 errors,
which can be a serious annoyance.
Transferring the contents of the loaded database into a brand-new database,
using BCP or Database/Object Transfer, starts everything over from scratch.
If you're interested, a better explanation than mine is given in the Books
Online. Look at the topic "Error 2558", in the section "Different Data and
> >I have a client with no backup of MASTERdb or Help_rev_devices, all I
> >have is a couple of .dmp's of the production data. In order to run DISK
> >REINIT I need to know the size of the database, is there any way of
> >finding out the size of the database device, if all you have to go with
> >is a backup dump file?
> >I know it won't be pretty.
> Since you're talking about disk reinit, I'll assume this is a 6.5
> server. Disk reinit has nothing to do with restoring databases. It's
> used for reattaching existing DEVICES. When you perform a disk
> reinit/refit, the device will be searched for existing databases. The
> system tables sysdatabases, sysdevices, and sysusages will be modified
> to reflect any databases found on the device(s).
> If you have a dump or backup of the database(s)
> Create a small database and attempt to load it from one of the dump
> files. Load database will tell you the minimum size needed to restore
> the database.