<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>primary key on AdaTheDev Blog</title><link>https://www.adathedev.co.uk/tags/primary-key/</link><description>Recent content in primary key on AdaTheDev Blog</description><generator>Hugo -- gohugo.io</generator><managingEditor>adathedev@gmail.com (Adrian Hills)</managingEditor><webMaster>adathedev@gmail.com (Adrian Hills)</webMaster><lastBuildDate>Mon, 01 Mar 2010 08:00:00 +0000</lastBuildDate><atom:link href="https://www.adathedev.co.uk/tags/primary-key/index.xml" rel="self" type="application/rss+xml"/><item><title>Changing primary key index structure</title><link>https://www.adathedev.co.uk/2010/03/changing-primary-key-index-structure.html</link><pubDate>Mon, 01 Mar 2010 08:00:00 +0000</pubDate><author>adathedev@gmail.com (Adrian Hills)</author><guid>https://www.adathedev.co.uk/2010/03/changing-primary-key-index-structure.html</guid><description>Changing the structure of a primary key constraint index from nonclustered to clustered (or from clustered to nonclustered) is not necessarily as straight forward as it first seems. The process of changing it over, involves the constraint being dropped and then recreated. This could potentially cause a problem if you&amp;rsquo;re making the change on a table whilst there could be activity against it.
Example
TableX was originally created as below:</description></item></channel></rss>