<?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.sqlfeeds.com/~d/styles/itemcontent.css"?><rss xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">
			<channel>
				<title>SQL Feeds</title>
				<link>http://sqlfeeds.com</link>
				<description>SQL Feeds - All your SQL feeds in one place.</description>
	
			<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.sqlfeeds.com/SqlFeeds" /><feedburner:info uri="sqlfeeds" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><item>
				<title>SQL Server 2008 R2 UNICODE Compression – what happens in the background?</title>
				<description>SQL Server 2008 R2 added a much requested feature: Unicode compression. It addresses the need to compress Unicode strings. It is implemented as part of ROW compression, which was added in SQL 2008. That is; if ROW compression (on SQL 2008 R2) is enabled on a table that contains NCHAR / NVARCHAR datatypes, then the Unicode compression algorithm will kick in for each individual Unicode column.
Note: since PAGE compression is a ‘superset’, which also includes ROW compression, it will also enable Un&lt;img src="http://feeds.feedburner.com/~r/SqlFeeds/~4/VR8I3TlddUQ" height="1" width="1"/&gt;</description>
				<link>http://feeds.sqlfeeds.com/~r/SqlFeeds/~3/VR8I3TlddUQ/sql-server-2008-r2-unicode-compression-what-happens-in-the-background.aspx</link>
				<author>Peter Scharlock</author>
				<pubDate>Wed, 03 Mar 2010 00:06:00 GMT</pubDate>
			<feedburner:origLink>http://blogs.msdn.com/sqlcat/archive/2010/03/03/sql-server-2008-r2-unicode-compression-what-happens-in-the-background.aspx</feedburner:origLink></item>
	
			<item>
				<title>Performance tips of using XML data in SQL Server</title>
				<description>Author: Kun ChengReviewers: Peter Carlin, Mike Ruthruff, Thomas Kejser, Nicholas Dritsas
XML data type is usually used to store semi-structured data with great flexibility and query capabilities. It’s a good choice for developing platform agnostic applications to separate storage of complex data from processing at application layer, which understands the complex data relationship. To achieve optimal performance of querying XML data in SQL Server, extra steps need to be taken to ensure query acc&lt;img src="http://feeds.feedburner.com/~r/SqlFeeds/~4/LyOZxj-hKjI" height="1" width="1"/&gt;</description>
				<link>http://feeds.sqlfeeds.com/~r/SqlFeeds/~3/LyOZxj-hKjI/performance-tips-of-using-xml-data-in-sql-server.aspx</link>
				<author>Kun Cheng</author>
				<pubDate>Mon, 01 Mar 2010 23:52:00 GMT</pubDate>
			<feedburner:origLink>http://blogs.msdn.com/sqlcat/archive/2010/03/01/performance-tips-of-using-xml-data-in-sql-server.aspx</feedburner:origLink></item>
	
			<item>
				<title>Full Text Indexing Terabytes of Files with SQL Server and Cloud Storage</title>
				<description>Author: Darko Sancanin, Nicholas Dritsas
Reviewers and contributors: Lubor Kollar, Stuart Ozer, Michael Thomassy
&amp;nbsp;Business Case
There are currently over 50 million files (over 10 Terabytes of data) that the customer is migrating into a custom project management application (for international customers) that can be accessed via the application and can be searched upon.&amp;nbsp; SQL Server 2008 full text indexing is used to index the content of these files which gives them rich searching capabi&lt;img src="http://feeds.feedburner.com/~r/SqlFeeds/~4/QGa6KUc-Zzs" height="1" width="1"/&gt;</description>
				<link>http://feeds.sqlfeeds.com/~r/SqlFeeds/~3/QGa6KUc-Zzs/full-text-indexing-terabytes-of-files-with-sql-server-and-cloud-storage.aspx</link>
				<author>Nicholas Dritsas</author>
				<pubDate>Wed, 03 Feb 2010 02:52:00 GMT</pubDate>
			<feedburner:origLink>http://blogs.msdn.com/sqlcat/archive/2010/02/03/full-text-indexing-terabytes-of-files-with-sql-server-and-cloud-storage.aspx</feedburner:origLink></item>
	
			<item>
				<title>SQL Saturday #35 - Dallas</title>
				<description>I had intended to post this weeks ago.&amp;nbsp; I guess I'm still postponing my New Year's resolution to stop procrastinating. 
