Jump to content


overcaffeinated

SCCM + WSUS on same SQL server instance?

Recommended Posts

Hey everyone, especially Niall, thank you so much for this community. It's been a great help!



I am standing up a new SCCM 2012 R2 server and am setting it up with the plan to deploy SUS updates from SCCM (currently using a standalone WSUS server in our environment). We are running the SQL server DB for SCCM on its own server, using the default instance. I have not installed the SUS role yet on the new SCCM server. My DBA is asking me if it's OK for the SCCM and WSUS databases to share the same instance. My instinct tells me I shouldn't, but the DBA says it that if it were possible, it would save a lot of maintenance overhead. Any SCCM/SQL gurus willing to weigh in on this?


I found one link on TechNet that seemed to suggest best practices for this: use the default instance for SCCM, and a named instance for WSUS. But is it necessary? Or recommended just because it's easier to determine resource utilization? Thanks everyone!


Share this post


Link to post
Share on other sites


Yes this can be done and yes they can share a instance,

 

Keep in mind that it is NOT recommend to have SQL remote from CM12 or WSUS for that matter.

Share this post


Link to post
Share on other sites

Yes this can be done and yes they can share a instance,

 

Keep in mind that it is NOT recommend to have SQL remote from CM12 or WSUS for that matter.

 

Is it not recommended only from a speed perspective? They are both virtualized on vSphere with a 10 Gbit link. I'm not concerned about throughput, but maybe there are other reasons? Our SCCM 2007 has been running with a "remote" SQL instance for years and is very fast.

 

Thanks!

Share this post


Link to post
Share on other sites

There are many reasons for not doing it.

  • Bandwidth being one of them.
  • Troubleshooting
  • Performance; generally it is faster to have SQL local.

Remember that CM12 and WSUS is very chatty.

 

How many computers are you managing?

Share this post


Link to post
Share on other sites

There are many reasons for not doing it.

  • Bandwidth being one of them.
  • Troubleshooting
  • Performance; generally it is faster to have SQL local.

Remember that CM12 and WSUS is very chatty.

 

How many computers are you managing?

 

In my All Systems collection, currently there are 1937 computers. I would not expect that number to grow very rapidly for us. The troubleshooting aspect is what worries me about having the 2 DBs on the same instance. Since SQL is by no means my strong suit, if we ran into performance issues in the future, I imagine it would be very difficult to pinpoint them. But let's just assume for now that we have to go with external SQL since that's how every other SQL server in our company operates, and since it's already built. But I am just looking for a solid reason from a member of the community here to recommend to my DBA that we go with separate instances for the two databases, if one exists.

Share this post


Link to post
Share on other sites

You will have more problems with remote SQL then you will ever has sharing one instance for CM12 and WSUS. Don't forget to install SSRS too.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...