>> >Well, there's more than 50 tables and they are differ between installations.

Each table is in its own file?


RESTORE FILELISTONLY will return the files and their names if you want to write something that could dynamically create the RESTORE DATABASE command.

Now, the MOVE TO option has the following syntax:

MOVE 'logical_file_name' TO 'operating_system_file_name'

Notice that you don't need to know the physical name of the file in the backup, only it's logical name, which it probably consistent across all of your installations.

-Mike



>Well, there's more than 50 tables and they are differ between installations. So when I get one .BAK, I have to create the directories and change all the physical filenames. If I could just tell SEM to simply put all files in one directory and then restore, it would be much easier.
>
>>>I'm trying to avoid the pain of telling SEM what physical file to use for each logical file ;)
>>
>>Any particular reason?
>>
>>-Mike
>>
>>>Hi Mike
>>>
>>>I'm trying to avoid the pain of telling SEM what physical file to use for each logical file ;)
>>>
>>>>When using the SEM to do the restore, on the second tab you can specify the location to write the data files. This equates to using the RESTORE's MOVE TO option.
>>>>
>>>>-Mike
>>>>
>>>>>Hi all
>>>>>
>>>>>I'm given .BAK files which are created by SQL Server during it's backup process. These BAK files are then restored using Enterprise Manager. The directories of the source machine differ from mine and I am not aware of the folder names until I create a new database and then attempt to restore it and check the options.
>>>>>
>>>>>This indicates the folder names are in the .BAK file. Is there a utility that can alter the folder names in a .BAK file? Or is there some way I can tell enterprise manager to ignore the folder names and just put all files in a specified folder?
>>>>>
>>>>>Thanks!