<?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: SQL SERVER - 2008 - Introduction to SPARSE Columns - Part 2</title>
	<atom:link href="http://blog.sqlauthority.com/2008/07/14/sql-server-2008-introduction-to-sparse-columns-part-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.sqlauthority.com/2008/07/14/sql-server-2008-introduction-to-sparse-columns-part-2/</link>
	<description>Notes of a SQL Server MVP and Database Administrator</description>
	<pubDate>Wed, 07 Jan 2009 16:35:07 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Qingsong Yao</title>
		<link>http://blog.sqlauthority.com/2008/07/14/sql-server-2008-introduction-to-sparse-columns-part-2/#comment-43539</link>
		<dc:creator>Qingsong Yao</dc:creator>
		<pubDate>Mon, 06 Oct 2008 18:37:08 +0000</pubDate>
		<guid isPermaLink="false">http://sqlauthority.wordpress.com/?p=683#comment-43539</guid>
		<description>if you create a wide table (i.e., a table with column set).  The default in/out method will only show the column set and hidden all sparse columns.  If you want to import using the sparse columns,  you may need to create a customized format file.  Please refer the bcp format file for details.</description>
		<content:encoded><![CDATA[<p>if you create a wide table (i.e., a table with column set).  The default in/out method will only show the column set and hidden all sparse columns.  If you want to import using the sparse columns,  you may need to create a customized format file.  Please refer the bcp format file for details.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mo Tamman</title>
		<link>http://blog.sqlauthority.com/2008/07/14/sql-server-2008-introduction-to-sparse-columns-part-2/#comment-42940</link>
		<dc:creator>Mo Tamman</dc:creator>
		<pubDate>Thu, 18 Sep 2008 13:33:31 +0000</pubDate>
		<guid isPermaLink="false">http://sqlauthority.wordpress.com/?p=683#comment-42940</guid>
		<description>So I've created my wide table and I need to import a comma delimited file...and for the life of me, I cannot get it to import.

I've used the import wizard (didn't expect that to work) and bulk insert, all to no avail.

Is there a trick to this?</description>
		<content:encoded><![CDATA[<p>So I&#8217;ve created my wide table and I need to import a comma delimited file&#8230;and for the life of me, I cannot get it to import.</p>
<p>I&#8217;ve used the import wizard (didn&#8217;t expect that to work) and bulk insert, all to no avail.</p>
<p>Is there a trick to this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Qingsong Yao</title>
		<link>http://blog.sqlauthority.com/2008/07/14/sql-server-2008-introduction-to-sparse-columns-part-2/#comment-41688</link>
		<dc:creator>Qingsong Yao</dc:creator>
		<pubDate>Thu, 14 Aug 2008 19:19:06 +0000</pubDate>
		<guid isPermaLink="false">http://sqlauthority.wordpress.com/?p=683#comment-41688</guid>
		<description>Hello, Richard
  In order to create more than 1024 columns,  you have to have a columnset column defined in the table.  We explict request this because the client can not retrieve more than 1024 columns, and  we do not want people facing the issue of not being to retrieving data.  Once the table has columnset defined, the select * will hide all sparse columns, and only see the column set.  Neanwhile, people can still select individual sparse columns in their query.   The default value of sparse column is NUll, that is the reason why we can not have default or rule on the column</description>
		<content:encoded><![CDATA[<p>Hello, Richard<br />
  In order to create more than 1024 columns,  you have to have a columnset column defined in the table.  We explict request this because the client can not retrieve more than 1024 columns, and  we do not want people facing the issue of not being to retrieving data.  Once the table has columnset defined, the select * will hide all sparse columns, and only see the column set.  Neanwhile, people can still select individual sparse columns in their query.   The default value of sparse column is NUll, that is the reason why we can not have default or rule on the column</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Topf</title>
		<link>http://blog.sqlauthority.com/2008/07/14/sql-server-2008-introduction-to-sparse-columns-part-2/#comment-41526</link>
		<dc:creator>Richard Topf</dc:creator>
		<pubDate>Sat, 09 Aug 2008 13:57:58 +0000</pubDate>
		<guid isPermaLink="false">http://sqlauthority.wordpress.com/?p=683#comment-41526</guid>
		<description>Sorry if this is a naive point!

Now we have the final release of SQl 2008, I have been trying to create a table with more that 1024 columns. I cannot. Even if all columns are defined as 'int sparse' I still get a max 1024 col error message.

Any advice would be very welcome.</description>
		<content:encoded><![CDATA[<p>Sorry if this is a naive point!</p>
<p>Now we have the final release of SQl 2008, I have been trying to create a table with more that 1024 columns. I cannot. Even if all columns are defined as &#8216;int sparse&#8217; I still get a max 1024 col error message.</p>
<p>Any advice would be very welcome.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kamran Shahid</title>
		<link>http://blog.sqlauthority.com/2008/07/14/sql-server-2008-introduction-to-sparse-columns-part-2/#comment-40889</link>
		<dc:creator>Kamran Shahid</dc:creator>
		<pubDate>Mon, 28 Jul 2008 07:36:14 +0000</pubDate>
		<guid isPermaLink="false">http://sqlauthority.wordpress.com/?p=683#comment-40889</guid>
		<description>SPARSE column can not have default value or rule or computed column.

Only this thing looks odd.Other things are not that much problem</description>
		<content:encoded><![CDATA[<p>SPARSE column can not have default value or rule or computed column.</p>
<p>Only this thing looks odd.Other things are not that much problem</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SQL SERVER - 2008 - Introduction to SPARSE Columns Journey to SQL Authority with Pinal Dave</title>
		<link>http://blog.sqlauthority.com/2008/07/14/sql-server-2008-introduction-to-sparse-columns-part-2/#comment-40200</link>
		<dc:creator>SQL SERVER - 2008 - Introduction to SPARSE Columns Journey to SQL Authority with Pinal Dave</dc:creator>
		<pubDate>Mon, 14 Jul 2008 09:52:23 +0000</pubDate>
		<guid isPermaLink="false">http://sqlauthority.wordpress.com/?p=683#comment-40200</guid>
		<description>[...] UPDATE : Read Advantages and Disadvantages of SPARSE Column SQL SERVER - 2008 - Introduction to SPARSE Columns - Part 2 [...]</description>
		<content:encoded><![CDATA[<p>[...] UPDATE : Read Advantages and Disadvantages of SPARSE Column SQL SERVER - 2008 - Introduction to SPARSE Columns - Part 2 [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
