Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Netflow Traffic Analyzer (NTA) > NTA - Knowledgebase Articles > Zero values in the cbQoSStats table

Zero values in the cbQoSStats table

Table of contents

Updated January 5, 2017

Overview

This article explains the behavior of the cbQoSStats with respect to zero CBQoS drops being polled.

Environment

All NTA versions

Detail

Earlier NTA versions

The cbQOSStats table is slightly different from other tables storing polled data. The time frames in the table will vary. Normally with Orion tables storing data, the StartDate is the time when the information was polled, while EndDate is the time when new data is retrieved. In such scenarios, with a five-minute polling interval, the EndDate-StardDate would be five minutes. To optimize performance by lowering the number of rows in the cbQOSStats table, it was decided to prolong EndDate time for 0 values if they are repeating multiple times. 

 

NTA 4.2.1

In later versions of NTA, the zero entries in the cbQoSStats table are at longest an hour apart.

 

 

 

 
 

 

Last modified

Tags

Classifications

Public