In the past, I have used contig.exe to remove physical fragmentation from SQL Server data files. They have always been on locally attached storage. Is there any benefit to running this on a data file that is stored on a SAN?
In the past, I have used contig.exe to remove physical fragmentation from SQL Server data files. They have always been on locally attached storage. Is there any benefit to running this on a data file that is stored on a SAN?
Not recommended to defragment files on a SAN, SQL or otherwise.
See this related ServerFault question and this excellent whitepaper. The major points include: