Hi, im settings up two new SharePoint 2013 farms. One production and one Test. They run on Windows 2012 Servers and the Database server are dedicated to SharePoint, running 2 instances, one for each farm.
Sharepoint are updated to Marts Public Update
The Database is SQL 2012 running on Windows Server 2012 in core mode.
I have this problem.
When creating content databases or installing services that create databases, they do not read the ModelDB settings. Im using PowerShell scripts but have testet through Central Admin too, same problem.
It is not the know bug with autogrowth, i know SharePoint dont read this. But initial size are ignored too.
More corectly it uses a previous value.
I have changed the initial size of the log files from 2,5 GB to 50 MB, there were a calculation error early on in the project.
But now, when i create any database the logfil starts as a 2,5 GB file. I have restarted the instances, and all servers too, just to be sure.
It is like both farms have cached the earlier value some where and simply ignores the current value set in ModelDB.
When i create a database in SQL Management Studio, up front it works fine.
Any idea on where SharePoint have cached this value and how i clear it ? Internet searches have not indicated this is a common issue.