Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
I am seeing at least 20 to 30 sleeping SQL connections with update number sequence table on SQL idle in a random pattern.
We dont see any users complaining about the number sequence on any modules. However I would still like to investigate the issue to avoid any future issues.
UPDATE NUMBERSEQUENCETABLE SET NEXTREC=@P1,RECVERSION=@P2,MODIFIEDTRANSACTIONID=@P3 WHERE ((RECID=@P4) AND (RECVERSION=@P5))
Has anyone come across this issue before.
Sleeping sessions are not really an issue unless there will be too many... Read this blog: littlekendra.com/.../confused-by-sp_who2-dear-sql-dba-episode-30
Thank you Andre for sharing your thoughts!!!
I haven't seen this behavior in any of the environments except production. I see these counts adding up gradually about 20 sessions in 4 hours on the same update statement
I did sql profiler to capture the updates on the numbersequence table not all the updates are ending in sleeping state.
I suspect if the update statements are orphaned by the AOS servers for any reason.
I have seen sleeping sessions in the past, but never paid that much attention what statement was executed then.
Monitoring further below is what i found in the event viewer of AOS servers
Object Server 01: The database reported (session 40 (admin)): [Microsoft][SQL Server Native Client 10.0]Communication link failure. The SQL statement was: ""
It might indicate that connections are not stable. I would suggest to find similar events to see if this was an incident or a recurring issue.
you are right, The SQL server has two Nic connecting one to the DR site. The DNS is registered with two ip address on the SQL server FQDN.
The AOS servers are not able to reach the SQL server with the DR(IP address). I added a host entry on the AOS servers to force connecting the SQL on the primary ip address. Hoping this should solve the issue
I dont see any orphaned sessions for the past 15 hours. I will keep you posted.
Thank you for your help and valuable suggestions. Highly appreciated!!
Business Applications communities