We're organizing our first SQL Saturday event in Dallas on May 22nd, hoping to make it an annual event.&amp;nbsp; It will be held at the Region 10 Education Center in Richardson, and we currently have 4 tracks slated:&amp;nbsp; Development, Administration, Business Intelligence and Beginner.&amp;nbsp; I'm particularly excited about the Beginner track since we so rarely find those at t&lt;img src="http://feeds.feedburner.com/~r/SqlFeeds/~4/5-QIQ2jw92o" height="1" width="1"/&gt;</description>
				<link>http://feeds.sqlfeeds.com/~r/SqlFeeds/~3/5-QIQ2jw92o/sql-saturday-35-dallas.aspx</link>
				<author>ErinW</author>
				<pubDate>Sun, 17 Jan 2010 18:09:00 GMT</pubDate>
			<feedburner:origLink>http://sqlblog.com/blogs/erin_welker/archive/2010/01/17/sql-saturday-35-dallas.aspx</feedburner:origLink></item>
	
			<item>
				<title>Monitoring free space in tempdb transaction log</title>
				<description>Author: Thomas Kejser     Reviewers: Peter Byrne, Sunil Agarwal, Prem Mehra, Peter Scharlock, Lindsey Allen, Mark Souza  As part of your database monitoring, you may be keeping track of the free space in the transaction log. One reason to do this, is to detect a rogue query consuming too much transaction log space. If you have such monitoring set up, you need to be a bit careful about tempdb.  Recall that unused space in the transaction log in a FULL and BULK LOGGED recovery mode database is rec&lt;img src="http://feeds.feedburner.com/~r/SqlFeeds/~4/rQyDUvs-P_I" height="1" width="1"/&gt;</description>
				<link>http://feeds.sqlfeeds.com/~r/SqlFeeds/~3/rQyDUvs-P_I/monitoring-free-space-in-tempdb-transaction-log.aspx</link>
				<author>tkejser</author>
				<pubDate>Mon, 14 Dec 2009 13:58:36 GMT</pubDate>
			<feedburner:origLink>http://blogs.msdn.com/sqlcat/archive/2009/12/14/monitoring-free-space-in-tempdb-transaction-log.aspx</feedburner:origLink></item>
	
			<item>
				<title>Performance Comparison between Data Type Conversion Techniques in SSIS 2008</title>
				<description>Authors: Sedat Yogurtcuoglu and Thomas Kejser               Technical Reviewers: Kevin Cox, Denny Lee, Carl Rabeler, Dana Kaufman, Jesse Fountain, Alexei Khalyako, Dana Kaufman          Overview          Data type conversion is one of the most common ETL tasks used in Microsoft® SQL Server® Integration Services packages. There are several ways to perform these conversions: you can use a Data Conversion transformation or a Derived Column transformation, or you can perform the conversion on the&lt;img src="http://feeds.feedburner.com/~r/SqlFeeds/~4/dAZT4NtOrH0" height="1" width="1"/&gt;</description>
				<link>http://feeds.sqlfeeds.com/~r/SqlFeeds/~3/dAZT4NtOrH0/draft-performance-comparison-between-data-type-conversion-techniques-in-ssis-2008.aspx</link>
				<author>tkejser</author>
				<pubDate>Tue, 01 Dec 2009 13:59:00 GMT</pubDate>
			<feedburner:origLink>http://blogs.msdn.com/sqlcat/archive/2009/12/01/draft-performance-comparison-between-data-type-conversion-techniques-in-ssis-2008.aspx</feedburner:origLink></item>
	
			<item>
				<title>New TPC Results on SQL Server 2008 R2</title>
				<description>On November 2, 2009, Unisys published two new TPC results (TPC-E and TPC-H) using the newly announced SQL Server 2008 R2* and Windows Server 2008 R2**.&amp;#160; These results were published on the 96-core Unisys ES7000 system.&amp;#160; These are the first SQL Server TPC results using more than 64 cores and they demonstrate the outstanding scalability of the Windows and SQL Server platform.&amp;#160;   The TPC-E publication was 2,012 tpsE with a price performance of $958.23 USD/tpsE.&amp;#160; The configuratio&lt;img src="http://feeds.feedburner.com/~r/SqlFeeds/~4/YUlLMTjT4UU" height="1" width="1"/&gt;</description>
				<link>http://feeds.sqlfeeds.com/~r/SqlFeeds/~3/YUlLMTjT4UU/new-tpc-results-on-sql-server-2008-r2.aspx</link>
				<author>Data &amp; SQL Storage Performance Team</author>
				<pubDate>Mon, 30 Nov 2009 19:31:55 GMT</pubDate>
			<feedburner:origLink>http://blogs.msdn.com/sqlperf/archive/2009/11/30/new-tpc-results-on-sql-server-2008-r2.aspx</feedburner:origLink></item>
	
			<item>
				<title>Automating UBO</title>
				<description>I was preparing for my presentation at PASS and wanted to show some code for automating usage-based optimization.&amp;#160; This is the process that allows for creating aggregation designs based on past query activity.&amp;#160; I was surprised to find that there were no code examples posted on the web on how to do this, at least none that I could find.&amp;#160; BIDSHelper and AggManager have similar functionality but, upon examining the code, they both use a more manual approach of examining each Dataset&lt;img src="http://feeds.feedburner.com/~r/SqlFeeds/~4/bGQV3v3YgyM" height="1" width="1"/&gt;</description>
				<link>http://feeds.sqlfeeds.com/~r/SqlFeeds/~3/bGQV3v3YgyM/automating-ubo.aspx</link>
				<author>ErinW</author>
				<pubDate>Sun, 15 Nov 2009 16:14:15 GMT</pubDate>
			<feedburner:origLink>http://sqlblog.com/blogs/erin_welker/archive/2009/11/15/automating-ubo.aspx</feedburner:origLink></item>
	
			<item>
				<title>How to View Currently Executing Queries in SQL Server</title>
				<description>Here&amp;#8217;s a quick TSQL query to find the &amp;#8220;currently executing queries&amp;#8221; and the database name:

