Now there's a concept, test before change :). This vendor is obviously
more reactive than proactive.
In this situation they usually determine they have hosed the db, then
need the active backup for their tests and later for recovery. I have
suggested that we question their practices but at least up until now has
fallen on deaf ears.
Thanks Shawn.

~Rick


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Shawn Drew
Sent: Wednesday, March 30, 2011 10:42 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Portable restore from TDP for Databases (SQL) ?

>From what I understand, you want to send a copy of your DB over to a
vendor before performing a modification.
Instead of using TSM, why not use the internal DB processes for doing
this?  (BAK files for MS SQL)
Continue using TDP for your internal backups but use the disk-based BAK
files for these one-off requests.

Regards,
Shawn
________________________________________________
Shawn Drew





Internet
RickAdamson AT WINN-DIXIE DOT COM

Sent by: ADSM-L AT VM.MARIST DOT EDU
03/30/2011 08:41 AM
Please respond to
ADSM-L AT VM.MARIST DOT EDU


To
ADSM-L
cc

Subject
[ADSM-L] Portable restore from TDP for Databases (SQL) ?






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



This message and any attachments (the "message") is intended solely for
the addressees and is confidential. If you receive this message in
error,
please delete it and immediately notify the sender. Any use not in
accord
with its purpose, any dissemination or disclosure, either whole or
partial,
is prohibited except formal approval. The internet can not guarantee the
integrity of this message. BNP PARIBAS (and its subsidiaries) shall
(will)
not therefore be liable for the message if modified. Please note that
certain
functions and services for BNP Paribas may be performed by BNP Paribas
RCC, Inc.