Anyone had issues with users accessing reports in 1606 with SQL 2014? This is a brand new install. Only the user who performed the install can view reports in SSRS. Other full administrators get access denied.
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Phil Schwan Sent: Monday, September 19, 2016 10:52 AM To: firstname.lastname@example.org Subject: [mssms] RE: SCCM 2012 - 1606 Upgrade - Package folder slow [This message is from outside Bradley. Exercise caution in opening attachments or links.] 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> [mailto:listsad...@lists.myitforum.com] On Behalf Of Robert Spinelli Sent: Monday, September 19, 2016 11:23 AM To: email@example.com<mailto:firstname.lastname@example.org> 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 ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer.