I have been creating databases in SQL 2008 with a primary filegroup for the system objects and a secondary, marked Default, for the data.We are preparing a migration to SQL 2014, and the administrator is complaining he won't adopt this structure on the new servers because 'there is no benefit' and 'a backup cannot be restored (!?)'.I've spent the last two hours googling, and found plenty of references stating this arrangement is "Best Practice", but very little to back up this statement.Can anyone point me in the direction of convincing documentation giving reasons why this is (or is not) the case?Secondly, would anyone care to argue the benefits and drawbacks of this structure. Am I simply making work for myself and complicating the lives of the other team members?
↧