﻿<?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 Advanced Querying, Stored Procedures</title><link>http://www.sqlservercentral.com/</link><description>Content tagged Advanced Querying, Stored Procedures posted on SQLServerCentral.com</description><language>en-us</language><ttl>360</ttl><managingEditor>sjones@sqlservercentral.com (Steve Jones)</managingEditor><item><title>Self Eliminated Parameters</title><description>Optional parameters are easily handled with NULL values in T-SQL, but there are cases where this doesn&amp;#39;t always work. Alex Grinberg brings us a new technique to allow your stored procedures to be structured to deal with this situation without dynamic SQL.
</description><guid>http://www.sqlservercentral.com/articles/Advanced+Querying/2638/</guid><pubDate>2006/10/09</pubDate><link>http://www.sqlservercentral.com/articles/Advanced+Querying/2638/</link></item><item><title>How to Build Dynamic Stored Procedures</title><description>Robert is our expert on dynamic sql. This week he offers some good hints for planning the contruction of a proc that will use dynamic sql. He also adds some suggestions on how to format the code so that when you return to it later, you can figure out what you were doing!


</description><guid>http://www.sqlservercentral.com/articles/Miscellaneous/howtobuilddynamicstoredprocedures/968/</guid><pubDate>2005/12/16</pubDate><link>http://www.sqlservercentral.com/articles/Miscellaneous/howtobuilddynamicstoredprocedures/968/</link></item><item><title>Be Prepared - Part 2</title><description>Error handling in SQL Server 2000 is tricky. And it isn&amp;#39;t the most robust system in the world. Stefan Popovski started a series on error handling using @@error and xact_abort. Here&amp;#39;s the second installment of this series looking at error handling in nested stored procedures.

</description><guid>http://www.sqlservercentral.com/articles/Advanced+Querying/bepreparedpart2/1386/</guid><pubDate>2004/06/08</pubDate><link>http://www.sqlservercentral.com/articles/Advanced+Querying/bepreparedpart2/1386/</link></item><item><title>How to Build Dynamic Stored Procedures</title><description>Robert is our expert on dynamic sql. This week he offers some good hints for planning the contruction of a proc that will use dynamic sql. He also adds some suggestions on how to format the code so that when you return to it later, you can figure out what you were doing!


</description><guid>http://www.sqlservercentral.com/articles/Miscellaneous/howtobuilddynamicstoredprocedures/968/</guid><pubDate>2005/12/16</pubDate><link>http://www.sqlservercentral.com/articles/Miscellaneous/howtobuilddynamicstoredprocedures/968/</link></item><item><title>Default Values and Named Parameters for Stored Procs</title><description>Are you using default values for your parameters? Using named parameters when you call the proc or passing the values by ordinal? Should you be? Andy thinks 6 out of 10 of our readers will agree with his point of view, we&amp;#39;ll be a little more conservative and guess that 5 of out 10 will be closer.
</description><guid>http://www.sqlservercentral.com/articles/Miscellaneous/defaultvaluesandnamedparametersforstoredprocs/882/</guid><pubDate>2003/01/08</pubDate><link>http://www.sqlservercentral.com/articles/Miscellaneous/defaultvaluesandnamedparametersforstoredprocs/882/</link></item><item><title>DoEvents with SQL Server 2000 and Extended Procedures</title><description>In this article, we will leverage Extended Stored Procedures to extend the functionality of SQL Server and give a starting point to experiment with Extended Stored Procedures.
</description><guid>http://www.sqlservercentral.com/articles/Advanced+Querying/doevents/784/</guid><pubDate>2002/08/26</pubDate><link>http://www.sqlservercentral.com/articles/Advanced+Querying/doevents/784/</link></item><item><title>Creating your own sp_MSforeach stored procedure</title><description>This article shows you one of the most time saving stored procedure built into SQL Server and then shows you how you can modify it to affect additional objects like triggers. For example, after this article and the code in the article, you&amp;#39;ll be able to disable every trigger in your system in one line of code.
</description><guid>http://www.sqlservercentral.com/articles/Administering/sp_msforeachworker/711/</guid><pubDate>2002/06/17</pubDate><link>http://www.sqlservercentral.com/articles/Administering/sp_msforeachworker/711/</link></item><item><title>Making Dynamic Queries Static</title><description>Building and executing dynamic sql in a stored procedure - is it the only way to solve problems like supporting a simple search function? Leon offers a couple alternatives that let you continue to provide the functionality in a stored procedure without using dynamic sql. Interesting ideas worth exploring!
</description><guid>http://www.sqlservercentral.com/articles/Performance+Tuning+and+Scaling/makingdynamicqueriesstatic/672/</guid><pubDate>2002/05/02</pubDate><link>http://www.sqlservercentral.com/articles/Performance+Tuning+and+Scaling/makingdynamicqueriesstatic/672/</link></item><item><title>SP_MSFOREACHDB - Getting a list of databases via TSQL.</title><description>Sp_MSforeachdb gives a DBA the ability to cycle through every database in your catalog. Find out how to use it.
</description><guid>http://www.sqlservercentral.com/articles/Advanced+Querying/sp_msforeachdb/182/</guid><pubDate>2001/05/31</pubDate><link>http://www.sqlservercentral.com/articles/Advanced+Querying/sp_msforeachdb/182/</link></item></channel></rss>