OK, I see what you mean. I guess I misunderstood what the product is probably doing. The company that has this auditing product is LUMIGENT, www.lumigent.com. The product is Entegra. I have not talked to their developers as yet, but they seem to be interested in retrieving the objects from TSM through the API.
We have just implemented TDPSQLC for logs and it works great. This wrinkle though is driving us back to using log intermediate files as you have described and backing them up. Would it be feasible for a tool like Entegra to read the data back throught the API, simulating the TDP for SQL Server? Paul D. Seay, Jr. Technical Specialist Naptheon Inc. 757-688-8180 -----Original Message----- From: Del Hoobler [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 04, 2002 10:49 AM To: [EMAIL PROTECTED] Subject: Re: TDP for SQL Server Transaction Log Restores Paul, I am not sure what you mean exactly. The SQL "logging" process does not have separate "log" segment files. The "log" that TDP for SQL backs up is just a "stream" of data that only SQL knows what to do with. It is not like a log file for Exchange or Domino. There is no way to just restore a "log" to a "file" with DP for SQL. You can only restore it to a live SQL server. The SQL server controls where that stream of data is written to. You might want to take a closer look at the requirement to find out how they are asking that this be done and in what fashion. Thanks, Del ---------------------------------------------------- Del Hoobler IBM Corporation [EMAIL PROTECTED] - Never cut what can be untied. - Commit yourself to constant improvement. ==================================================================== > We have a requirement to restore the transaction logs back to their > disk location either on the orginal or an alternate server or to be > able to post > process the transaction logs as disk files some kind of way before > they get > deleted after a TDP for SQL Server Backup. > > My DBAs tell me SQL server deletes the transaction logs immediately > after a > backup which presents a problem for a third party utility we want to > do auditing with.
