<?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>SQL Server Performance &#187; satnam singh</title>
	<atom:link href="http://www.sql-server-performance.com/author/satnamsingh/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sql-server-performance.com</link>
	<description>SQL Server Performance Tuning</description>
	<lastBuildDate>Wed, 15 May 2013 08:10:41 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>Transactional Replication – Unable to Replicate Data onto the Subscriber  &#8211;  A Practical Example</title>
		<link>http://www.sql-server-performance.com/2013/transactional-replication-unable-to-replicate-data-onto-the-subscriber/</link>
		<comments>http://www.sql-server-performance.com/2013/transactional-replication-unable-to-replicate-data-onto-the-subscriber/#comments</comments>
		<pubDate>Mon, 04 Mar 2013 10:55:17 +0000</pubDate>
		<dc:creator>satnam singh</dc:creator>
				<category><![CDATA[General DBA]]></category>
		<category><![CDATA[Reporting]]></category>
		<category><![CDATA[Replication]]></category>
		<category><![CDATA[SSRS]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=2906</guid>
		<description><![CDATA[Scenario: A couple of days back, I got a call from one of my users saying that the Data is not being replicated properly onto the Production Reporting Server from the Production OLTP server. We have Transactional Replication scheduled for every 15 minutes between our OLTP and the Reporting server. Approach: I started investigating this [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2013/transactional-replication-unable-to-replicate-data-onto-the-subscriber/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>SQL Server Disaster Recovery Test</title>
		<link>http://www.sql-server-performance.com/2013/disaster-recovery-test/</link>
		<comments>http://www.sql-server-performance.com/2013/disaster-recovery-test/#comments</comments>
		<pubDate>Wed, 30 Jan 2013 02:13:55 +0000</pubDate>
		<dc:creator>satnam singh</dc:creator>
				<category><![CDATA[General DBA]]></category>
		<category><![CDATA[Disaster Recovery]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=3558</guid>
		<description><![CDATA[This article describes a simple procedure we implemented to ensure that the data on our the database on the Disaster Recovery server is consistent with the production server. Our DR Server is a separate server which is located in a separate data centre. The DR server receives data from the production database server via Transactional [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2013/disaster-recovery-test/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Introduction to SQL Server Check Constraints</title>
		<link>http://www.sql-server-performance.com/2013/introduction-sql-server-check-constraints/</link>
		<comments>http://www.sql-server-performance.com/2013/introduction-sql-server-check-constraints/#comments</comments>
		<pubDate>Thu, 24 Jan 2013 02:25:18 +0000</pubDate>
		<dc:creator>satnam singh</dc:creator>
				<category><![CDATA[Developer]]></category>
		<category><![CDATA[General DBA]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=3553</guid>
		<description><![CDATA[Check Constraints play a very important role in SQL Server as it allows data validation rules to be imposed at the SQL Server instance level itself instead of writing rules for each application. Check Constraint enforces Domain Integrity by restricting the values that can be inserted into columns. Domain Integrity ensures that only a valid [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2013/introduction-sql-server-check-constraints/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Efficient T-SQL Code – A Case of Incorrect Use of a UNION Operator</title>
		<link>http://www.sql-server-performance.com/2013/tsql-incorrect-union-operator/</link>
		<comments>http://www.sql-server-performance.com/2013/tsql-incorrect-union-operator/#comments</comments>
		<pubDate>Thu, 17 Jan 2013 05:01:52 +0000</pubDate>
		<dc:creator>satnam singh</dc:creator>
				<category><![CDATA[Developer]]></category>
		<category><![CDATA[TSQL]]></category>
		<category><![CDATA[UNION]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=3540</guid>
		<description><![CDATA[A couple of days back, I had a developer complaining me the slow performance of some T-SQL which was causing the application to throw a Timeout Expired error. During Investigation, I noticed that the developer made an incorrect use of a UNION operator which was the culprit. In this article, I will demonstrate the issue [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2013/tsql-incorrect-union-operator/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Understanding SQL Server   Change Data Capture</title>
		<link>http://www.sql-server-performance.com/2013/understanding-sql-server-change-data-capture-cdc/</link>
		<comments>http://www.sql-server-performance.com/2013/understanding-sql-server-change-data-capture-cdc/#comments</comments>
		<pubDate>Tue, 15 Jan 2013 05:02:46 +0000</pubDate>
		<dc:creator>satnam singh</dc:creator>
				<category><![CDATA[General DBA]]></category>
		<category><![CDATA[CDC]]></category>
		<category><![CDATA[Change Data Capture]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=3534</guid>
		<description><![CDATA[DBA&#8217;s often encounter a requirement to audit DML activity such as INSERT/UPDATE/DELETE operations executed against a particular table or a group of tables in a particular database. Change Data Capture (first introduced in SQL Server 2008 R2) can greatly assist this function. Only members of sysadmin fixed server role can enable the Change Data Capture [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2013/understanding-sql-server-change-data-capture-cdc/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Recovering a SQL Server Database from Suspect Mode</title>
		<link>http://www.sql-server-performance.com/2012/recovery-sql-server-suspect-mode/</link>
		<comments>http://www.sql-server-performance.com/2012/recovery-sql-server-suspect-mode/#comments</comments>
		<pubDate>Wed, 19 Dec 2012 00:13:52 +0000</pubDate>
		<dc:creator>satnam singh</dc:creator>
				<category><![CDATA[General DBA]]></category>
		<category><![CDATA[Recovery]]></category>
		<category><![CDATA[suspect mode]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=2891</guid>
		<description><![CDATA[A couple of days back at I got a call from my support team informing me that one of our database located on the Production Server went into Suspect Mode. The version used was SQL Server 2005 Service Pack 3. Being a Production Database server, it was a Priority 1 incident and the expected time [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2012/recovery-sql-server-suspect-mode/feed/</wfw:commentRss>
		<slash:comments>22</slash:comments>
		</item>
		<item>
		<title>VARCHAR (MAX), NVARCHAR (MAX) and NTEXT Data Types</title>
		<link>http://www.sql-server-performance.com/2012/varchar-max-nvarchar-max-ntext-data-types/</link>
		<comments>http://www.sql-server-performance.com/2012/varchar-max-nvarchar-max-ntext-data-types/#comments</comments>
		<pubDate>Wed, 05 Dec 2012 05:15:12 +0000</pubDate>
		<dc:creator>satnam singh</dc:creator>
				<category><![CDATA[Developer]]></category>
		<category><![CDATA[General DBA]]></category>
		<category><![CDATA[Performance Tuning]]></category>
		<category><![CDATA[ntext]]></category>
		<category><![CDATA[nvarchar]]></category>
		<category><![CDATA[text]]></category>
		<category><![CDATA[TSQL]]></category>
		<category><![CDATA[varchar]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=3453</guid>
		<description><![CDATA[Despite NTEXT and TEXT being deprecated in SQL Server for some time they are still both used in production systems. In this article, I will briefly demonstrate the difference between a VARCHAR (MAX), NVARCHAR (MAX) and the NTEXT data types, and the impact on performance from using NTEXT/TEXT. Let’s create a table named Student using [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2012/varchar-max-nvarchar-max-ntext-data-types/feed/</wfw:commentRss>
		<slash:comments>13</slash:comments>
		</item>
		<item>
		<title>Tuning your SQL Query – Generating a Proper Execution Plan.</title>
		<link>http://www.sql-server-performance.com/2012/tuning-sql-query-execution-plan/</link>
		<comments>http://www.sql-server-performance.com/2012/tuning-sql-query-execution-plan/#comments</comments>
		<pubDate>Wed, 14 Nov 2012 05:15:12 +0000</pubDate>
		<dc:creator>satnam singh</dc:creator>
				<category><![CDATA[Developer]]></category>
		<category><![CDATA[General DBA]]></category>
		<category><![CDATA[Performance Tuning]]></category>
		<category><![CDATA[SQL]]></category>
		<category><![CDATA[T-SQL]]></category>
		<category><![CDATA[TSQL]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=3327</guid>
		<description><![CDATA[Recently one of my developers came to and complained of slow performance on a particular query. During the investigation I noticed that the primary cause was the poor query execution plan. In this article, I will discuss the approach which I used to improve the execution plan. For demonstration purpose, I will be creating a [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2012/tuning-sql-query-execution-plan/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Performance Tuning Re-indexing and Update Statistics  – A Case Study</title>
		<link>http://www.sql-server-performance.com/2012/performance-tuning-re-indexing-update-statistics/</link>
		<comments>http://www.sql-server-performance.com/2012/performance-tuning-re-indexing-update-statistics/#comments</comments>
		<pubDate>Wed, 24 Oct 2012 06:20:31 +0000</pubDate>
		<dc:creator>satnam singh</dc:creator>
				<category><![CDATA[General DBA]]></category>
		<category><![CDATA[Performance Tuning]]></category>
		<category><![CDATA[index]]></category>
		<category><![CDATA[re-indexing]]></category>
		<category><![CDATA[Update Statistics]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=3288</guid>
		<description><![CDATA[Recently we started experiencing a very strange issue in our production reporting environment where the Re-indexing and Update Statistics operation suddenly began taking more than 2 days to complete and was thus causing blockage in the database which in turn caused impairment in application performance. Reporting Server Configuration Details: SQL Server Version: SQL Server 2005 [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2012/performance-tuning-re-indexing-update-statistics/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Automating  SQL Server Transactional Log Shipping Alerts</title>
		<link>http://www.sql-server-performance.com/2012/automating-sql-server-transactional-log-shipping-alerts/</link>
		<comments>http://www.sql-server-performance.com/2012/automating-sql-server-transactional-log-shipping-alerts/#comments</comments>
		<pubDate>Tue, 02 Oct 2012 03:40:02 +0000</pubDate>
		<dc:creator>satnam singh</dc:creator>
				<category><![CDATA[General DBA]]></category>
		<category><![CDATA[Alert]]></category>
		<category><![CDATA[Emai]]></category>
		<category><![CDATA[Log Shipping]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=3251</guid>
		<description><![CDATA[DBAs often follow a practice of using the Transactional Log Shipping Monitor in SSMS to ensure that the Log Shipping is running without any issues. However, it is not always possible to do 24/7 monitoring using the Log Shipping monitor. The alert messages generated by third party monitoring systems can be overkill and generate messages [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2012/automating-sql-server-transactional-log-shipping-alerts/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
