3PAR SQL Server best practice
we have vm's running on hyper-v sql server 2012. storage 3par san. os installed on 1 vhdx , have 1 vhdx sql server data, data , log files in same directory. vhdx files on 1 csv on 3par , adaptive optimization enabled on csv. databases between 50-100gb big, have database of 1tb. what best practice concerning placement of sql server data , log file , best io performance? matter data , log files on same vhdx or on same csv? 1tb databases did created separate csv vhdx files containing data files , log files. size of databases not impact performance. need measure io characteristics. monitor environment determine optimal placement. without detailed information particular application , usage, impossible provide useful guidance. 'best practice' varies according specific needs. in general, recommended practice place log files on different volume/spindle database file. in general, spreading access across multiple spindles improves performance. handled within array - ...