DBServerInfo Data job fails with error "String or binary data would be truncated."

The DBServerInfo Data job calls the iss_DBSI_PrepareData_Update stored procedure, which is used to collect updated database information for the DBServerInfo command to use when run.

The SQL Server Agent Job Activity Monitor indicates that the DBServerInfo Data job has failed. Upon closer examination of the job history, the job is failing with the error "String or binary data would be truncated."

If you attempt to run the iss_DBSI_PrepareData_Update stored procedure, you obtain the same error.

It is important to note that this job is not critical for SiteProtector operation, but it is important for troubleshooting purposes. This means that this issue is not going to impact SiteProtector functionalities.

The "String or binary data would be truncated" error indicates that the procedure is attempting to store something in the DBServerInfo table that is larger than the column allows. The two known reasons this can occur are:

1. SQL Server has at least one database whose name exceeds 25 characters in length.
    
2. The 'show advanced options' parameter is enabled in SQL Server and you are running the Enterprise edition of SQL Server.

For issue #1, the only resolution is to either rename the database causing the problem or move it to another SQL server.

You can verify if #2 is the problem by running the SQL query:

sp_configure

If one of the parameter names returned in the result is "common criteria compliance enabled," then you can resolve the issue by executing the following query to hide the advanced options from the sp_configure results:

sp_configure 'show advanced options', 0;
go
reconfigure;
go

If you run the DBServerInfo Data job, it should run without issue now. If the Stored Procedure persists throwing out this or other errors, please contact support to get a fix for your specific needs.