We pre-create our SharePoint content databases in SQL, so we can distribute database files among disks and tune some parameters on the SQL Server side. Then we convert the SQL databases into SharePoint content databases by issuing a New-SPContentDatabase from a web front end, specifying the name of the existing, newly created SQL database. According to our experience, the cmdlet will not create a database but reuse the existing one, and will proceed to create the SharePoint schema into it. However, I've found no documentation regarding this behavior.
According to documentation, Mount-SPContentDatabase does more or less the same thing, given that the database exists already, which is the case in our context.
The question is, are there any relevant difference between using New-SPContentDatabase and Mount-SPContentDatabase when the target database already exists, and is empty?
Thanks in advance.