If you are using the command line and task scheduler you can just pipe to a log file. If you want to use T-SQL and agent jobs it is a little more involved. I just helped a customer on this problem and discovered there is very little help out there with manipulating the DD-Doost from T-SQL. I decided to do a Blog post on it. Hopefully it will help you.
Thanks for the info. The problem is that the output from DDBoost is very ugly, and it comes out via stderr not stdout. I am able to redirect the output, but why can't there be a command line parameter, oh, I don't know, something like '/log=mydatabase.log' ? Is that too difficult for the EMC programmers to code? And why the heck did they direct all of the output via stderr?
dmuegge
17 Posts
1262
0
Posted August 9th, 2014 08:00
droach,
If you are using the command line and task scheduler you can just pipe to a log file. If you want to use T-SQL and agent jobs it is a little more involved. I just helped a customer on this problem and discovered there is very little help out there with manipulating the DD-Doost from T-SQL. I decided to do a Blog post on it. Hopefully it will help you.
David Muegge’s Blog » Archive » Data Domain Boost for SQL – Deployment Planning Considerations for DBA’s
Regads,
Dave