﻿<?xml version="1.0" encoding="utf-8"?><rss xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="2.0"><channel><title>SQLServerCentral.com Content tagged Referential Integrity</title><link>http://www.sqlservercentral.com/</link><description>Content tagged Referential Integrity posted on SQLServerCentral.com</description><language>en-us</language><ttl>360</ttl><managingEditor>sjones@sqlservercentral.com (Steve Jones)</managingEditor><item><title>Avoid Untrusted Constraints in SQL Server</title><description>Some time ago, I loaded a large set of data into one my tables. To speed up the load, I disabled the FOREIGN KEY and CHECK constraints on the table and then re-enabled them after the load was complete. I am now finding that some of the loaded data was referentially invalid. What happened?</description><guid>http://www.sqlservercentral.com/redirect/articles/63695/</guid><pubDate>2008/07/18</pubDate><link>http://www.sqlservercentral.com/redirect/articles/63695/</link></item><item><title>Change column type on constrained columns</title><description>Use this proc if you need to alter a column that is part of a primery key</description><guid>http://www.sqlservercentral.com/scripts/Referential+Integrity/61707/</guid><pubDate>2008/02/04</pubDate><link>http://www.sqlservercentral.com/scripts/Referential+Integrity/61707/</link></item></channel></rss>