Progress Reports Data Columns
The Progress Reports event category has the following event classes:
| Event ID | Event Name | Event Description |
|---|---|---|
| 5 | Progress Report Begin | Progress report begin. |
| 6 | Progress Report End | Progress report end. |
| 7 | Progress Report Current | Progress report current. |
| 8 | Progress Report Error | Progress report error. |
The following tables list the data columns for each of these event classes.
Progress Report Begin–Data Columns
| Column Name | Column Id | Column Type | Column Description |
|---|---|---|---|
| EventClass | 0 | 1 | Event Class is used to categorize events. |
| EventSubclass | 1 | 1 | Event Subclass provides additional information about each event class. The following are valid Sub Class Id: Sub Class Name pairs: 1: Process 2: Merge 3: Delete 4: DeleteOldAggregations 5: Rebuild 6: Commit 7: Rollback 8: CreateIndexes 9: CreateTable 10: InsertInto 11: Transaction 12: Initialize 13: Discretize 14: Query 15: CreateView 16: WriteData 17: ReadData 18: GroupData 19: GroupDataRecord 20: BuildIndex 21: Aggregate 22: BuildDecode 23: WriteDecode 24: BuildDMDecode 25: ExecuteSQL 26: ExecuteModifiedSQL 27: Connecting 28: BuildAggsAndIndexes 29: MergeAggsOnDisk 30: BuildIndexForRigidAggs 31: BuildIndexForFlexibleAggs 32: WriteAggsAndIndexes 33: WriteSegment 34: DataMiningProgress 35: ReadBufferFullReport 36: ProactiveCacheConversion 37: Backup 38: Restore 39: Synchronize 40: Build Processing Schedule 41: Detach 42: Attach 43: Analyze\Encode Data 44: Compress Segment 45: Write Table Column 46: Relationship Build Prepare 47: Build Relationship Segment 48: Load 49: Metadata Load 50: Data Load 51: Post Load 52: Metadata traversal during Backup 53: VertiPaq 54: Hierarchy processing 55: Switching dictionary 57: Tabular transaction commit 58: Sequence point 59: Tabular object processing 60: Saving database 61: Tokenization store processing 63: Check segment indexes 64: Check tabular data structure 65: Check column data for duplicates or null values |
| CurrentTime | 2 | 5 | Contains the current time of the reported event, when available. For filtering, expected formats are 'YYYY-MM-DD' and 'YYYY-MM-DD HH:MM:SS'. |
| StartTime | 3 | 5 | Contains the time at which the event started, when available. For filtering, expected formats are 'YYYY-MM-DD' and 'YYYY-MM-DD HH:MM:SS'. |
| JobID | 7 | 1 | Contains the job ID associated with the reported event. |
| SessionType | 8 | 8 | Contains the session type (the entity causing the event) associated with the reported event. For processing events, values are: 1= User 2= Proactive Caching 3= Lazy processing |
| ObjectID | 11 | 8 | Contains the object ID (a string) associated with the reported event. |
| ObjectType | 12 | 1 | Contains the object type. |
| ObjectName | 13 | 8 | Contains the name of the object associated with the reported event. |
| ObjectPath | 14 | 8 | Contains the object path for the object associated with the reported event, as a comma-separated list of parents starting with the object's parents. |
| ObjectReference | 15 | 8 | Contains the object reference for the reported event, encoded as XML for all parents and using tags to describe the object. |
| ConnectionID | 25 | 1 | Contains the unique connection ID associated with the reported event. |
| DatabaseName | 28 | 8 | Contains the name of the database in which the reported event occurred. |
| NTUserName | 32 | 8 | Contains the user name associated with the command event. Depending on the environment, the user name is in the following form: - Windows user account (DOMAIN\UserName) - User Principal Name (UPN) (username@domain.com) - Service Principal Name (SPN) (appid@tenantid) - Power BI Service Account (Power BI Service) - Power BI Service on behalf of a UPN or SPN (Power BI Service (UPN/SPN)) |
| NTDomainName | 33 | 8 | Contains the domain name associated with the user account that triggered the command event. - Windows domain name for Windows user accounts - AzureAD for Microsoft Entra accounts - NT AUTHORITY accounts without a Windows domain name, such as the Power BI service |
| SessionID | 39 | 8 | Contains the session ID associated with the reported event. |
| NTCanonicalUserName | 40 | 8 | Contains the user name associated with the command event. Depending on the environment, the user name is in the following form: - Windows user account (DOMAIN\UserName) - User Principal Name (UPN) (username@domain.com) - Service Principal Name (SPN) (appid@tenantid) - Power BI Service Account (Power BI Service) |
| SPID | 41 | 1 | Contains the server process ID (SPID) that uniquely identifies the user session associated with the reported event. The SPID directly corresponds to the session GUID used by XML for Analysis (XMLA). |
| TextData | 42 | 9 | Contains the text data associated with the reported event. |
| ServerName | 43 | 8 | Contains the name of the instance on which the reported event occurred. |
Progress Report End–Data Columns
| Column Name | Column Id | Column Type | Column Description |
|---|---|---|---|
| EventClass | 0 | 1 | Event Class is used to categorize events. |
| EventSubclass | 1 | 1 | Event Subclass provides additional information about each event class. The following are valid Sub Class Id: Sub Class Name pairs: 1: Process 2: Merge 3: Delete 4: DeleteOldAggregations 5: Rebuild 6: Commit 7: Rollback 8: CreateIndexes 9: CreateTable 10: InsertInto 11: Transaction 12: Initialize 13: Discretize 14: Query 15: CreateView 16: WriteData 17: ReadData 18: GroupData 19: GroupDataRecord 20: BuildIndex 21: Aggregate 22: BuildDecode 23: WriteDecode 24: BuildDMDecode 25: ExecuteSQL 26: ExecuteModifiedSQL 27: Connecting 28: BuildAggsAndIndexes 29: MergeAggsOnDisk 30: BuildIndexForRigidAggs 31: BuildIndexForFlexibleAggs 32: WriteAggsAndIndexes 33: WriteSegment 34: DataMiningProgress 35: ReadBufferFullReport 36: ProactiveCacheConversion 37: Backup 38: Restore 39: Synchronize 40: Build Processing Schedule 41: Detach 42: Attach 43: Analyze\Encode Data 44: Compress Segment 45: Write Table Column 46: Relationship Build Prepare 47: Build Relationship Segment 48: Load 49: Metadata Load 50: Data Load 51: Post Load 52: Metadata traversal during Backup 53: VertiPaq 54: Hierarchy processing 55: Switching dictionary 57: Tabular transaction commit 58: Sequence point 59: Tabular object processing 60: Saving database 61: Tokenization store processing 63: Check segment indexes 64: Check tabular data structure 65: Check column data for duplicates or null values 66: Analyze refresh policy impact for tabular partition 67: Parallel session 68: Auto aggs training 69: AutoAggs cardinality analysis 70: Export |
| CurrentTime | 2 | 5 | Contains the current time of the reported event, when available. For filtering, expected formats are 'YYYY-MM-DD' and 'YYYY-MM-DD HH:MM:SS'. |
| StartTime | 3 | 5 | Contains the time at which the event started, when available. For filtering, expected formats are 'YYYY-MM-DD' and 'YYYY-MM-DD HH:MM:SS'. |
| EndTime | 4 | 5 | Contains the time at which the event ended. This column is not populated for starting event classes, such as SQL:BatchStarting or SP:Starting. For filtering, expected formats are 'YYYY-MM-DD' and 'YYYY-MM-DD HH:MM:SS'. |
| Duration | 5 | 2 | Contains the elapsed amount of time (in milliseconds) taken by the event. |
| CPUTime | 6 | 2 | Contains the amount of CPU time (in milliseconds) used by the event. |
| JobID | 7 | 1 | Contains the job ID associated with the reported event. |
| SessionType | 8 | 8 | Contains the session type (the entity causing the event) associated with the reported event. For processing events, values are: 1= User 2= Proactive Caching 3= Lazy processing |
| ProgressTotal | 9 | 1 | Contains the progress total for the reported event. |
| IntegerData | 10 | 1 | Contains the integer data associated with the reported event, such as the current count of the number of rows processed for a processing event. |
| ObjectID | 11 | 8 | Contains the object ID (a string) associated with the reported event. |
| ObjectType | 12 | 1 | Contains the object type. |
| ObjectName | 13 | 8 | Contains the name of the object associated with the reported event. |
| ObjectPath | 14 | 8 | Contains the object path for the object associated with the reported event, as a comma-separated list of parents starting with the object's parents. |
| ObjectReference | 15 | 8 | Contains the object reference for the reported event, encoded as XML for all parents and using tags to describe the object. |
| Severity | 22 | 1 | Contains the severity level of an exception associated the reported event. Values are: 0 = Success 1 = Informational 2 = Warning 3 = Error |
| Success | 23 | 1 | Contains the success or failure of the server reported event. Values are: 0 = Failure 1 = Success |
| Error | 24 | 1 | Contains the error number of a given event. |
| ConnectionID | 25 | 1 | Contains the unique connection ID associated with the reported event. |
| DatabaseName | 28 | 8 | Contains the name of the database in which the reported event occurred. |
| NTUserName | 32 | 8 | Contains the user name associated with the command event. Depending on the environment, the user name is in the following form: - Windows user account (DOMAIN\UserName) - User Principal Name (UPN) (username@domain.com) - Service Principal Name (SPN) (appid@tenantid) - Power BI Service Account (Power BI Service) - Power BI Service on behalf of a UPN or SPN (Power BI Service (UPN/SPN)) |
| NTDomainName | 33 | 8 | Contains the Windows domain account associated with the reported event. |
| SessionID | 39 | 8 | Contains the session ID associated with the reported event. |
| NTCanonicalUserName | 40 | 8 | Contains the user name associated with the command event. Depending on the environment, the user name is in the following form: - Windows user account (DOMAIN\UserName) - User Principal Name (UPN) (username@domain.com) - Service Principal Name (SPN) (appid@tenantid) - Power BI Service Account (Power BI Service) |
| SPID | 41 | 1 | Contains the server process ID (SPID) that uniquely identifies the user session associated with the reported event. The SPID directly corresponds to the session GUID used by XML for Analysis (XMLA). |
| TextData | 42 | 9 | Contains the text data associated with the reported event. |
| ServerName | 43 | 8 | Contains the name of the instance on which the reported event occurred. |
Progress Report Current–Data Columns
| Column Name | Column Id | Column Type | Column Description |
|---|---|---|---|
| EventClass | 0 | 1 | Event Class is used to categorize events. |
| EventSubclass | 1 | 1 | Event Subclass provides additional information about each event class. The following are valid Sub Class Id: Sub Class Name pairs: 1: Process 2: Merge 3: Delete 4: DeleteOldAggregations 5: Rebuild 6: Commit 7: Rollback 8: CreateIndexes 9: CreateTable 10: InsertInto 11: Transaction 12: Initialize 13: Discretize 14: Query 15: CreateView 16: WriteData 17: ReadData 18: GroupData 19: GroupDataRecord 20: BuildIndex 21: Aggregate 22: BuildDecode 23: WriteDecode 24: BuildDMDecode 25: ExecuteSQL 26: ExecuteModifiedSQL 27: Connecting 28: BuildAggsAndIndexes 29: MergeAggsOnDisk 30: BuildIndexForRigidAggs 31: BuildIndexForFlexibleAggs 32: WriteAggsAndIndexes 33: WriteSegment 34: DataMiningProgress 35: ReadBufferFullReport 36: ProactiveCacheConversion 37: Backup 38: Restore 39: Synchronize 40: Build Processing Schedule 41: Detach 42: Attach 43: Analyze\Encode Data 44: Compress Segment 45: Write Table Column 46: Relationship Build Prepare 47: Build Relationship Segment 48: Load 49: Metadata Load 50: Data Load 51: Post Load 52: Metadata traversal during Backup 53: VertiPaq 54: Hierarchy processing 55: Switching dictionary 57: Tabular transaction commit 58: Sequence point 59: Tabular object processing 60: Saving database 61: Tokenization store processing 63: Check segment indexes 64: Check tabular data structure 65: Check column data for duplicates or null values |
| CurrentTime | 2 | 5 | Contains the current time of the reported event, when available. For filtering, expected formats are 'YYYY-MM-DD' and 'YYYY-MM-DD HH:MM:SS'. |
| StartTime | 3 | 5 | Contains the time at which the event started, when available. For filtering, expected formats are 'YYYY-MM-DD' and 'YYYY-MM-DD HH:MM:SS'. |
| JobID | 7 | 1 | Contains the job ID associated with the reported event. |
| SessionType | 8 | 8 | Contains the session type (the entity causing the event) associated with the reported event. For processing events, values are: 1= User 2= Proactive Caching 3= Lazy processing |
| ProgressTotal | 9 | 1 | Contains the progress total for the reported event. |
| IntegerData | 10 | 1 | Contains the integer data associated with the reported event, such as the current count of the number of rows processed for a processing event. |
| ObjectID | 11 | 8 | Contains the object ID (a string) associated with the reported event. |
| ObjectType | 12 | 1 | Contains the object type. |
| ObjectName | 13 | 8 | Contains the name of the object associated with the reported event. |
| ObjectPath | 14 | 8 | Contains the object path for the object associated with the reported event, as a comma-separated list of parents starting with the object's parents. |
| ObjectReference | 15 | 8 | Contains the object reference for the reported event, encoded as XML for all parents and using tags to describe the object. |
| ConnectionID | 25 | 1 | Contains the unique connection ID associated with the reported event. |
| DatabaseName | 28 | 8 | Contains the name of the database in which the reported event occurred. |
| SessionID | 39 | 8 | Contains the session ID associated with the reported event. |
| SPID | 41 | 1 | Contains the server process ID (SPID) that uniquely identifies the user session associated with the reported event. The SPID directly corresponds to the session GUID used by XML for Analysis (XMLA). |
| TextData | 42 | 9 | Contains the text data associated with the reported event. |
| ServerName | 43 | 8 | Contains the name of the instance on which the reported event occurred. |
Progress Report Error–Data Columns
| Column Name | Column Id | Column Type | Column Description |
|---|---|---|---|
| EventClass | 0 | 1 | Event Class is used to categorize events. |
| EventSubclass | 1 | 1 | Event Subclass provides additional information about each event class. The following are valid Sub Class Id: Sub Class Name pairs: 1: Process 2: Merge 3: Delete 4: DeleteOldAggregations 5: Rebuild 6: Commit 7: Rollback 8: CreateIndexes 9: CreateTable 10: InsertInto 11: Transaction 12: Initialize 13: Discretize 14: Query 15: CreateView 16: WriteData 17: ReadData 18: GroupData 19: GroupDataRecord 20: BuildIndex 21: Aggregate 22: BuildDecode 23: WriteDecode 24: BuildDMDecode 25: ExecuteSQL 26: ExecuteModifiedSQL 27: Connecting 28: BuildAggsAndIndexes 29: MergeAggsOnDisk 30: BuildIndexForRigidAggs 31: BuildIndexForFlexibleAggs 32: WriteAggsAndIndexes 33: WriteSegment 34: DataMiningProgress 35: ReadBufferFullReport 36: ProactiveCacheConversion 37: Backup 38: Restore 39: Synchronize 40: Build Processing Schedule 41: Detach 42: Attach 43: Analyze\Encode Data 44: Compress Segment 45: Write Table Column 46: Relationship Build Prepare 47: Build Relationship Segment 48: Load 49: Metadata Load 50: Data Load 51: Post Load 52: Metadata traversal during Backup 53: VertiPaq 54: Hierarchy processing 55: Switching dictionary 57: Tabular transaction commit 58: Sequence point 59: Tabular object processing 60: Saving database 61: Tokenization store processing 63: Check segment indexes 64: Check tabular data structure 65: Check column data for duplicates or null values |
| CurrentTime | 2 | 5 | Contains the current time of the reported event, when available. For filtering, expected formats are 'YYYY-MM-DD' and 'YYYY-MM-DD HH:MM:SS'. |
| StartTime | 3 | 5 | Contains the time at which the event started, when available. For filtering, expected formats are 'YYYY-MM-DD' and 'YYYY-MM-DD HH:MM:SS'. |
| EndTime | 4 | 5 | Contains the time at which the event ended. This column is not populated for starting event classes, such as SQL:BatchStarting or SP:Starting. For filtering, expected formats are 'YYYY-MM-DD' and 'YYYY-MM-DD HH:MM:SS'. |
| Duration | 5 | 2 | Contains the elapsed amount of time (in milliseconds) taken by the event. |
| JobID | 7 | 1 | Contains the job ID associated with the reported event. |
| SessionType | 8 | 8 | Contains the session type (the entity causing the event) associated with the reported event. For processing events, values are: 1= User 2= Proactive Caching 3= Lazy processing |
| ProgressTotal | 9 | 1 | Contains the progress total for the reported event. |
| IntegerData | 10 | 1 | Contains the integer data associated with the reported event, such as the current count of the number of rows processed for a processing event. |
| ObjectID | 11 | 8 | Contains the object ID (a string) associated with the reported event. |
| ObjectType | 12 | 1 | Contains the object type. |
| ObjectName | 13 | 8 | Contains the name of the object associated with the reported event. |
| ObjectPath | 14 | 8 | Contains the object path for the object associated with the reported event, as a comma-separated list of parents starting with the object's parents. |
| ObjectReference | 15 | 8 | Contains the object reference for the reported event, encoded as XML for all parents and using tags to describe the object. |
| Severity | 22 | 1 | Contains the severity level of an exception associated the reported event. Values are: 0 = Success 1 = Informational 2 = Warning 3 = Error |
| Error | 24 | 1 | Contains the error number of a given event. |
| ConnectionID | 25 | 1 | Contains the unique connection ID associated with the reported event. |
| DatabaseName | 28 | 8 | Contains the name of the database in which the reported event occurred. |
| SessionID | 39 | 8 | Contains the session ID associated with the reported event. |
| SPID | 41 | 1 | Contains the server process ID (SPID) that uniquely identifies the user session associated with the reported event. The SPID directly corresponds to the session GUID used by XML for Analysis (XMLA). |
| TextData | 42 | 9 | Contains the text data associated with the reported event. |
| ServerName | 43 | 8 | Contains the name of the instance on which the reported event occurred. |
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for