<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Using ColdFusion and Timeline to visualize DTS task logs</title>
	<atom:link href="http://rickosborne.org/blog/index.php/2006/07/10/using-coldfusion-and-timeline-to-visualize-dts-task-logs/feed/" rel="self" type="application/rss+xml" />
	<link>http://rickosborne.org/blog/index.php/2006/07/10/using-coldfusion-and-timeline-to-visualize-dts-task-logs/</link>
	<description>Striving to subdue the mediocrity.</description>
	<lastBuildDate>Fri, 05 Mar 2010 15:14:08 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Liming Xu</title>
		<link>http://rickosborne.org/blog/index.php/2006/07/10/using-coldfusion-and-timeline-to-visualize-dts-task-logs/comment-page-1/#comment-42</link>
		<dc:creator>Liming Xu</dc:creator>
		<pubDate>Thu, 20 Jul 2006 04:37:15 +0000</pubDate>
		<guid isPermaLink="false">http://rickosborne.org/blog/?p=51#comment-42</guid>
		<description>Makes sense. Thanks for the explanation. I got my expand working, but tweaked for couple of days now, still not perfect. :( though bearable.</description>
		<content:encoded><![CDATA[<p>Makes sense. Thanks for the explanation. I got my expand working, but tweaked for couple of days now, still not perfect. :( though bearable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rick Osborne</title>
		<link>http://rickosborne.org/blog/index.php/2006/07/10/using-coldfusion-and-timeline-to-visualize-dts-task-logs/comment-page-1/#comment-30</link>
		<dc:creator>Rick Osborne</dc:creator>
		<pubDate>Tue, 11 Jul 2006 19:01:00 +0000</pubDate>
		<guid isPermaLink="false">http://rickosborne.org/blog/?p=51#comment-30</guid>
		<description>I just made it full browser size, as I figured it would only frustrate me to have it some random percentage of the screen.  Since I was able to integrate all of the DTS details, having other non-timeline information on the screen wasn&#039;t necessary.

However, I have the same problem of stacked events that you do.  I figured that instead of trying to guess the height, it would make more sense for me to expand the timeline horizontally.  This has the added benefit of giving a more fine-grained level of detail.  Going from HOUR to MINUTE is a bit too much of a jump for me, so I made QUARTERHOUR and QUARTERMINUTE resolutions.  The CF just looks at the overall time and tries to guess the best resolution.  (I think the logic now is that if the job takes less than 15 minutes, go to the MINUTE level, otherwise go up to QUARTERHOUR.)

There are still a few jobs that run a lot of little small tasks all at once, and my thought for how to deal with them would be hotspot detection.  Since Timeline will let you easily create hotspots, I figure a quick CFLOOP over the query looking for (DateDiff(&#039;s&#039;,StartTime[CurrentRow],StartTime[CurrentRow+10]) LT 60), that is less than 60 seconds for ten tasks, would be a good place to add a hotspot.  I haven&#039;t implemented it yet, but that&#039;s what I was thinking.</description>
		<content:encoded><![CDATA[<p>I just made it full browser size, as I figured it would only frustrate me to have it some random percentage of the screen.  Since I was able to integrate all of the DTS details, having other non-timeline information on the screen wasn&#8217;t necessary.</p>
<p>However, I have the same problem of stacked events that you do.  I figured that instead of trying to guess the height, it would make more sense for me to expand the timeline horizontally.  This has the added benefit of giving a more fine-grained level of detail.  Going from HOUR to MINUTE is a bit too much of a jump for me, so I made QUARTERHOUR and QUARTERMINUTE resolutions.  The CF just looks at the overall time and tries to guess the best resolution.  (I think the logic now is that if the job takes less than 15 minutes, go to the MINUTE level, otherwise go up to QUARTERHOUR.)</p>
<p>There are still a few jobs that run a lot of little small tasks all at once, and my thought for how to deal with them would be hotspot detection.  Since Timeline will let you easily create hotspots, I figure a quick CFLOOP over the query looking for (DateDiff(&#8217;s&#8217;,StartTime[CurrentRow],StartTime[CurrentRow+10]) LT 60), that is less than 60 seconds for ten tasks, would be a good place to add a hotspot.  I haven&#8217;t implemented it yet, but that&#8217;s what I was thinking.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Liming Xu</title>
		<link>http://rickosborne.org/blog/index.php/2006/07/10/using-coldfusion-and-timeline-to-visualize-dts-task-logs/comment-page-1/#comment-29</link>
		<dc:creator>Liming Xu</dc:creator>
		<pubDate>Tue, 11 Jul 2006 02:00:29 +0000</pubDate>
		<guid isPermaLink="false">http://rickosborne.org/blog/?p=51#comment-29</guid>
		<description>Hi, 

I&#039;m wondering how did you decided the &quot;height&quot; of the timeline? Because by default, it requires you to know how many events are gonne be there, otherwise, vertically(from top to bottom), if there are too many, it&#039;ll get cut off. 

I tried my implementation of it to expand based upon the number of events (but not perfect), I&#039;m wondering if got it working. 

Thanks</description>
		<content:encoded><![CDATA[<p>Hi, </p>
<p>I&#8217;m wondering how did you decided the &#8220;height&#8221; of the timeline? Because by default, it requires you to know how many events are gonne be there, otherwise, vertically(from top to bottom), if there are too many, it&#8217;ll get cut off. </p>
<p>I tried my implementation of it to expand based upon the number of events (but not perfect), I&#8217;m wondering if got it working. </p>
<p>Thanks</p>
]]></content:encoded>
	</item>
</channel>
</rss>
