You have a database named DB1.
You plan to configure change data capture on the existing tables in DB1.
The database file settings for the DB1 are shown in the exhibit. (Click the Exhibit button.)
You need to minimize disk contention caused by change data capture.
What should you do?
More than one answer choice may achieve the goal. Select the BEST answer.
A.
Increase the autogrowth value of the database file.
B.
Set the database recovery model to simple.
C.
Increase the autogrowth value of the log file.
D.
Configure change data capture to use to a secondary filegroup.
https://technet.microsoft.com/en-us/library/dd266396%28v=sql.100%29.aspx
We found no difference in our tests between having the change table on the same filegroup as the application table and having them on different filegroups. This might be different when the data files are located on an I/O subsystem that is already under heavy load. In this case, putting change tables in a filegroup that is located on a different set of physical disks can improve change data capture performance.
Of course, change data tables should be in a separate FG (even, preferably), on a separate physical disk.
It is always a SQL Server 2012 best practice to configure a separate filegroup for CDC, in order to avoid disk I/O contention.