Hi *SM-ers!
Our SQL Server department is currently migrating to SQL Server 2000 and thus
they are going to use DP for SQL Server 5.2.1 instead of TDP for SQL Server
1.1.2.
With 1.1.2 they were able to control retention through the ADSMAUTODELETE
command, but since 5.2.1 uses TSM policy retention management that's no
longer possible.
The problem (or challenge?) is that they have several databases on one node
with all their own retention requirements, varying from 9 days to 168 days.
Just storing all data for 168 days would be the easiest solution, but one of
the short retention databases is 20 Gb. so the impact on the TSM storage
would be significant.
Does anybody have a simple solution to use the 5.2.1 client in such an
environment?
Thanks in advance for any reply!
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines


**********************************************************************
For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), 
its subsidiaries and/or its employees shall not be liable for the incorrect or 
incomplete transmission of this e-mail or any attachments, nor responsible for 
any delay in receipt.
**********************************************************************