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
- 310 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
Two rows with ecid=0 for one NAV user in sysprocess view
Zdenal
Member Posts: 6
Hello,
I have SQL log table with informations about users logged to NAV (version 5). These informations are from SQL view sysprocesses.
In very few cases there are two rows for the same user, the same spid and host. User is logged to DatabaseA with NAV client, so why there is the same connection with the same spid to DatabaseB (DatabaseB is also NAV database, but sometimes there is master or tempdb instead of DatabaseB). In WHERE condition I also have ecid=0, so why two rows?
spid User ID Login Time Database Name Application Name Host Name
120 UserA 2013-05-14 07:38:26.843 DatabaseA Microsoft Dynamics NAV client HostA
120 UserA 2013-05-14 07:38:26.843 DatabaseB Microsoft Dynamics NAV client HostA
Anybody any suggestion, please?
I have SQL log table with informations about users logged to NAV (version 5). These informations are from SQL view sysprocesses.
In very few cases there are two rows for the same user, the same spid and host. User is logged to DatabaseA with NAV client, so why there is the same connection with the same spid to DatabaseB (DatabaseB is also NAV database, but sometimes there is master or tempdb instead of DatabaseB). In WHERE condition I also have ecid=0, so why two rows?
spid User ID Login Time Database Name Application Name Host Name
120 UserA 2013-05-14 07:38:26.843 DatabaseA Microsoft Dynamics NAV client HostA
120 UserA 2013-05-14 07:38:26.843 DatabaseB Microsoft Dynamics NAV client HostA
Anybody any suggestion, please?
0