Improve performance by spreading data

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT Kevin Kline - Monitoring/Administration Publisher residing on a different domain SQL Mail troubleshooting Installing SQL Server client tools on Windows XP Pro Incorrect drive letter assignments Installing SQL Server 2000 Enterprise Edition on Windows XP Identifier field in Microsoft's SQL Server Getting scheduled DTS packages to run Performance problems after installing Windows Service Pack 4 Difficulties transferring stored procedures and triggers Shrinking database and log files Microsoft SQL Server Performance Monitoring and Tuning Using traces in SQL Server Profiler SQL Server Mailbag: CALs, witnesses and unwanted changes SQL Server Mailbag: Data restoration and DB property management Working with IntelliSense in SQL Server 2008 Management Studio SQL Server Mailbag: Stored procedures, triggers and SSRS reports Troubleshooting Distributed Transaction Coordinator errors in SQL Server Clearing the Windows page file and its effect on server performance Optimizing SQL Server indexes –- even when they're not your indexes Performance implications of transaction log autogrowth in SQL Server The short course on how SQL Server really works

RELATED GLOSSARY TERMS Terms from Whatis.com − the technology online dictionary contiguity  (SearchSQLServer.com) contiguous  (SearchSQLServer.com) drilldown  (SearchSQLServer.com) hashing  (SearchSQLServer.com) hybrid online analytical processing  (SearchSQLServer.com)

RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary

Yes, you are correct. You only get a performance improvement when spreading data files across physically separate volumes. It doesn't help to spread data files across logically separate but physically identical drives. It never really helps to spread the transaction log files across multiple drives since, as you mention, transaction log files always write on the last data page of the last drive in the transaction log file volume.