(MDF and MDF) versus (MDF and NDF)

[rtantek]

in creating a db where there are multiple physical files, is there an advantage to changing the file extension of the extended physical file from .NDF to .MDF? if so, is there a white paper on it?

 

[tlbroadbent]

I've not seen anything that addresses the issue. I don't know why the file type would matter. You can use any file extension you want. Personally, I prefer to stay with the default extensions. If you want to get the best answer for your question read faq183-874 and thread183-468158.
Terry L. Broadbent - DBA
SQL Server Page:

http://tlbroadbent.home.attbi.com/sql/sql_articles.htm

 

[rtantek]

Terry, the scenario is to put data in one MDF and the index on another MDF. It was suggested that SQL may use one thread to accessing the data and another to access the index. or that SQL may use only one thread to access the index if the it is located on an NDF file.

 

[tlbroadbent]

I understand the concept of putting data and indexes on different files. Putting indexes on a different file is helpful if the files are on different devices. The more disk drives involved the better. Your question asked about the changing the extension. As stated, I don't believe the extension will make any difference in performance. Physical placement of files will make a difference. If you want to get the best answer for your question read faq183-874 and thread183-468158.
Terry L. Broadbent - DBA
SQL Server Page:

http://tlbroadbent.home.attbi.com/sql/sql_articles.htm