Skip to content
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

Error message "String or binary data would be truncated." #8

Open
Crucial2K opened this issue Apr 1, 2019 · 0 comments
Open

Error message "String or binary data would be truncated." #8

Crucial2K opened this issue Apr 1, 2019 · 0 comments

Comments

@Crucial2K
Copy link

Crucial2K commented Apr 1, 2019

Hi,
I recently got the error "String or binary data would be truncated." while executing dba_indexDefrag_sp . This is because the log, status and exclusion tables (plus some variables) have the type NVARCHAR(128) for columns such as database name, index name etc. being the maximum size allowed for object names. However, if the object name is the maximum 128 characters long a failure will occur with an INSERT using QUOTENAME() because adding square brackets to the name takes the length to 130 characters.

I suggest that the DDL for the tables and variables that are set at NVARCHAR(128) are changed to NVARCHAR(130). Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant