0 thoughts on “System Center 2012–using a common SQL backend database (#SYSCTR, #SCOM, #SCSM)”

0 thoughts on “System Center 2012–using a common SQL backend database (#SYSCTR, #SCOM, #SCSM)”

1. Alexander Schmitt May 23, 2012 at 8:42 am

   Hi Cameron,

   can you tell me where it is documented that SQL 2008 R2 SP1 CU6 is supported for all products? The research for my current customer showed that it looks like described in this post from Daniele http://nocentdocent.wordpress.com/articles-and-series/planning-sql-server-for-system-center-2012/. 
   I’m quite sure SQL 2008 R2 SP1 CU6 will work for all but if it is not documented as supported in Technet or some other official MS site I won’t recommend my customer to use it.

   Regards Alex
2. Cameron Fuller Post authorMay 23, 2012 at 10:04 am

   Currently the documentation on the various components is inconsistent unfortunately but all System Center 2012 will work on SQL 2008 R2 SP1 CU6. Please note that CU6 is only required for ConfigMgr. The other components do not required a particular CU.
3. Alexander Schmitt May 24, 2012 at 7:17 am

   Thank you for your response. Do you know about any plans to update the docs?

   Regards
   Alex
4. Cameron Fuller Post authorMay 24, 2012 at 6:01 pm

   Unfortunately I haven’t heard anything official. However, I would expect that as each of these are now components and not individual products that the documentation will be adjusting more to a common format. With SQL 2012 coming up, there will likely need to be some new functionality added to provide support for it in OpsMgr and other products so I would expect that documentation would need to be updated if/when support is provided for SQL 2012.
5. Cameron Fuller Post authorJune 5, 2012 at 2:43 pm

   Clarification on the article above, I list it as OpsMgr but I believe that this line should actually say ConfigMgr: ConfigMgr will not support SQL dynamic ports which is the default SQL setting, change each SQL instance dynamic port to a TCP port.
6. Steve Burkett July 25, 2012 at 8:52 am

   Any idea about licensing? All the System Center products come with rights to run SQL Server for SC purposes. Is that just one copy for sharing between all the products and you buy more SQL’s if you want to split it out, or can we legally install a SQL for CM, a SQL for OM, a SQL for SM etc etc?
7. Cameron Fuller Post authorJuly 25, 2012 at 3:23 pm

   Steve, that’s an excellent question. I do not consider myself to be capable of providing licensing recommendations but I would point to Marnix Wolf’s article series discussing these topics at: http://thoughtsonopsmgr.blogspot.com/2012/07/sc-2012-licensing-lets-complify-part-v.html
8. Pank Shrm August 5, 2012 at 1:41 pm

   What if i am having Single SQL Server BOX with single NIC, is it possible to use same Static TCP port (1433) for all instances???

   If not, wat will be the best solution (Like adding more NIC or something else..)

   Brief Detail of my setup……….

   SQL 2008 R2 Remote Standalone (No Cluster and Single NIC)
   SCCM 2012
   SCOM 2012
9. Cameron Fuller Post authorAugust 6, 2012 at 6:56 am

   Multiple instances of SQL cannot share a port number. So as an example, you cannot have the default instance on 1433 and then add a second instance called Instance2 and have it use port 1433. At a minimum, the reporting instances for each of the products needs to be separate but those can run on standard edition. Additionally, each ConfigMgr site requires a separate instance from the other ConfigMgr sites. So if you have a multiple site ConfigMgr environment that will require multiple instances. Depending on scaling and with sufficient hardware and such you could put together multiple components of System Center in the same instance such as App Controller, Orchestrator and such.

   Or the shorter version, is it possible to use the same static TCP port on one server for all instances – no.