locked
SCOM 2012 - Operations Manager Databases (SQL 2008 R2) RRS feed

  • Question

  • We are implementing SCOM 2012 (backend is SQL 2008 R2) but only Operations Manager for now. The expected size of the databases is about 500 GB (for operations manager db) and 1.6 TB for operations manager datawarehouse database (this includes the free space and growth for next 12 months). Since the databases are larger in size, we are thinking of using multiple data files (with each file in different drive.)  for each database. But we don't know whether this will create any issues. I am not looking from a SQL Server best practices point of view for this question, but this is more from a product perspective. Did anyone create multiple data files for the operations manager databases? Please share your experiences.

    Regards,

    Rocky


    Thursday, July 25, 2013 2:16 AM

Answers

  • Hi,

    I didn't create multiple data files, but you can do it. Please see this blog:

    System Center – SQL Server 2008 R2 Performance Tuning

    http://blog.scomfaq.ch/2012/02/28/system-center-sql-server-2008-r2-performance-tuning/


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    • Marked as answer by Cloud_TS Thursday, August 1, 2013 7:39 AM
    Thursday, July 25, 2013 6:19 AM
  • It is no problem to create a database with multiple data files for both the data and log files. This will stripe the data as well, so if implemented on separate disks will also increase speed. Another db to consider for this is the tempdb. SO yes it is possible to create a database with multiple files (create the small db and create additional db files and make all same size). Makes it easier to size the disks, and if in emergency a move of files is needed also smaller chunks. Also if split on different disks it increases the speed because of striping of data acorss the files.

    Had a customer with a setup where we split the opsdb in 8 files and the log file in 4 files. the tempdb also in 8 files. the DW into 10 files. Because the disks we separate disks for each file it was really fast as well!


    Bob Cornelissen - BICTT (My Blog about SCOM) - MVP 2012 + 2013 and Microsoft Community Contributor 2011 + 2012 Recipient

    Thursday, July 25, 2013 1:21 PM

All replies

  • Hi,

    I didn't create multiple data files, but you can do it. Please see this blog:

    System Center – SQL Server 2008 R2 Performance Tuning

    http://blog.scomfaq.ch/2012/02/28/system-center-sql-server-2008-r2-performance-tuning/


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    • Marked as answer by Cloud_TS Thursday, August 1, 2013 7:39 AM
    Thursday, July 25, 2013 6:19 AM
  • It is no problem to create a database with multiple data files for both the data and log files. This will stripe the data as well, so if implemented on separate disks will also increase speed. Another db to consider for this is the tempdb. SO yes it is possible to create a database with multiple files (create the small db and create additional db files and make all same size). Makes it easier to size the disks, and if in emergency a move of files is needed also smaller chunks. Also if split on different disks it increases the speed because of striping of data acorss the files.

    Had a customer with a setup where we split the opsdb in 8 files and the log file in 4 files. the tempdb also in 8 files. the DW into 10 files. Because the disks we separate disks for each file it was really fast as well!


    Bob Cornelissen - BICTT (My Blog about SCOM) - MVP 2012 + 2013 and Microsoft Community Contributor 2011 + 2012 Recipient

    Thursday, July 25, 2013 1:21 PM