We sync certain user information during the login phase, and we do this based on the last sync date which is stored in the DDS. But upon checking the SQL Profiler, I can see a SQL call being called many times to look at the last sync date from the DDS. I was expecting this to be cached and hence only trigger the SQL once and then look into the cache for subsequent requets. We have a standard implementation for this in many of our projects and have never faced an issue before, is there any setting or configuration that we can check to make sure the DDS cache is being populated.
Hi,
We sync certain user information during the login phase, and we do this based on the last sync date which is stored in the DDS. But upon checking the SQL Profiler, I can see a SQL call being called many times to look at the last sync date from the DDS. I was expecting this to be cached and hence only trigger the SQL once and then look into the cache for subsequent requets. We have a standard implementation for this in many of our projects and have never faced an issue before, is there any setting or configuration that we can check to make sure the DDS cache is being populated.