Hi,

Wanted to know how to calculate the IOPS requirement for SCCM 2012 R2 with local DB and remote DB?

Is there any recommendation of IOPS for SCCM 2012 R2?

We are planning to use common DB for SCOM, SCCM and SCVMM, so wanted to understand how do to calculate the IOPS for all 4 apps for better performance. Probably we will use RAID 10.

Regards,

Parag

We are planning to use common DB for SCOM, SCCM and SCVMM, so wanted to understand how do to calculate the IOPS for all 4 apps for better performance. Probably we will use RAID 10.

Regards,

Parag

Don't do it.

SCCM presents a security nightmare as it requires local admin rights to the SQL server as well as full SA permissions to the instance it's being installed in.  Not only that, but the SQL role SCCM installs doesn't inherently recognize SQL clusters which adds even more configuration overhead all for a Site System role that has no inherent HA options of it's own.

Just don't do it.

You're far better off using a shared SQL cluster (with unique instances) for the rest of System Center but putting SCCM on it's own SQL server... collocate it with the primary site server if you want.  From an admin perspective it's simpler to support and superior security all in one.   Doesn't even cost you any more (SQL standard is free if used exclusively for SC).

From an IOps perspective MS documentation recommends RAID 10 for all data drives for SCCM ... see this : https://technet.microsoft.com/en-us/library/hh846235.aspx?f=255&MSPPError=-2147217396

For my clients obsessed with virtualizing, I use a classic 50/50 R/W split against 10k RPM drives to get to a whopping 390 IOps per data volume, then factor in that SCCM will need an OS, SCCM, SQL-Logs (so 390*3)... then SQL DB and DSL/Staging at roughly 80/20 (more read than write or 312*2 IOps) ... for a whopping 1794 IOps to virtualize the primary site server.  Poor load planning is probably the #1 reason people will complain that SCCM doesn't behave well virtualized .... but these numbers should also give you an idea of what to expect if you are goign down the IOps path (I'm guessing on a virtual server otherwise you'd just be putting every DB on it's own spindles and not asking).

System Center is a great suite ... but be careful how you build it out.  I recomend downloading and going over the Private Cloud fast Tracks from Microsoft ... they have sample configurations right down to SQL count and instances for everything (but SCCM, which is basically assumed to be standalone): https://www.microsoft.com/en-us/download/details.aspx?id=30417

• Edited by Justin.King 2 hours 15 minutes ago

We are planning to use common DB for SCOM, SCCM and SCVMM, so wanted to understand how do to calculate the IOPS for all 4 apps for better performance. Probably we will use RAID 10.

Regards,

Parag

Don't do it.

SCCM presents a security nightmare as it requires local admin rights to the SQL server as well as full SA permissions to the instance it's being installed in.  Not only that, but the SQL role SCCM installs doesn't inherently recognize SQL clusters which adds even more configuration overhead all for a Site System role that has no inherent HA options of it's own.

Just don't do it.

You're far better off using a shared SQL cluster (with unique instances) for the rest of System Center but putting SCCM on it's own SQL server... collocate it with the primary site server if you want.  From an admin perspective it's simpler to support and superior security all in one.   Doesn't even cost you any more (SQL standard is free if used exclusively for SC).

From an IOps perspective MS documentation recommends RAID 10 for all data drives for SCCM ... see this : https://technet.microsoft.com/en-us/library/hh846235.aspx?f=255&MSPPError=-2147217396

For my clients obsessed with virtualizing, I use a classic 50/50 R/W split against 10k RPM drives to get to a whopping 390 IOps per data volume, then factor in that SCCM will need an OS, SCCM, SQL-Logs (so 390*3)... then SQL DB and DSL/Staging at roughly 80/20 (more read than write or 312*2 IOps) ... for a whopping 1794 IOps to virtualize the primary site server.  Poor load planning is probably the #1 reason people will complain that SCCM doesn't behave well virtualized .... but these numbers should also give you an idea of what to expect if you are goign down the IOps path (I'm guessing on a virtual server otherwise you'd just be putting every DB on it's own spindles and not asking).

