SqlServer-QA.net

Bottlenecks aka locking & blocking is a quite common scenario within a RDBMS platform, that too SQL Server is not an exception at all. With an access to shared resources causes bottlenecks and demands on shared resources cause poor response time and must be identified and tuned. Few root causes for such blocking are: Insufficient resources, ...

How many SQL Server licenses you need to fix the number of CPUs on the server? The answer it depends on the number! Well having hyper-threading (i.e. multiple threads execute on a single physical CPU appearing as 2 logical CPUs) and dual-core technology (i.e. a single CPU socket that has more than 1 core appearing as multiple logical CPUs) is a ...

Parameterizing T-SQL queries are a well-known task such as database programming and best practice in some tasks. It allows query plan reuse and eliminates the need of recompilation for multiple invocations of the same query that simply has different parameter values. However, there are times when parameterized queries might perform poorly, because ...

Here comes another Frequently Asked Question (FAQ) on the forums and Frequently Posted Blog (FPB) here about high cpu issues on the SQL Server 2000 instances. Looking at high cpu spiks and performace issues is a common problem in all SQL Server installations, handling this issue within SQL Server 2005 is not a problem as there are DMVs to extend ...

The system DMV sys.dm_os_schedulers is an useful DMV to find such as running tasks & active workers threads etc. This is required to monitor the system state is heavily loaded or not, in particular this view will help you identify if there is any CPU bottleneck in the SQL Server machine. SELECT ...

Dynamic Management Views (DMV) are very useful to get server state information to monitor the status, but not always you have to still continue in monitoring using SYSMON & PROFILER that are available by default with SQL installation. The engine within SQL Server 2005 improves accuracy by using the high-resolution counters that are capable to ...

By now you should have applied the Service Pack 4 on your SQL Server 2000 instances and you might come across the message within the SQL error log ''SQL Server has encountered 5877 occurrence(s) of IO requests taking longer than 15 seconds to complete on file''. Though this is classed as an informational message you should be concerned to ...