<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>WebMastersLoom &#187; SQL Server</title>
	<atom:link href="http://www.webmastersloom.com/category/languages-and-tools/sql-server/feed" rel="self" type="application/rss+xml" />
	<link>http://www.webmastersloom.com</link>
	<description>Enabling the architects and builders of the web. Information and resources for webmasters.</description>
	<lastBuildDate>Fri, 15 Aug 2008 21:27:24 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>T-SQL Tips</title>
		<link>http://www.webmastersloom.com/115/t-sql-tips-2</link>
		<comments>http://www.webmastersloom.com/115/t-sql-tips-2#comments</comments>
		<pubDate>Sun, 14 Aug 2005 01:47:44 +0000</pubDate>
		<dc:creator>Administrator</dc:creator>
				<category><![CDATA[SQL Server]]></category>

		<guid isPermaLink="false">http://www.webmastersloom.com/115/t-sql-tips-2</guid>
		<description><![CDATA[1.Never use embedded T-SQL; always use stored procedures.
2.&#160;&#160;&#160;&#160;&#160;&#160; Never do a select * even if you need all fields from a table or view. This makes code more efficient, reusable and is much less likely that a change may affect an application as it may change the order of the columns etc. The column set [...]]]></description>
		<wfw:commentRss>http://www.webmastersloom.com/115/t-sql-tips-2/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SQL Server XML Performance Tips</title>
		<link>http://www.webmastersloom.com/113/sql-server-xml-performance-tips-2</link>
		<comments>http://www.webmastersloom.com/113/sql-server-xml-performance-tips-2#comments</comments>
		<pubDate>Sun, 14 Aug 2005 01:46:48 +0000</pubDate>
		<dc:creator>Administrator</dc:creator>
				<category><![CDATA[SQL Server]]></category>

		<guid isPermaLink="false">http://www.webmastersloom.com/113/sql-server-xml-performance-tips-2</guid>
		<description><![CDATA[< ?xml:namespace prefix ="" o ns ="" "urn:schemas-microsoft-com:office:office" />
When using the FOR XML clause in your Transact-SQL applications, don&#8217;t include the XMLDATA option. The XMLDATA option returns additional XML schema data that generally is not needed. Because of this, using this option adds extra overhead to your server and network connection, reducing performance. [2000] Added [...]]]></description>
		<wfw:commentRss>http://www.webmastersloom.com/113/sql-server-xml-performance-tips-2/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SQL Server Database Coding Conventions</title>
		<link>http://www.webmastersloom.com/111/sql-server-database-coding-conventions</link>
		<comments>http://www.webmastersloom.com/111/sql-server-database-coding-conventions#comments</comments>
		<pubDate>Sun, 14 Aug 2005 01:45:24 +0000</pubDate>
		<dc:creator>Administrator</dc:creator>
				<category><![CDATA[SQL Server]]></category>

		<guid isPermaLink="false">http://www.webmastersloom.com/111/sql-server-database-coding-conventions</guid>
		<description><![CDATA[
Best Practices, and Programming Guidelines

< ?xml:namespace prefix ="" o ns ="" "urn:schemas-microsoft-com:office:office" />&#160;
Databases are the heart and soul of many enterprise applications, and it is very essential to pay special attention to database programming. I&#8217;ve seen in many occasions where database programming is overlooked, thinking that it&#8217;s something easy that be done by anyone. This [...]]]></description>
		<wfw:commentRss>http://www.webmastersloom.com/111/sql-server-database-coding-conventions/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Database Naming Convention</title>
		<link>http://www.webmastersloom.com/110/database-naming-convention</link>
		<comments>http://www.webmastersloom.com/110/database-naming-convention#comments</comments>
		<pubDate>Sun, 14 Aug 2005 01:43:59 +0000</pubDate>
		<dc:creator>Administrator</dc:creator>
				<category><![CDATA[SQL Server]]></category>

		<guid isPermaLink="false">http://www.webmastersloom.com/110/database-naming-convention</guid>
		<description><![CDATA[

Naming conventions
&#160;Stored Procedures
Stored procedure names should conform to the following convention:
AppName_ActionName< ?xml:namespace prefix ="" o ns ="" "urn:schemas-microsoft-com:office:office" />
e.g. HES_GetOfferDetails
&#160;




Property


Description




AppName


Name of the application/system that uses the stored procedure. E.g. &#8220;AM&#8221; (AdMaker),&#8221; HES&#8221;,&#8221; CPT&#8221;, etc
In some cases it could be a variant of the application, e.g. &#8220;VHES_Admin&#8221;




ActionName


Name of the action using Pascal notation. This should start [...]]]></description>
		<wfw:commentRss>http://www.webmastersloom.com/110/database-naming-convention/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Checks before making database changes live</title>
		<link>http://www.webmastersloom.com/109/checks-before-making-database-changes-live</link>
		<comments>http://www.webmastersloom.com/109/checks-before-making-database-changes-live#comments</comments>
		<pubDate>Sun, 14 Aug 2005 01:41:20 +0000</pubDate>
		<dc:creator>Administrator</dc:creator>
				<category><![CDATA[SQL Server]]></category>

		<guid isPermaLink="false">http://www.webmastersloom.com/109/checks-before-making-database-changes-live</guid>
		<description><![CDATA[&#183;&#160;&#160;&#160;&#160;&#160;&#160;&#160; Developer: Acquire a good understanding of the effect a query has on the underlying database.< ?xml:namespace prefix ="" o ns ="" "urn:schemas-microsoft-com:office:office" />
&#183;&#160;&#160;&#160;&#160;&#160;&#160;&#160; DBA: Perform regression testing and trend-analysis when moving any code (in application or database) from development servers to QA/test servers and onto production.
&#183;&#160;&#160;&#160;&#160;&#160;&#160;&#160; DBA: Make sure proper indexes are in place.
&#183;&#160;&#160;&#160;&#160;&#160;&#160;&#160; [...]]]></description>
		<wfw:commentRss>http://www.webmastersloom.com/109/checks-before-making-database-changes-live/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
