I would like to know why each user that logs in to the application creates multiple session id's to the system and data databases. This also happens for each screen a user opens resulting in a user having over 22 individule sessions to the databases. Is i possible to decrease the number of user sessions?
I see you have a case open for this issue, Will you please update this forum post with the resolution from your case when it is resolved .
Technical Support Engineer
**This posting is provided " AS - IS" with no warranties and confers no rights.
Sure will Blaine.
Sorry for the late reply but this is the email I got from support.
I was able to get an answer from the team without having to go to the development team. This is a question that’s been asked of the team before, just not to me personally. Unfortunately, it is what it is. That is the way that SL creates the connections and there isn’t another way to change it. The issue you are seeing with the waiting might be because there are users trying to access the same table/record at the same time and one user would be locked out of the table until the other user’s process had completed. You could get around this issue by setting stored procedures to “no lock”, however it’s possible that could cause data corruption.
I’m sorry that this is the case, and that there isn’t a way around it. I’m also limited on getting further information, as it appears you are running Microsoft Dynamics SL 7.0 which is in extended support. This means that break fixes, etc. will still be supported, however there will be no further development activity on the product version. Please let me know if you have any further questions for me and I’ll do my best to answer them.
Other Microsoft Sites
I'm a Customer
I'm a Partner
Follow Microsoft Dynamics