Skip to content

Add impact of TEXTSIZE on sp_executesql and EXEC statement #10069

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.

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

Closed
wants to merge 1 commit into from

Conversation

rrg92
Copy link
Contributor

@rrg92 rrg92 commented Apr 13, 2025

Hi,

I recently ran into an issue related to this and had never noticed that SQL Agent changes the TEXTSIZE setting by default.

I think it would be really helpful if the documentation explicitly mentioned this behavior—especially to improve indexing and discoverability for others facing similar issues (e.g., the query works fine in SSMS but fails when executed via SQL Agent).

In my case, the problem happened while using EXEC in combination with a linked server to MySQL, so I imagine many others around the world might encounter the same situation.

Add more examples and notes about impact of this settings in some common commands and Jobs
Copy link
Contributor

@rrg92 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

Copy link
Contributor

Learn Build status updates of commit 8898046:

✅ Validation status: passed

File Status Preview URL Details
docs/t-sql/statements/set-textsize-transact-sql.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@rrg92 rrg92 changed the title Add impact on sp_executesql and EXEC statement Add impact of TEXTSIZE on sp_executesql and EXEC statement Apr 13, 2025
@v-dirichards
Copy link
Contributor

@WilliamDAssafMSFT

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Apr 14, 2025
@rwestMSFT
Copy link
Contributor

#reassign:rwestMSFT

@rwestMSFT rwestMSFT self-requested a review April 14, 2025 17:26
@rwestMSFT
Copy link
Contributor

The underlying article needs a refresh, so I'll look into this and incorporate your changes as needed. Thanks for your contribution. This PR will automatically close when the internal PR is merged, which may take a few days.

@rwestMSFT
Copy link
Contributor

@rrg92 FYI, we're condensing this and moving it to the Manage Job Steps article, in the SSMS content area. You'll retain contributor credit here (even though it'll end up being a link), but not there, due to how GitHub works. We expect the article to publish in the next couple of business days.

@rrg92
Copy link
Contributor Author

rrg92 commented Apr 17, 2025

No problem @rwestMSFT! The most important thing is that the question about TEXTSIZE makes sense and is now being addressed officially in some documentation by you. I'm happy about that — thanks for the attention!

@rwestMSFT
Copy link
Contributor

Thank you for bringing this to our attention, and forcing me to review older content 😄

@ttorble ttorble closed this Apr 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants