 




<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>IT Answers &#187; Data Warehouse Planning</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/tag/data-warehouse-planning/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers</link>
	<description></description>
	<lastBuildDate>Mon, 20 May 2013 00:58:28 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Pros &amp; cons to have a typical star schema but with only one fact value field and a thousand attribute names in one of the dimension tables?</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/pros-cons-to-have-a-typical-star-schema-but-with-only-one-fact-value-field-and-a-thousand-attribute-names-in-one-of-the-dimension-tables/</link>
		<comments>http://itknowledgeexchange.techtarget.com/itanswers/pros-cons-to-have-a-typical-star-schema-but-with-only-one-fact-value-field-and-a-thousand-attribute-names-in-one-of-the-dimension-tables/#comments</comments>
		<pubDate>Wed, 25 Nov 2009 12:07:30 +0000</pubDate>
		<dc:creator>Rwg</dc:creator>
				<category><![CDATA[Data Warehouse Planning]]></category>
		<category><![CDATA[Data warehousing]]></category>
		<category><![CDATA[SQL]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[Want to build a kind of a scientific fact search and analytical engine for a lot of different types of measurements hosted in a lot of source tables and columns. A star join schema is built and data is copied (ETL) from the sources as usual &#8211; but all source column values are stored into [...]]]></description>
				<content:encoded><![CDATA[<p>Want to build a kind of a scientific fact search and analytical engine for a lot of different types of measurements hosted in a lot of source tables and columns. <br/><br/> A star join schema is built and data is copied (ETL) from the sources as usual &#8211; but all source column values are stored into a single fact-table value column and each column name is represented by a surrogate foreign key referencing a dimension table where the source table and column names are prestored. <br/><br/> There are several other dimensions as well, as usual. In this design ER-structures in the source database are deliberately abandoned, the only structure that is preserved is repeating groups through a simple serial number dimesion, so that e.g. time series values and depth intervals (stratigraphy) are chained. One might have a second fact value column for alphanumeric codes. <br/><br/> There will be a lot of rows in the fact table, but rather short ones. The star join database can be searched with SQL and simple statistics may be presented or one may take resulting datasets to other analytical tools, e.g. Excel. The SQL in queries may sometimes be tricky in this design. One might create (with SQL-scripts) smaller and specialized data marts on different topics from this data warehouse.<br/><br/> An interesting quality is that space coordinates in the fact table open up for unlimited possibilities to select and present data on digital maps from a GIS tool.  <br/><br/> /RWg, Geological Survey of Sweden.<br/><br/></p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/itanswers/pros-cons-to-have-a-typical-star-schema-but-with-only-one-fact-value-field-and-a-thousand-attribute-names-in-one-of-the-dimension-tables/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Build a Data warehouse end to end</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/build-a-dataware-end-to-end/</link>
		<comments>http://itknowledgeexchange.techtarget.com/itanswers/build-a-dataware-end-to-end/#comments</comments>
		<pubDate>Mon, 03 Aug 2009 12:39:51 +0000</pubDate>
		<dc:creator>Jsql</dc:creator>
				<category><![CDATA[Data Warehouse Planning]]></category>
		<category><![CDATA[Data warehouses]]></category>
		<category><![CDATA[Data warehousing]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[Im asked to build a datawarehouse from end to end. I have already worked on datawarehousing projects. I need to prepare a proposal document. How do i prepare a proposal document that explains End-to-end development. Can I get a sample document? Thanks.]]></description>
				<content:encoded><![CDATA[<p>Im asked to build a datawarehouse from end to end. I have already worked on datawarehousing projects. I need to prepare a proposal document.</p>
<p>How do i prepare a proposal document that explains End-to-end development. Can I get a sample document?</p>
<p>Thanks.</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/itanswers/build-a-dataware-end-to-end/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 3/16 queries in 0.021 seconds using memcached
Object Caching 380/413 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-20 04:34:14 -->