<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Live from Kimball University: Day 3 (Architecture, Metadata, Real Time BI)</title>
	<link>http://blog.todmeansfox.com/2008/05/08/live-from-kimball-university-day-3-architecture-metadata-real-time-bi/</link>
	<description>Business Intelligence, Data Warehousing, SQL, Visual FoxPro.</description>
	<pubDate>Tue, 06 Jan 2009 11:56:52 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2</generator>

	<item>
		<title>By: Tod means Fox &#124; ETL Subsystem 27: Workflow Monitoring</title>
		<link>http://blog.todmeansfox.com/2008/05/08/live-from-kimball-university-day-3-architecture-metadata-real-time-bi/#comment-9133</link>
		<author>Tod means Fox &#124; ETL Subsystem 27: Workflow Monitoring</author>
		<pubDate>Fri, 26 Dec 2008 10:09:12 +0000</pubDate>
		<guid>http://blog.todmeansfox.com/2008/05/08/live-from-kimball-university-day-3-architecture-metadata-real-time-bi/#comment-9133</guid>
		<description>[...] When you run a job, package, or script, you should log starting and ending times. In addition to logging these timestamps, include other details such as machine name, logged in user, process name, package versioning information, number of rows processed, number of errors, and any other useful bits of information that can be used to discover areas in which you can improve your ETL system. All of this data should be stored in your database as process metadata (more about process metadata here). [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] When you run a job, package, or script, you should log starting and ending times. In addition to logging these timestamps, include other details such as machine name, logged in user, process name, package versioning information, number of rows processed, number of errors, and any other useful bits of information that can be used to discover areas in which you can improve your ETL system. All of this data should be stored in your database as process metadata (more about process metadata here). [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
