Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K 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
- 269 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 SQL Performance
- 33 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Service Tier in NAV 2013 and Above Keeps "Updating" Database CONTINUOUSLY, even if no Clients Using
OldNavDog
Member Posts: 88
Hi,
We develop Add-Ons for NAV. As such, we have many (over 750) NAV DBs from various version scattered about on several Servers.
I found a wonderful little SQL script (Query) that can "report" on several types of "User" Access to a DB. BUT... Even if I restrict that Query to just show User "Updates" to the DB, it seems that any DB of version 2013 or later that has a "Running" Service Tier, it shows "User Update" Date/Time is essentially the Current Date/Time. This MUST mean that the Service Tier is beating-up on the DB CONTINUOUSLY, even if there are no "Clients" logged into the DB through NAV.
1. Is this true? I know it isn't a big deal for most people, that may only have 1 or 2 Service Tier "Instances" running; but it still seems like a bad design.
2. Is there any setting (there ARE lots of settings, afterall!) on the Service Tier that can stop that behavior when no one is logged-in?
Thanks In Advance!
We develop Add-Ons for NAV. As such, we have many (over 750) NAV DBs from various version scattered about on several Servers.
I found a wonderful little SQL script (Query) that can "report" on several types of "User" Access to a DB. BUT... Even if I restrict that Query to just show User "Updates" to the DB, it seems that any DB of version 2013 or later that has a "Running" Service Tier, it shows "User Update" Date/Time is essentially the Current Date/Time. This MUST mean that the Service Tier is beating-up on the DB CONTINUOUSLY, even if there are no "Clients" logged into the DB through NAV.
1. Is this true? I know it isn't a big deal for most people, that may only have 1 or 2 Service Tier "Instances" running; but it still seems like a bad design.
2. Is there any setting (there ARE lots of settings, afterall!) on the Service Tier that can stop that behavior when no one is logged-in?
Thanks In Advance!
Experience is what you get, when you don't get what you want. --Anon.
0
Answers
It is true, at least 2 processes for stillAliveDiffTime and lastKnownTimeStamp.
I don't see any settings/options to disable those.