System Center is a great suite ... but be careful how you build it out.  I recomend downloading and going over the Private Cloud fast Tracks from Microsoft ... they have sample configurations right down to SQL count and instances for everything (but SCCM, which is basically assumed to be standalone): https://www.microsoft.com/en-us/download/details.aspx?id=30417

• Edited by Justin.King Thursday, April 16, 2015 5:30 AM
• Proposed as answer by Jeff Poling Thursday, April 16, 2015 11:20 AM

We are planning to use common DB for SCOM, SCCM and SCVMM, so wanted to understand how do to calculate the IOPS for all 4 apps for better performance. Probably we will use RAID 10.

Regards,

Parag

Don't do it.

SCCM presents a security nightmare as it requires local admin rights to the SQL server as well as full SA permissions to the instance it's being installed in.  Not only that, but the SQL role SCCM installs doesn't inherently recognize SQL clusters which adds even more configuration overhead all for a Site System role that has no inherent HA options of it's own.

Just don't do it.

You're far better off using a shared SQL cluster (with unique instances) for the rest of System Center but putting SCCM on it's own SQL server... collocate it with the primary site server if you want.  From an admin perspective it's simpler to support and superior security all in one.   Doesn't even cost you any more (SQL standard is free if used exclusively for SC).

From an IOps perspective MS documentation recommends RAID 10 for all data drives for SCCM ... see this : https://technet.microsoft.com/en-us/library/hh846235.aspx?f=255&MSPPError=-2147217396

For my clients obsessed with virtualizing, I use a classic 50/50 R/W split against 10k RPM drives to get to a whopping 390 IOps per data volume, then factor in that SCCM will need an OS, SCCM, SQL-Logs (so 390*3)... then SQL DB and DSL/Staging at roughly 80/20 (more read than write or 312*2 IOps) ... for a whopping 1794 IOps to virtualize the primary site server.  Poor load planning is probably the #1 reason people will complain that SCCM doesn't behave well virtualized .... but these numbers should also give you an idea of what to expect if you are goign down the IOps path (I'm guessing on a virtual server otherwise you'd just be putting every DB on it's own spindles and not asking).

System Center is a great suite ... but be careful how you build it out.  I recomend downloading and going over the Private Cloud fast Tracks from Microsoft ... they have sample configurations right down to SQL count and instances for everything (but SCCM, which is basically assumed to be standalone): https://www.microsoft.com/en-us/download/details.aspx?id=30417

• Edited by Justin.King Thursday, April 16, 2015 5:30 AM
• Proposed as answer by Jeff Poling Thursday, April 16, 2015 11:20 AM

Just to add to this CM12 and OM12 can't share the same SSRS.

If SQL is remote to CM12 you are asking for a world of hurt.

Sorry bymistake I wrote the common DB. Its not a common DB, we will be using common SQL server with dedicated instances for each apps.

So want to understand what will be IOPS required for SQL server to have better performance with workload of SCCM, SCOM and SCVMM.

Sorry bymistake I wrote the common DB. Its not a common DB, we will be using common SQL server with dedicated instances for each apps.

Still don't do it, both CM12 and OM12 use SQL Heavy, you are begging for trouble by doing this. It is recommend that SQL and CM12 be installed together, why exactly would you want to separate them!

To reduce administration overhead to manage multiple SQL servers and hardware of each SQL servers, by configuring high-end common SQL server.

It is recommend that SQL and CM12 be installed together, 

So you mean to say it is not good to use remote SQL server for SCCM?

So you mean to say it is not good to use remote SQL server for SCCM?

Yes that is exactly what I'm saying. CM12 will in 99% of all case even preform better using local SQL too.

Thanks for suggestion, will work on that.

By the way can please tell me how to calculate the IOPS requirement for SCCM server and remote SQL server for SCCM server.

Is there any recommendation of IOPS?