String or binary data would be truncated used to hide which column was too long. In SQL Server 2019, Msg 2628 names the table, the column and the value. Here is the same insert on 2017 and 2019, and what to do once you know the column.
SQL SERVER – Script Level Upgrade for Database ‘master’ Failed Because Upgrade Step ‘SSIS_hotfix_install.sql’ Encountered Error 15151
Another SQL Server upgrade failure: upgrade step SSIS_hotfix_install.sql hit error 15151 because a user did not exist. Here is how I fixed it.
SQL SERVER – Error in Validation: Listener in Workgroup – Unable to determine if the computer exists in the domain ‘WORKGROUP’
A client’s domain-less Always On cluster in Azure could not create a listener: Unable to determine if the computer exists in the domain ‘WORKGROUP’. Here is why.
SQL SERVER – Script Level Upgrade for Database ‘master’ Failed Because Upgrade Step ‘msdb110_upgrade.sql’ Encountered Error 8649, State 1, Severity 17
Patching SQL 2017 failed at msdb110_upgrade.sql with error 8649: the query cost exceeded the configured threshold. Here is the cause and the fix.
SQL SERVER – Error: 825 – A Read of the File at Offset Succeeded After Failing 1 Time(s)
One of my clients contacted me to give advice about an error. In this blog, we would discuss error message – A read of the file at offset succeeded after failing 1 time(s)
SQL SERVER – Unable to Set Cloud Witness. Error: An Existing Connection Was Forcibly Closed by The Remote Host
Setting up a cloud witness for a client failed with: An existing connection was forcibly closed by the remote host. Test-NetConnection pointed to the real cause.
SQL SERVER – FIX: Database Diagram Error 15517 – Cannot Execute as the Database Principal Because the Principal ‘dbo’ Does Not Exist
Opening a database diagram failed with error 15517: Cannot execute as the database principal because the principal ‘dbo’ does not exist. Let me show you the fix.