<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://sqlserver-qa.net/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>SQL Server Security, Performance &amp; Tuning (SSQA.net)</title><link>http://sqlserver-qa.net/blogs/perftune/default.aspx</link><description>SQL Server - Optimization, Index Tuning, problem with slow queries, data normalization and know here how to attain the performance with the available tips &amp; features. Also considering the importance of Security that can help to achieve performance with peace of mind.</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.2)</generator><item><title>CLR Stored Procedures - handling security on SQL Server side</title><link>http://sqlserver-qa.net/blogs/perftune/archive/2008/07/24/4655.aspx</link><pubDate>Thu, 24 Jul 2008 08:52:00 GMT</pubDate><guid isPermaLink="false">e5229e21-c1bf-42d8-be15-8e3c8579d3f0:4655</guid><dc:creator>SQL Master</dc:creator><slash:comments>2</slash:comments><comments>http://sqlserver-qa.net/blogs/perftune/comments/4655.aspx</comments><wfw:commentRss>http://sqlserver-qa.net/blogs/perftune/commentrss.aspx?PostID=4655</wfw:commentRss><description>Ok this is not new to say you can write stored procedures in any language to manage them in SQL Server, as 2005 version has started this CLR integration functionality that is exposed in an assembly called system.data.dll, which is part of the .NET Framework....(&lt;a href="http://sqlserver-qa.net/blogs/perftune/archive/2008/07/24/4655.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlserver-qa.net/aggbug.aspx?PostID=4655" width="1" height="1"&gt;</description><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/sql+server/default.aspx">sql server</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/security/default.aspx">security</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/.net/default.aspx">.net</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/code/default.aspx">code</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/peverify/default.aspx">peverify</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/practices/default.aspx">practices</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/clr/default.aspx">clr</category></item><item><title>Microsoft Security Bulletin Summary for July 2008 - what is it now?</title><link>http://sqlserver-qa.net/blogs/perftune/archive/2008/07/09/4566.aspx</link><pubDate>Wed, 09 Jul 2008 08:07:00 GMT</pubDate><guid isPermaLink="false">e5229e21-c1bf-42d8-be15-8e3c8579d3f0:4566</guid><dc:creator>SQL Master</dc:creator><slash:comments>2</slash:comments><comments>http://sqlserver-qa.net/blogs/perftune/comments/4566.aspx</comments><wfw:commentRss>http://sqlserver-qa.net/blogs/perftune/commentrss.aspx?PostID=4566</wfw:commentRss><description>I believe it has been a while that we have seen the security hotfix from Microsoft Security team on SQL Server (alone). The latest security bulletin has announced important security patches that are related to SQL Server in addition to Windows operating...(&lt;a href="http://sqlserver-qa.net/blogs/perftune/archive/2008/07/09/4566.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlserver-qa.net/aggbug.aspx?PostID=4566" width="1" height="1"&gt;</description><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/sql+server/default.aspx">sql server</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/security/default.aspx">security</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/hotfix/default.aspx">hotfix</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/best+practice/default.aspx">best practice</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/service+pack/default.aspx">service pack</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/guidance/default.aspx">guidance</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/vulnerability/default.aspx">vulnerability</category></item><item><title>SQL Server: PERFMON counters  to identify server utilization data</title><link>http://sqlserver-qa.net/blogs/perftune/archive/2008/06/18/4482.aspx</link><pubDate>Wed, 18 Jun 2008 12:21:00 GMT</pubDate><guid isPermaLink="false">e5229e21-c1bf-42d8-be15-8e3c8579d3f0:4482</guid><dc:creator>satyaskj</dc:creator><slash:comments>2</slash:comments><comments>http://sqlserver-qa.net/blogs/perftune/comments/4482.aspx</comments><wfw:commentRss>http://sqlserver-qa.net/blogs/perftune/commentrss.aspx?PostID=4482</wfw:commentRss><description>Recently I have been involved to carry over an assesment of server utilization on the SQL estate farm (nearly 150+) instances, as it stands it is not an easy job to obtain the results when you have no influence on accessing required information on a shared...(&lt;a href="http://sqlserver-qa.net/blogs/perftune/archive/2008/06/18/4482.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlserver-qa.net/aggbug.aspx?PostID=4482" width="1" height="1"&gt;</description><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/sql+server/default.aspx">sql server</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/perfmon/default.aspx">perfmon</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/sysmon/default.aspx">sysmon</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/tools/default.aspx">tools</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/utilization/default.aspx">utilization</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/counters/default.aspx">counters</category></item><item><title>SQL Server - Precision Performance techniques using RML Utilities</title><link>http://sqlserver-qa.net/blogs/perftune/archive/2008/06/09/4427.aspx</link><pubDate>Mon, 09 Jun 2008 12:50:00 GMT</pubDate><guid isPermaLink="false">e5229e21-c1bf-42d8-be15-8e3c8579d3f0:4427</guid><dc:creator>SQL Master</dc:creator><slash:comments>2</slash:comments><comments>http://sqlserver-qa.net/blogs/perftune/comments/4427.aspx</comments><wfw:commentRss>http://sqlserver-qa.net/blogs/perftune/commentrss.aspx?PostID=4427</wfw:commentRss><description>As a DBA, you probably often find yourself striving or struggling to improve the performance of SQL Server instance queries (might be smaller or complex ones). By default in order to get further analysis on the system's performance you need to perform...(&lt;a href="http://sqlserver-qa.net/blogs/perftune/archive/2008/06/09/4427.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlserver-qa.net/aggbug.aspx?PostID=4427" width="1" height="1"&gt;</description><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/performance/default.aspx">performance</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/sql+server/default.aspx">sql server</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/dmv/default.aspx">dmv</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/sqldiag/default.aspx">sqldiag</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/performance+monitoring/default.aspx">performance monitoring</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/pssdiag/default.aspx">pssdiag</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/rml/default.aspx">rml</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/sqlnexus/default.aspx">sqlnexus</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/utilities/default.aspx">utilities</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/sqlcat/default.aspx">sqlcat</category></item><item><title>SQL Injection attacks - don't forget to visit guidance information from Microsoft</title><link>http://sqlserver-qa.net/blogs/perftune/archive/2008/05/31/4374.aspx</link><pubDate>Sat, 31 May 2008 20:59:00 GMT</pubDate><guid isPermaLink="false">e5229e21-c1bf-42d8-be15-8e3c8579d3f0:4374</guid><dc:creator>SQL Master</dc:creator><slash:comments>2</slash:comments><comments>http://sqlserver-qa.net/blogs/perftune/comments/4374.aspx</comments><wfw:commentRss>http://sqlserver-qa.net/blogs/perftune/commentrss.aspx?PostID=4374</wfw:commentRss><description>One of the biggest threats in IT industry &amp;amp; Database world is unprecedented attacks aka most commonly termed as 'SQL injection'. There is no doubt that biggest database vendors, one of them as Microsoft so far providing recommendations regarding security-related...(&lt;a href="http://sqlserver-qa.net/blogs/perftune/archive/2008/05/31/4374.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlserver-qa.net/aggbug.aspx?PostID=4374" width="1" height="1"&gt;</description><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/sql+server/default.aspx">sql server</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/security/default.aspx">security</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/authentication/default.aspx">authentication</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/best+practice/default.aspx">best practice</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/blogs/default.aspx">blogs</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/injection/default.aspx">injection</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/reference/default.aspx">reference</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/attacks/default.aspx">attacks</category></item><item><title>SQL Server 2005 Connectivity, Security policies &amp; Network protocols: simple practice to follow, after installation?</title><link>http://sqlserver-qa.net/blogs/perftune/archive/2008/05/23/4155.aspx</link><pubDate>Fri, 23 May 2008 08:44:00 GMT</pubDate><guid isPermaLink="false">e5229e21-c1bf-42d8-be15-8e3c8579d3f0:4155</guid><dc:creator>SQL Master</dc:creator><slash:comments>2</slash:comments><comments>http://sqlserver-qa.net/blogs/perftune/comments/4155.aspx</comments><wfw:commentRss>http://sqlserver-qa.net/blogs/perftune/commentrss.aspx?PostID=4155</wfw:commentRss><description>Secured by default, secured by design is the buzzword and catchy stuff for any Enterprise IT administrators. Then it comes about standards and policies to follow such as ISO , with the recent threats (last 10 years) and vulnerabilities within IT world...(&lt;a href="http://sqlserver-qa.net/blogs/perftune/archive/2008/05/23/4155.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlserver-qa.net/aggbug.aspx?PostID=4155" width="1" height="1"&gt;</description><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/sql+server/default.aspx">sql server</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/security/default.aspx">security</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/blocking/default.aspx">blocking</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/hotfix/default.aspx">hotfix</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/service+pack/default.aspx">service pack</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/best+practices/default.aspx">best practices</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/cumulative+update/default.aspx">cumulative update</category></item><item><title>SQL Server Performance issues with Fragmentation and heavy usage of TEMPDB?</title><link>http://sqlserver-qa.net/blogs/perftune/archive/2008/05/15/4240.aspx</link><pubDate>Thu, 15 May 2008 08:59:00 GMT</pubDate><guid isPermaLink="false">e5229e21-c1bf-42d8-be15-8e3c8579d3f0:4240</guid><dc:creator>SQL Master</dc:creator><slash:comments>2</slash:comments><comments>http://sqlserver-qa.net/blogs/perftune/comments/4240.aspx</comments><wfw:commentRss>http://sqlserver-qa.net/blogs/perftune/commentrss.aspx?PostID=4240</wfw:commentRss><description>Whenever a performance issue occurs on the SQL Server database best option for diagnosing and troubleshooting common problems by using publicly available tools such as Profiler, System Monitor (Perfmon), and Dynamic Management Views (DMVs) in SQL Server...(&lt;a href="http://sqlserver-qa.net/blogs/perftune/archive/2008/05/15/4240.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlserver-qa.net/aggbug.aspx?PostID=4240" width="1" height="1"&gt;</description><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/performance/default.aspx">performance</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/sql+server/default.aspx">sql server</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/dmv/default.aspx">dmv</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/tempdb/default.aspx">tempdb</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/monitoring/default.aspx">monitoring</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/performance+monitoring/default.aspx">performance monitoring</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/benchmarking/default.aspx">benchmarking</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/best+practices/default.aspx">best practices</category></item><item><title>SQL Server - Kill a KILLED/ROLLBACK status process without restarting Server or SQL services?</title><link>http://sqlserver-qa.net/blogs/perftune/archive/2008/05/06/4120.aspx</link><pubDate>Tue, 06 May 2008 08:02:00 GMT</pubDate><guid isPermaLink="false">e5229e21-c1bf-42d8-be15-8e3c8579d3f0:4120</guid><dc:creator>SQL Master</dc:creator><slash:comments>2</slash:comments><comments>http://sqlserver-qa.net/blogs/perftune/comments/4120.aspx</comments><wfw:commentRss>http://sqlserver-qa.net/blogs/perftune/commentrss.aspx?PostID=4120</wfw:commentRss><description>This may be the typical situation within your database environment where the you might have killed a SPID (Process) that has been running for long time, without knowing the ROLLBACK operations for such processes. Say if you are executing a stored procedure...(&lt;a href="http://sqlserver-qa.net/blogs/perftune/archive/2008/05/06/4120.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlserver-qa.net/aggbug.aspx?PostID=4120" width="1" height="1"&gt;</description><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/sql+server/default.aspx">sql server</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/spid/default.aspx">spid</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/transactions/default.aspx">transactions</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/transaction+log/default.aspx">transaction log</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/processes/default.aspx">processes</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/kill/default.aspx">kill</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/rollback/default.aspx">rollback</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/sysprocesses/default.aspx">sysprocesses</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/kpid/default.aspx">kpid</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/sp_5F00_who2/default.aspx">sp_who2</category></item><item><title>SQL Server 2005 Login Security - CHECK_POLICY and CHECK_EXPIRATION setting, how it affects the password policy?</title><link>http://sqlserver-qa.net/blogs/perftune/archive/2008/04/30/4133.aspx</link><pubDate>Wed, 30 Apr 2008 08:53:00 GMT</pubDate><guid isPermaLink="false">e5229e21-c1bf-42d8-be15-8e3c8579d3f0:4133</guid><dc:creator>SQL Master</dc:creator><slash:comments>2</slash:comments><comments>http://sqlserver-qa.net/blogs/perftune/comments/4133.aspx</comments><wfw:commentRss>http://sqlserver-qa.net/blogs/perftune/commentrss.aspx?PostID=4133</wfw:commentRss><description>Adding password complexity and password expiration to SQL Server logins is one of best feature I quote for SQL Server version 2005 onwards, similarly such password complexity policies are designed to deter brute force attacks by increasing the number...(&lt;a href="http://sqlserver-qa.net/blogs/perftune/archive/2008/04/30/4133.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlserver-qa.net/aggbug.aspx?PostID=4133" width="1" height="1"&gt;</description><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/sql+server/default.aspx">sql server</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/microsoft/default.aspx">microsoft</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/security/default.aspx">security</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/best+practice/default.aspx">best practice</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/settings/default.aspx">settings</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/logins/default.aspx">logins</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/password/default.aspx">password</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/check_5F00_expiration/default.aspx">check_expiration</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/check_5F00_policy/default.aspx">check_policy</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/computing/default.aspx">computing</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/policies/default.aspx">policies</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/trustworthy/default.aspx">trustworthy</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/feature/default.aspx">feature</category></item><item><title>SQL Server - Have you observed DBCC SHRINKFILE operation performance, on huge databases?</title><link>http://sqlserver-qa.net/blogs/perftune/archive/2008/04/25/4112.aspx</link><pubDate>Fri, 25 Apr 2008 08:30:00 GMT</pubDate><guid isPermaLink="false">e5229e21-c1bf-42d8-be15-8e3c8579d3f0:4112</guid><dc:creator>SQL Master</dc:creator><slash:comments>2</slash:comments><comments>http://sqlserver-qa.net/blogs/perftune/comments/4112.aspx</comments><wfw:commentRss>http://sqlserver-qa.net/blogs/perftune/commentrss.aspx?PostID=4112</wfw:commentRss><description>In general it is not a best practice to perform SHRINK database operation on a production server, atleast regularly! Sometimes it may be compulsory to keep them sized in order to ensure the disk storage is not compromised for any sudden changes to databases...(&lt;a href="http://sqlserver-qa.net/blogs/perftune/archive/2008/04/25/4112.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlserver-qa.net/aggbug.aspx?PostID=4112" width="1" height="1"&gt;</description><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/sql+server/default.aspx">sql server</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/cache/default.aspx">cache</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/memory/default.aspx">memory</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/indexes/default.aspx">indexes</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/databases/default.aspx">databases</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/cpu/default.aspx">cpu</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/monitoring/default.aspx">monitoring</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/operating+system/default.aspx">operating system</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/huge/default.aspx">huge</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/dbcc+shrinkfile/default.aspx">dbcc shrinkfile</category></item><item><title>SQL Server latch waits - index contention &amp; performance issues how DMVs can help you to get information?</title><link>http://sqlserver-qa.net/blogs/perftune/archive/2008/04/17/4032.aspx</link><pubDate>Thu, 17 Apr 2008 10:06:00 GMT</pubDate><guid isPermaLink="false">e5229e21-c1bf-42d8-be15-8e3c8579d3f0:4032</guid><dc:creator>SQL Master</dc:creator><slash:comments>2</slash:comments><comments>http://sqlserver-qa.net/blogs/perftune/comments/4032.aspx</comments><wfw:commentRss>http://sqlserver-qa.net/blogs/perftune/commentrss.aspx?PostID=4032</wfw:commentRss><description>What kind of performance issues you see on day-to-day basis within your environment? The following elements are important factors that can add fuel to the fire (problem): Faulty hardware • Hardware that is not configured correctly • Firmware settings...(&lt;a href="http://sqlserver-qa.net/blogs/perftune/archive/2008/04/17/4032.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlserver-qa.net/aggbug.aspx?PostID=4032" width="1" height="1"&gt;</description><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/sql+server/default.aspx">sql server</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/memory/default.aspx">memory</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/disk/default.aspx">disk</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/IO/default.aspx">IO</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/analysis/default.aspx">analysis</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/monitoring/default.aspx">monitoring</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/iometer/default.aspx">iometer</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/configuration/default.aspx">configuration</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/contention/default.aspx">contention</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/latching/default.aspx">latching</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/latches/default.aspx">latches</category></item><item><title>SQL Server problem: Excessive paging and memory bottlenecks</title><link>http://sqlserver-qa.net/blogs/perftune/archive/2008/04/16/3922.aspx</link><pubDate>Wed, 16 Apr 2008 07:02:00 GMT</pubDate><guid isPermaLink="false">e5229e21-c1bf-42d8-be15-8e3c8579d3f0:3922</guid><dc:creator>SQL Master</dc:creator><slash:comments>2</slash:comments><comments>http://sqlserver-qa.net/blogs/perftune/comments/3922.aspx</comments><wfw:commentRss>http://sqlserver-qa.net/blogs/perftune/commentrss.aspx?PostID=3922</wfw:commentRss><description>Paging and Memory bottlenecks are quite common when a performance problem strikes on your SQL Server. As we discussed here previously and relevant blog posts below talks about them: Paging and Available Memory for Operating sysem, what you need to know?...(&lt;a href="http://sqlserver-qa.net/blogs/perftune/archive/2008/04/16/3922.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlserver-qa.net/aggbug.aspx?PostID=3922" width="1" height="1"&gt;</description><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/sql+server/default.aspx">sql server</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/memory/default.aspx">memory</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/audit/default.aspx">audit</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/pagesize/default.aspx">pagesize</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/logical+disk/default.aspx">logical disk</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/paging/default.aspx">paging</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/bottlenecks/default.aspx">bottlenecks</category></item><item><title>SQL Server 2005 Scalability and Performance - recommended limit on number of instances on a clustered environment?</title><link>http://sqlserver-qa.net/blogs/perftune/archive/2008/04/04/3961.aspx</link><pubDate>Fri, 04 Apr 2008 09:48:00 GMT</pubDate><guid isPermaLink="false">e5229e21-c1bf-42d8-be15-8e3c8579d3f0:3961</guid><dc:creator>SQL Master</dc:creator><slash:comments>3</slash:comments><comments>http://sqlserver-qa.net/blogs/perftune/comments/3961.aspx</comments><wfw:commentRss>http://sqlserver-qa.net/blogs/perftune/commentrss.aspx?PostID=3961</wfw:commentRss><description>This is a very tricky question and hard to stick to 1 or few solutions as answer, it depends! Overall the say is if there isn’t any resource contention (from your pre-installation testing &amp;amp; analysis) and there is enough of each resource to go around,...(&lt;a href="http://sqlserver-qa.net/blogs/perftune/archive/2008/04/04/3961.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlserver-qa.net/aggbug.aspx?PostID=3961" width="1" height="1"&gt;</description><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/sql+server/default.aspx">sql server</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/memory/default.aspx">memory</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/clustered/default.aspx">clustered</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/i_2F00_o/default.aspx">i/o</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/best+practice/default.aspx">best practice</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/resources/default.aspx">resources</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/monitoring/default.aspx">monitoring</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/maintenance+plan/default.aspx">maintenance plan</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/performance+monitoring/default.aspx">performance monitoring</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/configuration/default.aspx">configuration</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/contention/default.aspx">contention</category></item><item><title>SQL Server Memory - what's your method on Configuration and Troubleshooting Issues</title><link>http://sqlserver-qa.net/blogs/perftune/archive/2008/04/01/3733.aspx</link><pubDate>Tue, 01 Apr 2008 09:49:00 GMT</pubDate><guid isPermaLink="false">e5229e21-c1bf-42d8-be15-8e3c8579d3f0:3733</guid><dc:creator>SQL Master</dc:creator><slash:comments>5</slash:comments><comments>http://sqlserver-qa.net/blogs/perftune/comments/3733.aspx</comments><wfw:commentRss>http://sqlserver-qa.net/blogs/perftune/commentrss.aspx?PostID=3733</wfw:commentRss><description>Memory - an important aspect of system performance within a RDBMS platform, not specific to a database product or application. Coming to Microsoft related products such as Windows Server and SQL Server so on, various resources available on web such as...(&lt;a href="http://sqlserver-qa.net/blogs/perftune/archive/2008/04/01/3733.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlserver-qa.net/aggbug.aspx?PostID=3733" width="1" height="1"&gt;</description><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/performance/default.aspx">performance</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/sql+server/default.aspx">sql server</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/cache/default.aspx">cache</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/memory/default.aspx">memory</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/troubleshoot/default.aspx">troubleshoot</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/raid/default.aspx">raid</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/hardware/default.aspx">hardware</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/best+practice/default.aspx">best practice</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/disk+space/default.aspx">disk space</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/monitoring/default.aspx">monitoring</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/system/default.aspx">system</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/baseline/default.aspx">baseline</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/configuration/default.aspx">configuration</category></item><item><title>What's your practice on Disk Defragmentation methods - specific to data file and indexes drives?</title><link>http://sqlserver-qa.net/blogs/perftune/archive/2008/03/26/3722.aspx</link><pubDate>Wed, 26 Mar 2008 08:01:00 GMT</pubDate><guid isPermaLink="false">e5229e21-c1bf-42d8-be15-8e3c8579d3f0:3722</guid><dc:creator>SQL Master</dc:creator><slash:comments>5</slash:comments><comments>http://sqlserver-qa.net/blogs/perftune/comments/3722.aspx</comments><wfw:commentRss>http://sqlserver-qa.net/blogs/perftune/commentrss.aspx?PostID=3722</wfw:commentRss><description>Fragmentation is dearest friend of database when you need to deal with Performance, so by using the DBCC statements and other methods here you can deal the database level fragmentation, what about the physical level fragmentation? So what is the best...(&lt;a href="http://sqlserver-qa.net/blogs/perftune/archive/2008/03/26/3722.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlserver-qa.net/aggbug.aspx?PostID=3722" width="1" height="1"&gt;</description><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/performance/default.aspx">performance</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/sql+server/default.aspx">sql server</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/dbcc/default.aspx">dbcc</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/object/default.aspx">object</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/best+practice/default.aspx">best practice</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/defrag/default.aspx">defrag</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/showcontig/default.aspx">showcontig</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/blogs/default.aspx">blogs</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/disk+space/default.aspx">disk space</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/monitoring/default.aspx">monitoring</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/diskkeeper/default.aspx">diskkeeper</category><category domain="http://sqlserver-qa.net/blogs/perftune/archive/tags/file/default.aspx">file</category></item></channel></rss>