Greetings, If the spilt stays in the primary file group only, then the benefits of additional worker threads are not going to be useful.
In my opinion the split to multiple files allows for performance since each file can be on its own disk platter. I think this is useful in the past few years where FC connected storage were either too expensive or not prevalent. Also the idea of splitting to multiple files plays a part for heavy OLTP kind of activity on the database. That said, even for a few thousand agents just using a good FC setup or the hard disk and keeping the DB files and log files into separate FC disk is good enough. Regards Sarbjit Singh From: [email protected] [mailto:[email protected]] On Behalf Of Kevin Holman Sent: Wednesday, July 30, 2014 11:40 PM 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