SELECT db.name,
er.session_id,
er.transaction_id,
er.start_time,
er.[status],
er.command,
er.wait_time
&amp;#8211; etc.
FROM sys.dm_exec_requests AS er
JOIN sys.sysdatabases AS db
ON er.database_id = db.dbid
WHERE er.status = &amp;#8216;running&amp;#8217;
Here&amp;#8217;s the query in action:




 Tagged: active queries, active query, active sessions, running queries, sql server 2008, sql server running&lt;img src="http://feeds.feedburner.com/~r/SqlFeeds/~4/VXUnyNKXZi4" height="1" width="1"/&gt;</description>
				<link>http://feeds.sqlfeeds.com/~r/SqlFeeds/~3/VXUnyNKXZi4/</link>
				<author>MarlonRibunal</author>
				<pubDate>Thu, 12 Nov 2009 20:14:38 GMT</pubDate>
			<feedburner:origLink>http://feedproxy.google.com/~r/DanglingOnTheShouldersOfGiants/~3/KKHuE-O9GSY/</feedburner:origLink></item>
	
			<item>
				<title>Selectively using secure connection to SQL Server</title>
				<description>Secure connection to SQL Server can be enforced by different ways, e.g. forcing encryption by using “ForceEncryption” property under the Network Configuration in the server. But this setting will force all clients to use encryption and any client that is not able to use an encrypted connection will fail.
If you need to connect to SQL Server selectively here is how to achieve this:
You can take advantage of the two client settings, “Force Protocol Encryption” and “Trust Server Certificate” and tw&lt;img src="http://feeds.feedburner.com/~r/SqlFeeds/~4/MgeQLrO1FE8" height="1" width="1"/&gt;</description>
				<link>http://feeds.sqlfeeds.com/~r/SqlFeeds/~3/MgeQLrO1FE8/selectively-using-secure-connection-to-sql-server.aspx</link>
				<author>SQL Protocols</author>
				<pubDate>Mon, 19 Oct 2009 21:48:00 GMT</pubDate>
			<feedburner:origLink>http://blogs.msdn.com/sql_protocols/archive/2009/10/19/selectively-using-secure-connection-to-sql-server.aspx</feedburner:origLink></item>
	
			</channel>
		</rss>
