A request that we receive that CPSM running slowly or that there is a very high load on the SQL server. This can sometimes be attributed to send ADSync so many requests that it causes an impact on the server.
for provisioning protocols of search will give you a good idea of how many successful or unsuccessful provisioning requests have been made for ADSync. However, there could be many ADSync requests that are rejected before it's to a provisioning request by the API due to validation problems.
The following article steps to configure a SQL Trace on the OLM database provides the calls of the trace API provided by a ADSync client for user requests.
Background Information
If ADSync attempt to synchronize, the API a SQL lookup the remote user SID in the database. With this knowledge we can pursue these lookups and find out how many times a customer requests the API.
There is no cover track contacts or distribution groups.
Setting the Profiler trace.
to connect to your SQL Server.
Open SQL Server Profiler.
Click File> New Trace
Specify credentials required for the SQL Server / Instance containing the CPSM OLM database
in the Trace Properties screen, click Save on the Table.
In the table field set the OLM database
in ZADSyncStats (this can be changed, just remember to change the query)
Click OK
look the trace features page is as reflect the change.
Click "all columns" on the bottom right
Back to the right and click on the heading "Database"
in As field in OLM put
Scroll down the filter box down and find the filter called "text Data"
in the Like- field in exec put sp_UserSearch2 @property%
Click OK
Click Run.
Run. The track for 5 minutes, and you will see data in the track, and it will also be fitted in the ZADSyncStats
to query the data.
Open SQL Server Management Studio.
to the instance in connection with the OLM database on them.
, the following query to get the number of requests per client show.
you should change the start time to the area to try on the image.
with customer info (customerid, start time)
AS
(
select substring (CAST (text data as nvarchar (max)), PATINDEX ( '% CustomerID =%', CAST (text data as nvarchar (max))) + 11, PATINDEX ( '% @ Property%', CAST (text data as nvarchar (max))) - (PATINDEX ( '% CustomerID =%', CAST (text data as nvarchar (max) )) + 11)) as CustomerID Start Time oF ZADSyncStats
WHERE text Data is nonzero
)
SELECT ci.customerid, cu.name, cu.label, COUNT (*) queries from customerinfo ci
INNER JOIN customers cu
ON ci.customerid = cu.customerid
WHERE start time between "25/11/2014 09:30:00" and "13/08/2014 12: 30:00 '
GROUP BY ci.customerid, cu.name, cu.label
ORDER BY queries from
example
In this example, client 29 sent 1,237 while customers 28 sent requests 3.
it does not mean that there occurs a problem for customers is 29 might be, they add additional users, forced a password change and users log on to update for the day.
Conclusion
While this beat an insight into the ADSync requests your SQL Server and provides a good starting point to check which customers might have ADSync problems, it does not give that a ADSync Client the customer is not working properly.
you could password-update for all users forced or even onboard new users.
In a later article I by the ADSync customers and troubleshooting created to discuss the possible burden to mitigate tips.
0 Komentar