http://itknowledgeexchange.techtarget.com/itanswers/dfu-to-sql-translator/ Sun, 19 May 2013 03:14:28 +0000 hourly 1 http://itknowledgeexchange.techtarget.com/itanswers/dfu-to-sql-translator/#comment-113851 TomLiotta Fri, 30 Nov 2012 06:38:55 +0000 http://itknowledgeexchange.techtarget.com/itanswers/dfu-to-sql-translator/#comment-113851 DFU and SQL are not fully compatible, so conversion wouldn’t be guaranteed. I can’t imagine a product that could make the jump, especially since DFU is proprietary.
 
Regardless, the ‘Answer’ suggestion to use journaling (rather than either the database monitor or the DFU logging) is almost certainly best. SQL statement logging doesn’t tell you what actually happened. Only journaling will tell you that. It’s also more reliable, and it’s actually acceptable for compliance and similar requirements where database monitor output would not be. (It’s vulnerable to manipulation.)
 
The database monitor is really appropriate for performance optimization. It’s not well structured for audit logging. It leaves out important audit items, such as which rows were affected, or in fact whether any rows were affected at all. And of course, it’s not appropriate for any non-database (non-SQL) I/O at all.
 
Since there is no conversion between DFU and SQL, it seems reasonable that you need something different. It would be helpful if you could describe the business objective that you’re trying to satisfy.
 
Tom

]]>