<?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: How to Estimate Database Size</title>
	<atom:link href="http://blogs.inside.quest.com/modeling/2008/07/17/how-to-estimate-database-size/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.inside.quest.com/modeling/2008/07/17/how-to-estimate-database-size/</link>
	<description>Just another Blogs.inside.quest.com weblog</description>
	<pubDate>Mon, 22 Mar 2010 10:42:15 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Arialdo</title>
		<link>http://blogs.inside.quest.com/modeling/2008/07/17/how-to-estimate-database-size/#comment-3371</link>
		<dc:creator>Arialdo</dc:creator>
		<pubDate>Sat, 08 Aug 2009 11:16:09 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.inside.quest.com/modeling/?p=50#comment-3371</guid>
		<description>Hi Vaclav.
I'm working on your script in the chance I'll be able to improve it.
The idea is to use the Size field to represent the number of rows rather than the size of the table. The script should then be able to calculate the (average) size of a single row of each table (based on the size of each field type).
This should lead to a more accurate estimation.
Obvioulsy, problems come with fields like Text, varchar and blobs, whose size is not design-defined.

I'm stucked with the problem of evaluating each field's size, but I count I'll be able to complete the script soon.

Bye and thanks for your script!</description>
		<content:encoded><![CDATA[<p>Hi Vaclav.<br />
I&#8217;m working on your script in the chance I&#8217;ll be able to improve it.<br />
The idea is to use the Size field to represent the number of rows rather than the size of the table. The script should then be able to calculate the (average) size of a single row of each table (based on the size of each field type).<br />
This should lead to a more accurate estimation.<br />
Obvioulsy, problems come with fields like Text, varchar and blobs, whose size is not design-defined.</p>
<p>I&#8217;m stucked with the problem of evaluating each field&#8217;s size, but I count I&#8217;ll be able to complete the script soon.</p>
<p>Bye and thanks for your script!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
