You can improve system performance by placing logs and database objects on separate devices:
Placing a table on one hard disk and nonclustered indexes on another ensures that physical reads and writes are faster, since the work is split between two disk drives.
Splitting large tables across two disks can improve performance, particularly for multiuser applications.
When log and data share devices, user log cache buffering of transaction log records is disabled.
Partitioning provides multiple insertion points for a heap table, adds a degree of parallelism to systems configured to perform parallel query processing, and makes it possible to distribute a table’s I/O across multiple database devices.
See Chapter 1, “Controlling Physical Data Placement,” in the Performance and Tuning Series: Physical Database Tuning for a detailed discussion of how object placement affects performance.
