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 > Are there any differences in the way CBQoS data are handled

Are there any differences in the way CBQoS data are handled

Table of contents

Updated January 12, 2017

Overview

Are there any differences in the way CBQoS data are handled?

 

Environment

  • NTA 4.x

Detail

There is no fundamental change in the way CBQoS data is handled, between 3.x and 4.x: In both, the default polling period is 300 sec, and the CBQoS data are retained for the configured retention period.

 

The difference is in the displaying, because NTA 3.x was aggregating the CBQoS data consistently with the Flow data, in order to provide chart consistency. In NTA 4.x, the CBQoS aggregation has been removed in order to show as-polled data. It will therefore show more granular data than 3.x, even if the polling and retention period remains the same as in 3.x (no database sizing difference due to CBQoS between 3.x and 4.x).

 

 

 

Last modified

Tags

Classifications

Public
/*]]>*/