<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://sqlblog.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>15 shopping days left at ALFKI</title><link>http://sqlblog.com/blogs/paul_nielsen/archive/2007/12/10/15-shopping-days-left-at-alfki.aspx</link><description>I'm kicking off the next round of the SQL Server Bible series for Wiley. For the past two versions I used my own custom sample databases and skipped the MSFT sample databases (even though I feel that ALFKI's a friend and I'd love to shop there someday.)</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.1)</generator><item><title>re: 15 shopping days left at ALFKI</title><link>http://sqlblog.com/blogs/paul_nielsen/archive/2007/12/10/15-shopping-days-left-at-alfki.aspx#3819</link><pubDate>Mon, 10 Dec 2007 20:25:35 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:3819</guid><dc:creator>Denis Gobo</dc:creator><description>&lt;p&gt;Why not 3 DBs?&lt;/p&gt;
&lt;p&gt;SmallSample DB&lt;/p&gt;
&lt;p&gt;MediumSample DB&lt;/p&gt;
&lt;p&gt;LargeSample DB&lt;/p&gt;
&lt;p&gt;or is that overkill?&lt;/p&gt;
</description></item><item><title>re: 15 shopping days left at ALFKI</title><link>http://sqlblog.com/blogs/paul_nielsen/archive/2007/12/10/15-shopping-days-left-at-alfki.aspx#3820</link><pubDate>Mon, 10 Dec 2007 20:28:14 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:3820</guid><dc:creator>Adam Machanic</dc:creator><description>&lt;p&gt;Which US Census download are you referring to? &amp;nbsp;TIGER?&lt;/p&gt;
</description></item><item><title>re: 15 shopping days left at ALFKI</title><link>http://sqlblog.com/blogs/paul_nielsen/archive/2007/12/10/15-shopping-days-left-at-alfki.aspx#3821</link><pubDate>Mon, 10 Dec 2007 20:28:59 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:3821</guid><dc:creator>Paul Nielsen</dc:creator><description>&lt;p&gt;Hi Denis, do you mean small, medium, large in the number of table and complexity or the amount of data?&lt;/p&gt;
&lt;p&gt;-Paul&lt;/p&gt;
</description></item><item><title>re: 15 shopping days left at ALFKI</title><link>http://sqlblog.com/blogs/paul_nielsen/archive/2007/12/10/15-shopping-days-left-at-alfki.aspx#3822</link><pubDate>Mon, 10 Dec 2007 20:30:43 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:3822</guid><dc:creator>Paul Nielsen</dc:creator><description>&lt;p&gt;Hi Adam,&lt;/p&gt;
&lt;p&gt;I found the 1990 Census data easy to download and use, so that's what I'm playing with, but if you have a better idea, I'm open. &lt;/p&gt;
&lt;p&gt;-Paul&lt;/p&gt;
</description></item><item><title>re: 15 shopping days left at ALFKI</title><link>http://sqlblog.com/blogs/paul_nielsen/archive/2007/12/10/15-shopping-days-left-at-alfki.aspx#3823</link><pubDate>Mon, 10 Dec 2007 20:39:08 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:3823</guid><dc:creator>Adam Machanic</dc:creator><description>&lt;p&gt;Paul,&lt;/p&gt;
&lt;p&gt;I'm not familiar with the Census data itself, and didn't even know you could download it. &amp;nbsp;There is a product called TIGER that you can download which contains line segments that describe roads, large buildings, bodies of water, and other formations. &amp;nbsp;I've worked with this data and it is a tremendous pain so I was surprised that you might be considering it :-)&lt;/p&gt;
</description></item><item><title>re: 15 shopping days left at ALFKI</title><link>http://sqlblog.com/blogs/paul_nielsen/archive/2007/12/10/15-shopping-days-left-at-alfki.aspx#3824</link><pubDate>Mon, 10 Dec 2007 20:40:46 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:3824</guid><dc:creator>Denis Gobo</dc:creator><description>&lt;p&gt;Paul, &amp;nbsp;I would say size, you can always use a handful of tables. You also don't need to populate all the tables with the same number of rows.....remember not everyone has a TB on their laptop&lt;/p&gt;
</description></item><item><title>re: 15 shopping days left at ALFKI</title><link>http://sqlblog.com/blogs/paul_nielsen/archive/2007/12/10/15-shopping-days-left-at-alfki.aspx#3825</link><pubDate>Mon, 10 Dec 2007 20:56:22 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:3825</guid><dc:creator>Paul Nielsen</dc:creator><description>&lt;p&gt;Denis,&lt;/p&gt;
&lt;p&gt;I agree, that's why the sample database has to have a fixed loadable set of test data for unit testing and demo code that always generates the same answer to a query. &lt;/p&gt;
&lt;p&gt;And a Populate script can pump data into the API so the reader/developer can push the database to whatever size they want for volumn testing, or run multiple copies of the script to test transaction locking and blocking. &lt;/p&gt;
&lt;p&gt;-Paul &lt;/p&gt;
</description></item></channel></rss>