THE SQL Server Blog Spot on the Web

Welcome to SQLblog.com - The SQL Server blog spot on the web Sign in | |
in Search

Browse by Tags

All Tags » Performance » Best Practices   (RSS)
Showing page 2 of 6 (60 total posts)
  • New on SQLMag.Com: Update to SP_WHOISACTIVE

    I profiled Adam Machanic's (blog | twitter) excellent stored procedure, SP_WHOISACTIVE, back in August of 2010 in my monthly SQLMag column, Tool Time.  Adam has been diligent about maintaining the tool and adding new features. Read the details on my SQLMag Tool Time column (here - ...
    Posted to Kevin Kline (Weblog) by KKline on April 21, 2011
  • Reminder: Totally Awesome and Totally Free Training SQL Server Training

    One of the things that I enjoy about working for Quest Software is that we give back copiously to the community.  From activities and offerings like SQLServerPedia, to our free posters mailed anywhere in North America (and don't forget the free hi-res PDFs for the rest of the world), Don't forget that free DVDs of our virtual conferences ...
    Posted to Kevin Kline (Weblog) by KKline on February 21, 2011
  • Database Maintenance Scripting Done Right

    I first wrote about useful database maintenance scripts on my SQLBlog account way back in 2008. Hmmm - now that I think about it, I first wrote about my own useful database maintenance scripts in a journal called SQL Server Professional back in the mid-1990's on SQL Server v6.5 or some such. But I digress... Anyway, I pointed out a couple ...
    Posted to Kevin Kline (Weblog) by KKline on February 18, 2011
  • Have You Heard About Project Lucy?

    Lucy, You Got Some 'Splainin to Do!' Quest Software's latest community initiative, Windows Azure-based Project Lucy, has debuted! Project Lucy is part infrastructure analytics, part social media experiment, and part performance data warehouse. The best things about Project Lucy include: It’s Free - just like our SQLServerPedia ...
    Posted to Kevin Kline (Weblog) by KKline on February 16, 2011
  • Linked servers and performance impact: Direction matters!

    When you have some data on a SQL Server instance (say SQL01) and you want to move the data to another SQL Server instance (say SQL02) through openquery(), you can either push the data from SQL01, or pull the data from SQL02.   To push the data, you can run a SQL script like the following on SQL01, which is the source server:   -- The ...
    Posted to Linchi Shea (Weblog) by Linchi Shea on November 30, 2010
  • Linked servers: permissions and distributed query performance

    In an earlier post, I highlighted that linked server security configuration can have a huge performance impact, and complained that this was not properly documented in SQL Server Books Online and filed a Connectitem for this. Good news is that in Books Online for SQL Server 2008 R2,  Microsoft has revised the documentation, and included the ...
    Posted to Linchi Shea (Weblog) by Linchi Shea on November 22, 2010
  • Revisiting the transaction batch size

    It’s a well known good practice to control the batch size when you perform large data changes. For instance, you may need to purge a large amount of data monthly, and if you delete them all in one shot, you may blow up your transaction log. Therefore, it's wise that you chop up the total amount of data to be deleted into smaller chunks and delete ...
    Posted to Linchi Shea (Weblog) by Linchi Shea on July 31, 2010
  • Bad database practices: abusing linked servers

    In SQL Server, it is rather handy to retrieve data from a different SQL Server instance and use the result locally in another SQL statement for further processing. In theory and in the set purists’ fantasy land, it shouldn’t matter where you get your data or even how you get the data as long as you can use them to further compose a set-based ...
    Posted to Linchi Shea (Weblog) by Linchi Shea on November 6, 2009
  • Bad database practices: moving data to procedures vs. moving procedures to data

    Is it better to move data to procedures or move procedures to data?   The answer is, of course, “it depends.” Let’s consider a scenario where you have two SQL Server instances: ServerA and ServerB, and you have a procedure on ServerB (call it procB), but need to access data on ServerA.   Three database solutions are ...
    Posted to Linchi Shea (Weblog) by Linchi Shea on October 30, 2009
  • SQL Server challenge: show me trace flag 1118 is significant -- a quick update

    I posted the following SQL Server challenge yesterday:   Describe a reproducible workload that would see significant throughput improvement when trace flag 1118 is enabled.   In response, Konstantin Korobkov wanted to know whether the number of data files in tempdb would make a difference.   I did test that scenario and did ...
    Posted to Linchi Shea (Weblog) by Linchi Shea on October 2, 2009
< Previous 1 2 3 4 5 Next > ... Last »
Powered by Community Server (Commercial Edition), by Telligent Systems
  Privacy Statement