﻿<?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, Basic Querying, Advanced Querying</title><link>http://www.sqlservercentral.com/</link><description>Content tagged T-SQL, Basic Querying, Advanced Querying posted on SQLServerCentral.com</description><language>en-us</language><ttl>360</ttl><managingEditor>sjones@sqlservercentral.com (Steve Jones)</managingEditor><item><title>Using Exotic Joins in SQL Part 1</title><description>When most developers think of joins, they think of a.SomethingID = b.SomethingID. This type of join, the equijoin, is vitally important to SQL programming; however, it only scratches the surface of the power of the SQL join. This is the first in a series of articles that will look at several different types of exotic joins in SQL. This article will focus on using the BETWEEN operator in joins when dealing with range-based data.

</description><guid>http://www.sqlservercentral.com/articles/Basic+Querying/usingexoticjoinsinsql/899/</guid><pubDate>2005/04/29</pubDate><link>http://www.sqlservercentral.com/articles/Basic+Querying/usingexoticjoinsinsql/899/</link></item><item><title>New MDX Book Published</title><description>Fast Track to MDX gives readers all the necessary background information needed to write useful, powerful MDX expressions and introduces the most frequently used MDX functions and constructs. No prior knowledge is assumed and examples are used throughout the book to rapidly develop MDX skills to the point where a reader can solve real business problems. A CD containing examples from within the book, and a time-limited version of ProClarity, is included</description><guid>http://www.sqlservercentral.com/redirect/articles/971/</guid><pubDate>2003/05/01</pubDate><link>http://www.sqlservercentral.com/redirect/articles/971/</link></item><item><title>Gathering Random Data</title><description>Brian Knight recently had the basic need to retrieve a record from the database at random. What seemed to be an easy task quickly became a complex one. This case showed an interesting quirk with T-SQL that was resolved in an equally quirky way. This quick article shows you a method to retrieve random data or randomize the display of data.

</description><guid>http://www.sqlservercentral.com/articles/Basic+Querying/randomvalues/943/</guid><pubDate>2003/03/26</pubDate><link>http://www.sqlservercentral.com/articles/Basic+Querying/randomvalues/943/</link></item><item><title>Reusing Identities</title><description>Ever wanted to know how to reuse identity values after they&amp;#39;re deleted? In this example by Dinesh, he shows you two methods to reuse the wholes in identity rows.




</description><guid>http://www.sqlservercentral.com/articles/Basic+Querying/reuseidentities/915/</guid><pubDate>2003/02/18</pubDate><link>http://www.sqlservercentral.com/articles/Basic+Querying/reuseidentities/915/</link></item><item><title>Using Exotic Joins in SQL - Part 2</title><description>In the previous article, you saw how the BETWEEN operator could be used in joins to solve problems dealing with range-based data. In this article, Chris Cubley will show you how to take joins even further by using multiple criteria in joins as well as using the greater than, less than, and not equals operators in joins.

</description><guid>http://www.sqlservercentral.com/articles/Basic+Querying/usingexoticjoinsinsqlpart2/904/</guid><pubDate>2003/02/05</pubDate><link>http://www.sqlservercentral.com/articles/Basic+Querying/usingexoticjoinsinsqlpart2/904/</link></item><item><title>Using Exotic Joins in SQL Part 1</title><description>When most developers think of joins, they think of a.SomethingID = b.SomethingID. This type of join, the equijoin, is vitally important to SQL programming; however, it only scratches the surface of the power of the SQL join. This is the first in a series of articles that will look at several different types of exotic joins in SQL. This article will focus on using the BETWEEN operator in joins when dealing with range-based data.

</description><guid>http://www.sqlservercentral.com/articles/Basic+Querying/usingexoticjoinsinsql/899/</guid><pubDate>2005/04/29</pubDate><link>http://www.sqlservercentral.com/articles/Basic+Querying/usingexoticjoinsinsql/899/</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>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></channel></rss>