http://www.sqlservercentral.com/Articles tagged Miscellaneous, Performance Tuning and Scaling posted on SQLServerCentral.comen-us360sjones@sqlservercentral.com (Steve Jones)New Author! Deadlocks aren't the most common problem but they happen they can really degrade performance. Shiv works through how to nail down what is causing the deadlock. http://www.sqlservercentral.com/articles/Performance+Tuning+and+Scaling/tracingdeadlocks/1324/2007/04/06http://www.sqlservercentral.com/articles/Performance+Tuning+and+Scaling/tracingdeadlocks/1324/New author Jambu Krishnamurthy brings us a look at table variables and how they differ from temporary tables in SQL Server 2000. http://www.sqlservercentral.com/articles/Performance+Tuning+and+Scaling/2691/2006/11/21http://www.sqlservercentral.com/articles/Performance+Tuning+and+Scaling/2691/It has not been clear to what extent fragmentation, either internal or external, truly affects the performance of your SQL Server 2000 databases. New author Koby Biller discusses some of the impacts that it could have and has a free tool for download that can help you determine how fragmented your disk truly is. http://www.sqlservercentral.com/articles/Performance+Tuning+and+Scaling/performancemonitoringbyinternalfragmentationmeasur/2014/2005/08/16http://www.sqlservercentral.com/articles/Performance+Tuning+and+Scaling/performancemonitoringbyinternalfragmentationmeasur/2014/New Author! Deadlocks aren't the most common problem but they happen they can really degrade performance. Shiv works through how to nail down what is causing the deadlock. http://www.sqlservercentral.com/articles/Performance+Tuning+and+Scaling/tracingdeadlocks/1324/2007/04/06http://www.sqlservercentral.com/articles/Performance+Tuning+and+Scaling/tracingdeadlocks/1324/As Chris points out, in most applications these days you end up having to go with optimistic locking, which presents a few challenges. Chris works through the list of options. If you're building web/disconnected apps and need anything besides last update wins, this one is for you. http://www.sqlservercentral.com/articles/Performance+Tuning+and+Scaling/dealingwithchangingdata/1233/2003/12/19http://www.sqlservercentral.com/articles/Performance+Tuning+and+Scaling/dealingwithchangingdata/1233/Kumar discusses the differences between scale up and scale out, then does a very good walk through of how to build a scale out solution. http://www.sqlservercentral.com/articles/Performance+Tuning+and+Scaling/scalingout/1209/2003/12/03http://www.sqlservercentral.com/articles/Performance+Tuning+and+Scaling/scalingout/1209/Another new author! Gheorge shares some ideas about importing event logs and using OLAP to analyze the results. Not a bad idea at all. How many of use OLAP as often as we should? Read the article, see if it's something you want to try - and let Gheorge know what you think! http://www.sqlservercentral.com/articles/Administering/importingandanalyzingeventlogs/997/2003/05/28http://www.sqlservercentral.com/articles/Administering/importingandanalyzingeventlogs/997/Seagate has a white paper out that discusses how faster (15k rpm) drives can lead to lower cost of ownership. Interesting, and worth looking into. http://www.sqlservercentral.com/redirect/articles/983/2003/05/08http://www.sqlservercentral.com/redirect/articles/983/New author! Mike Pearson discusses how auto close was at the root of a performance problem he was troubleshooting, how you can check your servers easily, and discusses why both auto close and auto shrink are bad ideas in a production environment. http://www.sqlservercentral.com/articles/Administering/autocloseandautoshrinkjustdont/984/2003/05/05http://www.sqlservercentral.com/articles/Administering/autocloseandautoshrinkjustdont/984/A monster book at 980 pages, it's written in 'how-to' format and has a ton of good material. Andy gave it the once over for us and reports back - see what he thinks! http://www.sqlservercentral.com/articles/Installation/reviewofsql2000fastanswers/959/2003/04/18http://www.sqlservercentral.com/articles/Installation/reviewofsql2000fastanswers/959/Programmers can most commonly relate to interface-based programming in their programming language. This is harder to accomplish in SQL Server though. In this article by Chris Cubley, he shows you how to build interfaced-based SQL. http://www.sqlservercentral.com/articles/Performance+Tuning+and+Scaling/sql_interface_final/732/2002/07/19http://www.sqlservercentral.com/articles/Performance+Tuning+and+Scaling/sql_interface_final/732/This book from Microsoft Press has a lot of good information that will help you do capacity planning and performance tuning. Is it worth buying though? Andy just finishing reading it and writing the review, see what he thinks! http://www.sqlservercentral.com/articles/Performance+Tuning+and+Scaling/reviewofsqlserver2000performancetuning/673/2002/05/03http://www.sqlservercentral.com/articles/Performance+Tuning+and+Scaling/reviewofsqlserver2000performancetuning/673/This week Andy continues his series on how to reduce the number of round trips to the server by looking at some things you can easily add to your applications without a lot of rearchitecting. http://www.sqlservercentral.com/articles/Performance+Tuning+and+Scaling/reducingroundtripspart3/621/2002/03/11http://www.sqlservercentral.com/articles/Performance+Tuning+and+Scaling/reducingroundtripspart3/621/Middle tier applications often use a single database management system (DBMS) to store data, which can expose scaling limitations as the number of user requests increases. Caching, a technique used to increase application performance by copying data and then using the copied data in place of the original data, can dramatically increase the throughput (the number of application requests serviceable per unit time) and scalability of middle tier applications. http://www.sqlservercentral.com/redirect/articles/619/2002/03/08http://www.sqlservercentral.com/redirect/articles/619/Last week Andy started a discussion of the various ways you can reduce the number of round trips to the server. This week he continues by looking at a method he used recently to do client side caching of data to eliminate the round trip altogether. Gotta read it! http://www.sqlservercentral.com/articles/Performance+Tuning/reducingroundtripspart2/588/2002/02/06http://www.sqlservercentral.com/articles/Performance+Tuning/reducingroundtripspart2/588/This white paper outlines the following: -The steps to configure Log Shipping between two or more servers that are running SQL Server 2000 Enterprise Edition. -The steps to configure Log Shipping between Microsoft SQL Server 7.0 Service Pack 2 (SP2), or later, and Microsoft SQL Server 2000 Enterprise Edition. -A brief comparison between Log Shipping and the other high availability-solutions that SQL Server provides. http://www.sqlservercentral.com/redirect/articles/577/2002/01/25http://www.sqlservercentral.com/redirect/articles/577/SQL Profiler lets you log the results of a trace directly to a table, yet would you believe you can't save the trace as a script to do the exact same thing? Find out why and get some ideas on work arounds. http://www.sqlservercentral.com/articles/Performance+Tuning+and+Scaling/profilerloggingresultstoatable/564/2002/01/07http://www.sqlservercentral.com/articles/Performance+Tuning+and+Scaling/profilerloggingresultstoatable/564/Running a Web farm means managing session state across servers. Since session state can't be shared across a Web farm with Internet Information Services 5.0, a custom solution is required. One such solution using a tool called the session manager is described here. http://www.sqlservercentral.com/redirect/articles/244/2001/07/06http://www.sqlservercentral.com/redirect/articles/244/