That's useful information. I expect a not so large DB, all VMs (resources assigned as required), not sure about IO of the disks though (SAN).
It would be one filegroup with max files of eight, parallel processing shouldn't go over 8 anyway and one core per file is the plan. I tend to not do it though. Thanks, roland From: [email protected] [mailto:[email protected]] On Behalf Of Kevin Holman Sent: Mittwoch, 30. Juli 2014 17:40 To: [email protected] Subject: RE: [msmom] PreCreate DB's? This is common for the TempDB. http://technet.microsoft.com/en-us/library/ms175527(v=SQL.105).aspx However for the OpsDB, it is arguable, and there isn't a standard that fits across the board. It comes down to some significant SQL tuning, and will be dependent on a LOT of factors, primarily things like how many CPU's are present, is the SQL server virtualized or not, is the VM tuned for NUMA topology, is MAXDOP tuned appropriately, etc. I have had customers split these DB's into multiple files, and had many who didn't. I cannot say we always saw a major performance gain either way. It is supported to take an OpsMgr DB and split into multiple files in the PRIMARY filegroup only. We do not support splitting the DB into multiple filegroups. From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Roland Janus Sent: Wednesday, July 30, 2014 5:03 AM To: [email protected] <mailto:[email protected]> Subject: [msmom] PreCreate DB's? Hey, In ConfigMgr it is supported and may even be recommended to create the DB in advance to e.g. use several files (max. 8) for parallel processing. Is that recommend, supported or even useful for OpsMgr? -Roland
