Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
itsonlyme4
Posting Yak Master
109 Posts |
 Posted - 2014-03-16 : 09:58:41
|
| I have a sql server 2000 instance where the MDF for one of the databases is on the C: drive and we are running out of space.The Database is a transactional replication subscriber - the Replication logging and Replication PUSH jobs are running on the Publisher.If I add a Datafile (.NDF) on another Drive and then set the .MDF file to NOT autogrow, will the .MDF stop growing altogether and data will be written to the .NDF going forward? Or am I better served to detach the database and just move the MDF file to another drive?? |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2014-03-16 : 12:56:47
|
| Yes if you set the MDF file to not autogrow, it will use the NDF file. SQL Server uses a proportional fill algorithm for the data files in a filegroup. But I would move the MDF file to a different drive as it is not a good practice to have it on the same drive as the operating system.Tara KizerSQL Server MVP since 2007http://weblogs.sqlteam.com/tarad/ |
 |
|
|
jackv
Master Smack Fu Yak Hacker
2179 Posts |
Posted - 2014-03-17 : 02:44:13
|
| There are certain performance benefits by splitting out some data into different files across different drives - for example, splitting read only and write data. This requires some analysis and planning.Jack Vamvas--------------------http://www.sqlserver-dba.com |
|
|
|
|
|
|
Move MDF file vs adding an NDF file