﻿<?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 T-SQL, Stored Procedures, System Development Life Cycle</title><link>http://www.sqlservercentral.com/</link><description>Content tagged T-SQL, Stored Procedures, System Development Life Cycle posted on SQLServerCentral.com</description><language>en-us</language><ttl>360</ttl><managingEditor>sjones@sqlservercentral.com (Steve Jones)</managingEditor><item><title>Stored Procedure Development Cycle</title><description>This month Robert covers the process he uses for developing stored procedures. In many ways it reflects how software is developed, but it does have it&amp;#39;s minor differences. This is a high level process discussion, not a line by line example of the entire process - by design of course.
</description><guid>http://www.sqlservercentral.com/articles/Stored+Procedures/storedproceduredevelopmentcycle/1120/</guid><pubDate>2003/09/03</pubDate><link>http://www.sqlservercentral.com/articles/Stored+Procedures/storedproceduredevelopmentcycle/1120/</link></item></channel></rss>