﻿<?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 Database Design, Visual Basic 6, Programming, Strategies</title><link>http://www.sqlservercentral.com/</link><description>Content tagged Database Design, Visual Basic 6, Programming, Strategies posted on SQLServerCentral.com</description><language>en-us</language><ttl>360</ttl><managingEditor>sjones@sqlservercentral.com (Steve Jones)</managingEditor><item><title>Version Control for Stored Procedures</title><description>Version control for stored procedures isn&amp;#39;t always popular and certainly isn&amp;#39;t easy. Or can it be? Andy discusses a technique he used on a recent project that you might find interesting.
</description><guid>http://www.sqlservercentral.com/articles/Administering/versioncontrolforstoredprocedures/681/</guid><pubDate>2002/05/10</pubDate><link>http://www.sqlservercentral.com/articles/Administering/versioncontrolforstoredprocedures/681/</link></item></channel></rss>