SQL Server, performance, data, analytics
If you receive error code 4815 while doing a Bulk Insert into an Azure SQL Database (including SqlBulkCopy()), it’s likely you are trying to insert a string that is too long into a (n)varchar(x) column.
The unhelpful error message does not contain any mention of overflow, or the column name! Posting in the hope it will save someone some time.
If anyone needed a single concrete reason to upgrade to SQL Server 2019 (when its released), ignoring all the new features, here it is:
2628 – String or binary data would be truncated in table ‘%.ls’, column ‘%.ls’. Truncated value: ‘%.*ls’.
That’s right! After something like 25+ years, Microsoft are finally fixing the cursed “BINARY OR STRING DATA WOULD BE TRUNCATED”!
Seen via Brent Ozar’s post: What’s New in SQL Server 2019’s sys.messages: More Unannounced Features
If you are running SQL Server 2012 and you see this error:
DESCRIPTION: No catalog entry found for partition ID xxx in database N.
The metadata is inconsistent. Run DBCC CHECKDB to check for a metadata
corruption.a quick check reveals database 2 is tempDB:
SELECT name FROM sys.databases WHERE database_id = 2;If you run a DBCC CHECKDB against tempDB:
DBCC CHECKDB ('tempdb') WITH NO_INFOMSGS, TABLERESULTS;you receive no results, indicating no issues with tempDB.
This is a known issue with a fix:
FIX: “No catalog entry found for partition ID in database ” error when you use SQL Server 2012
Assume that you query the tempdb.sys.allocation_units table in Microsoft SQL Server 2012. When you use NOLOCK hint in the query or the query is under the READ UNCOMMITED transaction isolation level, you receive the following intermittent 608 error message:
Error: 608 Severity: 16 State: 1
No catalog entry found for partition in database . The metadata is inconsistent. Run DBCC CHECKDB to check for a metadata corruptionNote The DBCC CHECKDB command does not show any sign of database corruption.
Fixed in: