Skip to content

When the @get_additional_info=1 parameter is passed, it replaces the hexadecimal job step identifier with the actual job name. #133

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
mfuller333 wants to merge 1 commit into
base: master
Choose a base branch
from
Open

When the @get_additional_info=1 parameter is passed, it replaces the hexadecimal job step identifier with the actual job name. #133

mfuller333 wants to merge 1 commit into from

Conversation

@mfuller333
Copy link
Contributor

@mfuller333 mfuller333 commented Sep 21, 2025 •
edited
Loading

When the parameter is passed, the system now reveals the actual job name in the field—replacing hex step identifiers. This improvement makes it significantly easier to identify and understand running processes at a glance.

@mfuller333
When you pass in the parameter @get_additional_info=1, it switches th…
26eab2d 
…e program_name job step hex "SQLAgent - TSQL JobStep (Job 0x9C6ADAEF6E1A4F458032492E97TA7C9 : Step 1)" to the actual job name for example in this case "SQL Job = Replication monitoring refresher for distribution." Which makes it easier to understand what I am looking at. This is resolves an old issue.
@mfuller333 mfuller333 changed the title When the parameter is passed, it replaces the hexadecimal job step identifier—such as —with the actual job name. For example, in this case, it becomes This enhancement makes it much easier to interpret the job context and resolves a longstanding issue. When the parameter is passed, it replaces the hexadecimal job step identifier—such as —with the actual job name. Enhancement makes it much easier to interpret the job context and resolves a longstanding issue. Sep 21, 2025
@mfuller333 mfuller333 changed the title When the parameter is passed, it replaces the hexadecimal job step identifier—such as —with the actual job name. Enhancement makes it much easier to interpret the job context and resolves a longstanding issue. When the parameter is passed, it replaces the hexadecimal job step identifier such as "SQLAgent - TSQL JobStep (Job 0x9C6ADAEF6E1A4F4580324E97CEA7C9 : Step 1)" with the actual job name. Enhancement makes it much easier to interpret the job context and resolves a longstanding issue. Sep 21, 2025
@mfuller333 mfuller333 changed the title When the parameter is passed, it replaces the hexadecimal job step identifier such as "SQLAgent - TSQL JobStep (Job 0x9C6ADAEF6E1A4F4580324E97CEA7C9 : Step 1)" with the actual job name. Enhancement makes it much easier to interpret the job context and resolves a longstanding issue. When the parameter is passed, it replaces the hexadecimal job step identifier such as "SQLAgent - TSQL JobStep (Job 0x9C6ADAEF6E1A4F4580324E97CEA7C9 : Step 1)" with the actual job name. Enhancement makes it much easier to interpret the job context and resolves a longstanding issue. #66 Sep 21, 2025
@mfuller333 mfuller333 changed the title When the parameter is passed, it replaces the hexadecimal job step identifier such as "SQLAgent - TSQL JobStep (Job 0x9C6ADAEF6E1A4F4580324E97CEA7C9 : Step 1)" with the actual job name. Enhancement makes it much easier to interpret the job context and resolves a longstanding issue. #66 When the @get_additional_info=1 parameter is passed, it replaces the hexadecimal job step identifier with the actual job name. Sep 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@mfuller333