Rick,

One thing to understand about SQL Server legacy (VDI) backups:
The backups are a "stream of bytes". Data Protection for SQL
does not read and write files. The SQL Server gives
Data Protection for SQL a stream of bytes at backup time,
and Data Protection for SQL gives the SQL Server those
stream of bytes at restore time.

Now.. having said that, you can solve your problem by
redirecting the restore of the backup into
a "temporary" database name and relocate the files.
After the restore is complete, you will have the
temporary database with all the database files
(.MDF, .LDF, .etc.) under your temporary directory.
Use the "Restore Into" and "Relocate" abilities of
Data Protection for SQL to accomplish this.
This technote might help:
   http://www-01.ibm.com/support/docview.wss?uid=swg21253263

Thanks,

Del

----------------------------------------------------

"ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu> wrote on 03/30/2011
08:41:24 AM:

>> From: Rick Adamson <RickAdamson AT WINN-DIXIE DOT COM>
>> To: ADSM-L AT vm.marist DOT edu
>> Date: 03/30/2011 08:43 AM
>> Subject: Portable restore from TDP for Databases (SQL) ?
>> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
>>
>> We have a remote vendor who sends updates to a SQL db that lives on one
>> of our SQL servers. From time-to-time the updates are determined
>> undesirable and before performing a restore in production  we want to
be
>> able to send them a portable copy so they can determine the root cause
>> of the problem before moving forward. I have had this situation come up
>> before and scoured over the TDP documentation and found no clear
>> definition of how to complete the task.
>>
>>
>>
>> Is there a way to perform what I will call a portable "flat file"
>> restore of SQL databases from TSM without it affecting the production
>> copy that is live on the SQL server?
>>
>> How do you handle these requests?
>>
>>
>>
>> All feedback appreciated....TIA
>>
>>
>>
>> Rick Adamson
>>
>> Jacksonville, FL