Skip to main content
Solved

Slow IAM sync of roles version 2025.1

  • April 18, 2025
  • 1 reply
  • 23 views

Forum|alt.badge.img

I am upgrading our SF to version 2025.1 (from version 2023.1) and i am running some test upgrades to see how smoothly this will go and what the changes are. We are running on SQL Server 2019.

I noticed that when i do an iam synchronisation of a β€œnew” branch to an IAM that this executes faster than before πŸ˜€. But when i change some roles and do an IAM synchronisation of an existing branch in the target IAM that the synchronisation process takes forever.  

In the example above i stopped the process because it took to long. 

In Management Studio i see it is working on this query. The role_tab_variant_look_up table has more than 750k lines.

Also in general i occasionally experience that merge statements sometimes take very long.

Anyone else ever experienced the same problems and fixed it.

Best answer by Mark Jongeling

Hi,

We have noticed that the 2025.1 way of processing the synchronized data inside IAM can sometimes become slow due to SQL Server's way of dealing with the data. We have optimized that for 2025.2 luckily, but I understand that is a bit of a long wait when you are experiencing these kind of performance related issues.

We did have a ticket on this topic that experiences a similar thing which triggered the optimalization for 2025.2. I'll make sure to release the improved code for this particular procedure as a platform improvement to resolve this for you and potentially others.

Edit: improvement has been released: 

 

View original
Did this topic help you find an answer to your question?

1 reply

Mark Jongeling
Administrator
Forum|alt.badge.img+23
  • Administrator
  • 3945 replies
  • Answer
  • April 18, 2025

Hi,

We have noticed that the 2025.1 way of processing the synchronized data inside IAM can sometimes become slow due to SQL Server's way of dealing with the data. We have optimized that for 2025.2 luckily, but I understand that is a bit of a long wait when you are experiencing these kind of performance related issues.

We did have a ticket on this topic that experiences a similar thing which triggered the optimalization for 2025.2. I'll make sure to release the improved code for this particular procedure as a platform improvement to resolve this for you and potentially others.

Edit: improvement has been released: 

 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings