<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: SQL SERVER &#8211; Difference Between Candidate Keys and Primary Key</title>
	<atom:link href="http://blog.sqlauthority.com/2009/05/30/sql-server-difference-between-candidate-keys-and-primary-key/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.sqlauthority.com/2009/05/30/sql-server-difference-between-candidate-keys-and-primary-key/</link>
	<description>Personal Notes of Pinal Dave</description>
	<lastBuildDate>Sun, 12 Feb 2012 09:22:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: ankita</title>
		<link>http://blog.sqlauthority.com/2009/05/30/sql-server-difference-between-candidate-keys-and-primary-key/#comment-250050</link>
		<dc:creator><![CDATA[ankita]]></dc:creator>
		<pubDate>Wed, 08 Feb 2012 15:38:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=5208#comment-250050</guid>
		<description><![CDATA[how to identify condidate key  plz tell me?]]></description>
		<content:encoded><![CDATA[<p>how to identify condidate key  plz tell me?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: anonymous</title>
		<link>http://blog.sqlauthority.com/2009/05/30/sql-server-difference-between-candidate-keys-and-primary-key/#comment-241288</link>
		<dc:creator><![CDATA[anonymous]]></dc:creator>
		<pubDate>Fri, 20 Jan 2012 11:59:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=5208#comment-241288</guid>
		<description><![CDATA[the main reason why it is called &quot;composite key&quot; is because it can only be made of two or more- but not one- attributes. a composite key is not just a primary key: it can be a candidate and superkey as well. but the original meaning lies in the fact that it is made up of more than one attribute]]></description>
		<content:encoded><![CDATA[<p>the main reason why it is called &#8220;composite key&#8221; is because it can only be made of two or more- but not one- attributes. a composite key is not just a primary key: it can be a candidate and superkey as well. but the original meaning lies in the fact that it is made up of more than one attribute</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sagar</title>
		<link>http://blog.sqlauthority.com/2009/05/30/sql-server-difference-between-candidate-keys-and-primary-key/#comment-142463</link>
		<dc:creator><![CDATA[Sagar]]></dc:creator>
		<pubDate>Mon, 20 Jun 2011 14:21:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=5208#comment-142463</guid>
		<description><![CDATA[@Jasminder: A composite key is a primary key which has more than 1 column. For example consider the many to many relation between student and courses. Here we need another table , lets say studentcourses  . 

This studentcourses table will have student id and course id as its columns. This will form your composite key. 

Candidate key   is a set of columns which can uniquely identify the values in a table and can act as a unique key. One of these candidate keys will become the primary key and the rest will become alternate keys. 

Unique key as the name suggests , is used to uniquely identify a value in a table. For example Emp_id etc. Every candidate key will act as a unique key. Unique key can never be a NULL value.]]></description>
		<content:encoded><![CDATA[<p>@Jasminder: A composite key is a primary key which has more than 1 column. For example consider the many to many relation between student and courses. Here we need another table , lets say studentcourses  . </p>
<p>This studentcourses table will have student id and course id as its columns. This will form your composite key. </p>
<p>Candidate key   is a set of columns which can uniquely identify the values in a table and can act as a unique key. One of these candidate keys will become the primary key and the rest will become alternate keys. </p>
<p>Unique key as the name suggests , is used to uniquely identify a value in a table. For example Emp_id etc. Every candidate key will act as a unique key. Unique key can never be a NULL value.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jasminder</title>
		<link>http://blog.sqlauthority.com/2009/05/30/sql-server-difference-between-candidate-keys-and-primary-key/#comment-62783</link>
		<dc:creator><![CDATA[Jasminder]]></dc:creator>
		<pubDate>Fri, 12 Mar 2010 04:34:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=5208#comment-62783</guid>
		<description><![CDATA[Can u plz explain what is difference between Composite Key and Candidate Key ?

Also what is importance of Unique Key in Candidate key]]></description>
		<content:encoded><![CDATA[<p>Can u plz explain what is difference between Composite Key and Candidate Key ?</p>
<p>Also what is importance of Unique Key in Candidate key</p>
]]></content:encoded>
	</item>
</channel>
</rss>

