Breaking news from around the world
Get the Bing + MSN extension
End of mainstream support for Microsoft Dynamics AX 2009, 2012, and 2012Mainstream support for Dynamics AX 2009 Service Pack 1 (SP1), Dynamics AX 2012, and Dynamics AX 2012 R2 ended Oct. 9, 2018. After that date, only security hotfixes will be provided for these three versions through the extended support period that until Oct. 12, 2021. Read more
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Talent 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