<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">
<channel>
<title>MSSQLTips - Latest SQL Server  Tips</title>
<link>http://www.mssqltips.com/</link>
<description>Last five SQL Server  tips from MSSQLTips.com</description>
<language>en-us</language>

<lastBuildDate>Fri, 6 Nov 2009 08:00:00 GMT</lastBuildDate>
<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/MSSQLTips-LatestSqlServerTips" type="application/rss+xml" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><item>
<title>Best Practices � When Using FILESTREAM Feature of SQL Server 2008</title>
<description>In SQL Server 2008 one can store BLOBs (e.g. Images, video, Word, Excel, PDF, MP3, etc) in the NTFS file system rather than in a database file. This can be done by using the new FILESTREAM feature which was introduced in SQL Server 2008. In this tip we will take a look at some of the best practices which a database administrator can follow to get the best performance when using the FILESTREAM feature of SQL Server 2008.&lt;img src="http://feeds.feedburner.com/~r/MSSQLTips-LatestSqlServerTips/~4/QXOX9WDweOA" height="1" width="1"/&gt;</description>
<link>http://feedproxy.google.com/~r/MSSQLTips-LatestSqlServerTips/~3/QXOX9WDweOA/tip.asp</link>
<pubDate>Fri, 6 Nov 2009 08:00:00 GMT</pubDate>
<feedburner:origLink>http://www.mssqltips.com/tip.asp?tip=1875</feedburner:origLink></item>
<item>
<title>Moving your database to the cloud with SQL Azure - Part 1 </title>
<description>There has been lots of buzz about cloud computing lately and looking at the benefits it provides (in terms of cost savings, high availability, scalability (scale up/down) etc.) it is now evident that cloud computing is the future for next generation applications. In this tip series, I am going to show how you can start creating databases and database objects on the cloud with SQL Azure.&lt;img src="http://feeds.feedburner.com/~r/MSSQLTips-LatestSqlServerTips/~4/qGOkj7ftKlU" height="1" width="1"/&gt;</description>
<link>http://feedproxy.google.com/~r/MSSQLTips-LatestSqlServerTips/~3/qGOkj7ftKlU/tip.asp</link>
<pubDate>Thu, 5 Nov 2009 08:00:00 GMT</pubDate>
<feedburner:origLink>http://www.mssqltips.com/tip.asp?tip=1874</feedburner:origLink></item>
<item>
<title>How to read SQL Server graphical query execution plans</title>
<description>In the previous tip in this series, I gave you an initial look into how to launch and read a graphical query execution plan.  We're going to dive deeper into the different opportunities for information sources within the graphical execution plan itself.  Yes, you read that right.  There are other sources of information in the graphical execution plan that are not readily apparent at first blush.  This tip will focus on Tooltips and the next on the Properties window.&lt;img src="http://feeds.feedburner.com/~r/MSSQLTips-LatestSqlServerTips/~4/z98W64yAYiw" height="1" width="1"/&gt;</description>
<link>http://feedproxy.google.com/~r/MSSQLTips-LatestSqlServerTips/~3/z98W64yAYiw/tip.asp</link>
<pubDate>Wed, 4 Nov 2009 08:00:00 GMT</pubDate>
<feedburner:origLink>http://www.mssqltips.com/tip.asp?tip=1873</feedburner:origLink></item>
<item>
<title>Introduction to the Database Engine Tuning Advisor (DTA) for Performance Tuning</title>
<description>I have identified one production database in particular where the business users are constantly complaining about slow performance.  I would like to focus strictly on identifying and mitigating issues related to query performance in that database.  What's the best tool to analyze a workload and identify improvements?  In this tip we look at how to use the Database Engine Tuning Advisor (DTA) to identify performance issues and resolutions.&lt;img src="http://feeds.feedburner.com/~r/MSSQLTips-LatestSqlServerTips/~4/MM1uR0AbiE4" height="1" width="1"/&gt;</description>
<link>http://feedproxy.google.com/~r/MSSQLTips-LatestSqlServerTips/~3/MM1uR0AbiE4/tip.asp</link>
<pubDate>Tue, 3 Nov 2009 08:00:00 GMT</pubDate>
<feedburner:origLink>http://www.mssqltips.com/tip.asp?tip=1872</feedburner:origLink></item>
<item>
<title>Customizing the Status Bar for Each SSMS Connection</title>
<description>Almost every DBA has to manage more than one instance of SQL Server. If you are administering production, test and development servers then there are probably databases with similar names and structures in each of these instances. The scenario becomes more complicated when you are working with multiple logins in each instance at the same time. Chances increase to run a script on an instance other than on which it was intended to run. Although every query pane in SSMS includes information such as server instance and user this information is not always displayed prominently. In this tip, I will show an option in SSMS 2008 to easily identify each instance.&lt;img src="http://feeds.feedburner.com/~r/MSSQLTips-LatestSqlServerTips/~4/DTbwYAXD3Zk" height="1" width="1"/&gt;</description>
<link>http://feedproxy.google.com/~r/MSSQLTips-LatestSqlServerTips/~3/DTbwYAXD3Zk/tip.asp</link>
<pubDate>Mon, 2 Nov 2009 08:00:00 GMT</pubDate>
<feedburner:origLink>http://www.mssqltips.com/tip.asp?tip=1871</feedburner:origLink></item>
</channel></rss>
