Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 304 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Business Central version 15 (On-premise) - Long Running Queries
bbrown
Member Posts: 3,268
Statement: BeginTransaction IsolationLevel=65536
I am seeing random occurrences of the above statement noted as "long running SQL statement" in the service tier's event viewer. I sent this to MS and all I got back was the definition for Repeatable Read. I know what that is. What I'm trying to dig into is shy these take so long. Any thoughts or ideas on what to look at are welcome.
Also seeing entries like Statement: Commit.
I am seeing random occurrences of the above statement noted as "long running SQL statement" in the service tier's event viewer. I sent this to MS and all I got back was the definition for Repeatable Read. I know what that is. What I'm trying to dig into is shy these take so long. Any thoughts or ideas on what to look at are welcome.
Also seeing entries like Statement: Commit.
There are no bugs - only undocumented features.
0