Is the performance issue just with SQL Replication between Site Servers? Or is 
it more systemic than that?
By chance do you have any links with more info?
Regards-S

From: philsch...@hotmail.com
To: mssms@lists.myitforum.com
Subject: [mssms] RE: SCCM 2012 - 1606 Upgrade - Package folder slow
Date: Mon, 19 Sep 2016 15:51:39 +0000









What version of SQL?  IIRC, there are known performance issues with SQL 
2014/2016 and SCCM 1606.  You’ll want to set the DB compatibility level to SQL 
2012 using the following (where CM_XXX is your SCCM database):
 
ALTER DATABASE CM_XXX
SET COMPATIBILITY_LEVEL = 110;
GO
 
-Phil
 
 
 



From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com]
On Behalf Of Robert Spinelli

Sent: Monday, September 19, 2016 11:23 AM

To: mssms@lists.myitforum.com

Subject: [mssms] SCCM 2012 - 1606 Upgrade - Package folder slow


 
We upgraded from SCCM 2012 – 1606 this weekend and now when you go into the 
packages root node its taking 3-4 minutes to return the default 1000 packages 
list.  When we had 2012 it took maybe 10 seconds to return them.  Anyone else 
see
 this when they upgraded?
 
We were planning on doing 1606 Rollup 1 also but ran into replication issues 
between the CAS and 3 primaries.  I hate having a CAS but since 2012 only 
supported 100k we had to go with it.  I know SCCM CB supports 175k clients per 
primary
 now so maybe one day we can collapse everything to 1 primary but that’s not 
going to happen for a while.
 
Thanks
 
Rob
 





                                          


Reply via email to