<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://sqlserver-qa.net/utility/FeedStylesheets/atom.xsl" media="screen"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en"><title type="html">SQL Server Security, Performance &amp; Tuning (SSQA.net)</title><subtitle type="html">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.</subtitle><id>http://sqlserver-qa.net/blogs/perftune/atom.aspx</id><link rel="alternate" type="text/html" href="http://sqlserver-qa.net/blogs/perftune/default.aspx" /><link rel="self" type="application/atom+xml" href="http://sqlserver-qa.net/blogs/perftune/atom.aspx" /><generator uri="http://communityserver.org" version="2.1.61129.2">Community Server</generator><updated>2008-03-26T01:01:00Z</updated><entry><title>CLR Stored Procedures - handling security on SQL Server side</title><link rel="alternate" type="text/html" href="http://sqlserver-qa.net/blogs/perftune/archive/2008/07/24/4655.aspx" /><id>http://sqlserver-qa.net/blogs/perftune/archive/2008/07/24/4655.aspx</id><published>2008-07-24T08:52:00Z</published><updated>2008-07-24T08:52:00Z</updated><content type="html">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. So think about code access security in addition to managing security privileges for the user on database side. CLR supports the access security mechanism which is based on the assumption that the runtime can host both fully trusted and partially...(&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;</content><author><name>sqlmaster</name><uri>http://sqlserver-qa.net/members/sqlmaster.aspx</uri></author><category term="sql server" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/sql+server/default.aspx" /><category term="security" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/security/default.aspx" /><category term=".net" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/.net/default.aspx" /><category term="code" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/code/default.aspx" /><category term="peverify" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/peverify/default.aspx" /><category term="practices" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/practices/default.aspx" /><category term="clr" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/clr/default.aspx" /></entry><entry><title>Microsoft Security Bulletin Summary for July 2008 - what is it now?</title><link rel="alternate" type="text/html" href="http://sqlserver-qa.net/blogs/perftune/archive/2008/07/09/4566.aspx" /><id>http://sqlserver-qa.net/blogs/perftune/archive/2008/07/09/4566.aspx</id><published>2008-07-09T08:07:00Z</published><updated>2008-07-09T08:07:00Z</updated><content type="html">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 system. They quote that "... With the release of the bulletins for July 2008, this bulletin summary replaces the bulletin advance notification originally issued July 3, 2008. For more information about the bulletin advance notification service, see...(&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;</content><author><name>sqlmaster</name><uri>http://sqlserver-qa.net/members/sqlmaster.aspx</uri></author><category term="sql server" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/sql+server/default.aspx" /><category term="security" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/security/default.aspx" /><category term="hotfix" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/hotfix/default.aspx" /><category term="best practice" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/best+practice/default.aspx" /><category term="service pack" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/service+pack/default.aspx" /><category term="guidance" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/guidance/default.aspx" /><category term="vulnerability" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/vulnerability/default.aspx" /></entry><entry><title>SQL Server: PERFMON counters  to identify server utilization data</title><link rel="alternate" type="text/html" href="http://sqlserver-qa.net/blogs/perftune/archive/2008/06/18/4482.aspx" /><id>http://sqlserver-qa.net/blogs/perftune/archive/2008/06/18/4482.aspx</id><published>2008-06-18T12:21:00Z</published><updated>2008-06-18T12:21:00Z</updated><content type="html">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 platform. So in order to get the results quickly as you might guess using PERFMON *(SYSMON) tool is best to go with for initial assesment. As it defines within the SYSMON tool getting Collection of counter logs with Performance Logs and Alerts...(&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;</content><author><name>satyaskj</name><uri>http://sqlserver-qa.net/members/satyaskj.aspx</uri></author><category term="sql server" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/sql+server/default.aspx" /><category term="perfmon" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/perfmon/default.aspx" /><category term="sysmon" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/sysmon/default.aspx" /><category term="tools" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/tools/default.aspx" /><category term="utilization" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/utilization/default.aspx" /><category term="counters" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/counters/default.aspx" /></entry><entry><title>SQL Server - Precision Performance techniques using RML Utilities</title><link rel="alternate" type="text/html" href="http://sqlserver-qa.net/blogs/perftune/archive/2008/06/09/4427.aspx" /><id>http://sqlserver-qa.net/blogs/perftune/archive/2008/06/09/4427.aspx</id><published>2008-06-09T12:50:00Z</published><updated>2008-06-09T12:50:00Z</updated><content type="html">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 server side trace along with SYSMON (PERFMON) trace collection, this is important in trying to discover the queries or batches that take too long to run, perform too many I/O requests, or use too many CPU cycles. By default the users will find using...(&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;</content><author><name>sqlmaster</name><uri>http://sqlserver-qa.net/members/sqlmaster.aspx</uri></author><category term="rml" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/rml/default.aspx" /><category term="sqlnexus" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/sqlnexus/default.aspx" /><category term="utilities" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/utilities/default.aspx" /><category term="sqlcat" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/sqlcat/default.aspx" /><category term="performance" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/performance/default.aspx" /><category term="sql server" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/sql+server/default.aspx" /><category term="dmv" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/dmv/default.aspx" /><category term="sqldiag" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/sqldiag/default.aspx" /><category term="performance monitoring" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/performance+monitoring/default.aspx" /><category term="pssdiag" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/pssdiag/default.aspx" /></entry><entry><title>SQL Injection attacks - don't forget to visit guidance information from Microsoft</title><link rel="alternate" type="text/html" href="http://sqlserver-qa.net/blogs/perftune/archive/2008/05/31/4374.aspx" /><id>http://sqlserver-qa.net/blogs/perftune/archive/2008/05/31/4374.aspx</id><published>2008-05-31T20:59:00Z</published><updated>2008-05-31T20:59:00Z</updated><content type="html">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 configuration settings since the good &amp;amp; bad times of SQL Server version 2000, not in particular to point DBA or Developer and whole as in Application database, remember ' Slammer Worm '!. Here it is best to refer the ignored 'best'...(&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;</content><author><name>sqlmaster</name><uri>http://sqlserver-qa.net/members/sqlmaster.aspx</uri></author><category term="sql server" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/sql+server/default.aspx" /><category term="security" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/security/default.aspx" /><category term="authentication" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/authentication/default.aspx" /><category term="best practice" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/best+practice/default.aspx" /><category term="blogs" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/blogs/default.aspx" /><category term="injection" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/injection/default.aspx" /><category term="reference" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/reference/default.aspx" /><category term="attacks" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/attacks/default.aspx" /></entry><entry><title>SQL Server 2005 Connectivity, Security policies &amp; Network protocols: simple practice to follow, after installation?</title><link rel="alternate" type="text/html" href="http://sqlserver-qa.net/blogs/perftune/archive/2008/05/23/4155.aspx" /><id>http://sqlserver-qa.net/blogs/perftune/archive/2008/05/23/4155.aspx</id><published>2008-05-23T08:44:00Z</published><updated>2008-05-23T08:44:00Z</updated><content type="html">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 it is most important factor you need to follow as per the compliance standards that are deemed as industry proven, Common Criteria. This 'international' standard has been ratified in the year 1999 that was designed by a group of nations to improve the...(&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;</content><author><name>sqlmaster</name><uri>http://sqlserver-qa.net/members/sqlmaster.aspx</uri></author><category term="sql server" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/sql+server/default.aspx" /><category term="security" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/security/default.aspx" /><category term="blocking" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/blocking/default.aspx" /><category term="hotfix" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/hotfix/default.aspx" /><category term="service pack" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/service+pack/default.aspx" /><category term="best practices" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/best+practices/default.aspx" /><category term="cumulative update" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/cumulative+update/default.aspx" /></entry><entry><title>SQL Server Performance issues with Fragmentation and heavy usage of TEMPDB?</title><link rel="alternate" type="text/html" href="http://sqlserver-qa.net/blogs/perftune/archive/2008/05/15/4240.aspx" /><id>http://sqlserver-qa.net/blogs/perftune/archive/2008/05/15/4240.aspx</id><published>2008-05-15T08:59:00Z</published><updated>2008-05-15T08:59:00Z</updated><content type="html">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 2005 (onwards). What to detect? Use SYSMON to detect excessive compiles and recompiles. Technical documentation refers that for this kind of problem use SQL Statistics object that provides counters to monitor compilation and the type of requests that...(&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;</content><author><name>sqlmaster</name><uri>http://sqlserver-qa.net/members/sqlmaster.aspx</uri></author><category term="performance" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/performance/default.aspx" /><category term="sql server" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/sql+server/default.aspx" /><category term="dmv" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/dmv/default.aspx" /><category term="tempdb" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/tempdb/default.aspx" /><category term="monitoring" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/monitoring/default.aspx" /><category term="performance monitoring" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/performance+monitoring/default.aspx" /><category term="benchmarking" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/benchmarking/default.aspx" /><category term="best practices" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/best+practices/default.aspx" /></entry><entry><title>SQL Server - Kill a KILLED/ROLLBACK status process without restarting Server or SQL services?</title><link rel="alternate" type="text/html" href="http://sqlserver-qa.net/blogs/perftune/archive/2008/05/06/4120.aspx" /><id>http://sqlserver-qa.net/blogs/perftune/archive/2008/05/06/4120.aspx</id><published>2008-05-06T08:02:00Z</published><updated>2008-05-06T08:02:00Z</updated><content type="html">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 which is built with a transactional based statements, by default the relational engine has the ability to control transactions mainly when you have specified a transaction starts and ends. In addition to that it must also be able to correctly handle...(&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;</content><author><name>sqlmaster</name><uri>http://sqlserver-qa.net/members/sqlmaster.aspx</uri></author><category term="sql server" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/sql+server/default.aspx" /><category term="spid" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/spid/default.aspx" /><category term="transactions" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/transactions/default.aspx" /><category term="transaction log" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/transaction+log/default.aspx" /><category term="processes" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/processes/default.aspx" /><category term="kill" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/kill/default.aspx" /><category term="rollback" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/rollback/default.aspx" /><category term="sysprocesses" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/sysprocesses/default.aspx" /><category term="kpid" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/kpid/default.aspx" /><category term="sp_who2" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/sp_5F00_who2/default.aspx" /></entry><entry><title>SQL Server 2005 Login Security - CHECK_POLICY and CHECK_EXPIRATION setting, how it affects the password policy?</title><link rel="alternate" type="text/html" href="http://sqlserver-qa.net/blogs/perftune/archive/2008/04/30/4133.aspx" /><id>http://sqlserver-qa.net/blogs/perftune/archive/2008/04/30/4133.aspx</id><published>2008-04-30T08:53:00Z</published><updated>2008-04-30T08:53:00Z</updated><content type="html">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 of possible passwords. When password complexity policy is enforced and password expiration policies are used to manage the lifespan of a password. In any of the above cases the SQL Server engine runs the check to enforce password expiration policy and...(&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;</content><author><name>sqlmaster</name><uri>http://sqlserver-qa.net/members/sqlmaster.aspx</uri></author><category term="sql server" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/sql+server/default.aspx" /><category term="microsoft" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/microsoft/default.aspx" /><category term="security" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/security/default.aspx" /><category term="best practice" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/best+practice/default.aspx" /><category term="settings" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/settings/default.aspx" /><category term="logins" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/logins/default.aspx" /><category term="password" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/password/default.aspx" /><category term="check_expiration" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/check_5F00_expiration/default.aspx" /><category term="check_policy" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/check_5F00_policy/default.aspx" /><category term="computing" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/computing/default.aspx" /><category term="policies" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/policies/default.aspx" /><category term="trustworthy" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/trustworthy/default.aspx" /><category term="feature" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/feature/default.aspx" /></entry><entry><title>SQL Server - Have you observed DBCC SHRINKFILE operation performance, on huge databases?</title><link rel="alternate" type="text/html" href="http://sqlserver-qa.net/blogs/perftune/archive/2008/04/25/4112.aspx" /><id>http://sqlserver-qa.net/blogs/perftune/archive/2008/04/25/4112.aspx</id><published>2008-04-25T08:30:00Z</published><updated>2008-04-25T08:30:00Z</updated><content type="html">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 ETL processes, coming to the point by design the DBCC SHRINKFILE operation is a single-threaded operation that means you cannot define or configure the server to use multiple CPUs or a dedicated CPU. So troubleshooting the performance problems...(&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;</content><author><name>sqlmaster</name><uri>http://sqlserver-qa.net/members/sqlmaster.aspx</uri></author><category term="sql server" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/sql+server/default.aspx" /><category term="cache" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/cache/default.aspx" /><category term="memory" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/memory/default.aspx" /><category term="indexes" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/indexes/default.aspx" /><category term="databases" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/databases/default.aspx" /><category term="cpu" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/cpu/default.aspx" /><category term="monitoring" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/monitoring/default.aspx" /><category term="operating system" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/operating+system/default.aspx" /><category term="huge" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/huge/default.aspx" /><category term="dbcc shrinkfile" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/dbcc+shrinkfile/default.aspx" /></entry><entry><title>SQL Server latch waits - index contention &amp; performance issues how DMVs can help you to get information?</title><link rel="alternate" type="text/html" href="http://sqlserver-qa.net/blogs/perftune/archive/2008/04/17/4032.aspx" /><id>http://sqlserver-qa.net/blogs/perftune/archive/2008/04/17/4032.aspx</id><published>2008-04-17T10:06:00Z</published><updated>2008-04-17T10:06:00Z</updated><content type="html">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 • Filter drivers • Compression • Bugs • Other conditions in the I/O path I/O is important factor to consider when it comes to the performance issues, such as blocking, locking and slow response time that will cause stretching of resources on the server....(&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;</content><author><name>sqlmaster</name><uri>http://sqlserver-qa.net/members/sqlmaster.aspx</uri></author><category term="sql server" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/sql+server/default.aspx" /><category term="memory" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/memory/default.aspx" /><category term="disk" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/disk/default.aspx" /><category term="IO" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/IO/default.aspx" /><category term="analysis" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/analysis/default.aspx" /><category term="monitoring" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/monitoring/default.aspx" /><category term="iometer" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/iometer/default.aspx" /><category term="configuration" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/configuration/default.aspx" /><category term="contention" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/contention/default.aspx" /><category term="latching" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/latching/default.aspx" /><category term="latches" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/latches/default.aspx" /></entry><entry><title>SQL Server problem: Excessive paging and memory bottlenecks</title><link rel="alternate" type="text/html" href="http://sqlserver-qa.net/blogs/perftune/archive/2008/04/16/3922.aspx" /><id>http://sqlserver-qa.net/blogs/perftune/archive/2008/04/16/3922.aspx</id><published>2008-04-16T07:02:00Z</published><updated>2008-04-16T07:02:00Z</updated><content type="html">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? SQL Server Memory - what's your method on Configuration and Troubleshooting Issues Using PERFMON to get memory counters, what you need to check? By default, SQL Server changes its memory requirements dynamically, on the basis of available system resources....(&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;</content><author><name>sqlmaster</name><uri>http://sqlserver-qa.net/members/sqlmaster.aspx</uri></author><category term="sql server" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/sql+server/default.aspx" /><category term="memory" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/memory/default.aspx" /><category term="audit" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/audit/default.aspx" /><category term="pagesize" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/pagesize/default.aspx" /><category term="logical disk" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/logical+disk/default.aspx" /><category term="paging" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/paging/default.aspx" /><category term="bottlenecks" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/bottlenecks/default.aspx" /></entry><entry><title>SQL Server 2005 Scalability and Performance - recommended limit on number of instances on a clustered environment?</title><link rel="alternate" type="text/html" href="http://sqlserver-qa.net/blogs/perftune/archive/2008/04/04/3961.aspx" /><id>http://sqlserver-qa.net/blogs/perftune/archive/2008/04/04/3961.aspx</id><published>2008-04-04T09:48:00Z</published><updated>2008-04-04T09:48:00Z</updated><content type="html">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, then there is usually no reason to set any restrictions on the server resource. The Operating System and SQL Server will share the available resources without any problems. However, if there is any resource contention, then depending on the resource...(&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;</content><author><name>sqlmaster</name><uri>http://sqlserver-qa.net/members/sqlmaster.aspx</uri></author><category term="sql server" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/sql+server/default.aspx" /><category term="memory" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/memory/default.aspx" /><category term="clustered" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/clustered/default.aspx" /><category term="i/o" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/i_2F00_o/default.aspx" /><category term="best practice" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/best+practice/default.aspx" /><category term="resources" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/resources/default.aspx" /><category term="monitoring" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/monitoring/default.aspx" /><category term="maintenance plan" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/maintenance+plan/default.aspx" /><category term="performance monitoring" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/performance+monitoring/default.aspx" /><category term="configuration" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/configuration/default.aspx" /><category term="contention" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/contention/default.aspx" /></entry><entry><title>SQL Server Memory - what's your method on Configuration and Troubleshooting Issues</title><link rel="alternate" type="text/html" href="http://sqlserver-qa.net/blogs/perftune/archive/2008/04/01/3733.aspx" /><id>http://sqlserver-qa.net/blogs/perftune/archive/2008/04/01/3733.aspx</id><published>2008-04-01T09:49:00Z</published><updated>2008-04-01T09:49:00Z</updated><content type="html">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 MSDN blogs, Books Online and articles, frequently viewed concept for memory is such as /3GB switch and optimum memory settings. In any case the performance will be sufferred if there is a memory shortage, adding fule to the situation with insufficient...(&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;</content><author><name>sqlmaster</name><uri>http://sqlserver-qa.net/members/sqlmaster.aspx</uri></author><category term="performance" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/performance/default.aspx" /><category term="sql server" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/sql+server/default.aspx" /><category term="cache" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/cache/default.aspx" /><category term="memory" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/memory/default.aspx" /><category term="troubleshoot" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/troubleshoot/default.aspx" /><category term="raid" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/raid/default.aspx" /><category term="hardware" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/hardware/default.aspx" /><category term="best practice" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/best+practice/default.aspx" /><category term="disk space" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/disk+space/default.aspx" /><category term="monitoring" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/monitoring/default.aspx" /><category term="system" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/system/default.aspx" /><category term="baseline" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/baseline/default.aspx" /><category term="configuration" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/configuration/default.aspx" /></entry><entry><title>What's your practice on Disk Defragmentation methods - specific to data file and indexes drives?</title><link rel="alternate" type="text/html" href="http://sqlserver-qa.net/blogs/perftune/archive/2008/03/26/3722.aspx" /><id>http://sqlserver-qa.net/blogs/perftune/archive/2008/03/26/3722.aspx</id><published>2008-03-26T08:01:00Z</published><updated>2008-03-26T08:01:00Z</updated><content type="html">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 way forward to fix the data file fragmentation in SQL Server, say when you have much of SHRINK operations are performed on Database level. The generic answer would be to use the defragmentation tools from windows or operating system based tools, but...(&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;</content><author><name>sqlmaster</name><uri>http://sqlserver-qa.net/members/sqlmaster.aspx</uri></author><category term="performance" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/performance/default.aspx" /><category term="sql server" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/sql+server/default.aspx" /><category term="dbcc" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/dbcc/default.aspx" /><category term="object" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/object/default.aspx" /><category term="best practice" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/best+practice/default.aspx" /><category term="defrag" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/defrag/default.aspx" /><category term="showcontig" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/showcontig/default.aspx" /><category term="blogs" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/blogs/default.aspx" /><category term="disk space" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/disk+space/default.aspx" /><category term="monitoring" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/monitoring/default.aspx" /><category term="diskkeeper" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/diskkeeper/default.aspx" /><category term="file" scheme="http://sqlserver-qa.net/blogs/perftune/archive/tags/file/default.aspx" /></entry></feed>