Finalmente... "String or binary data would be truncated"

Finalmente.. 

Questo è quello che mi sono detto mentre leggevo le novità che l'uscita della Versione 2019 di SQL Server si porterà dietro.

Sicuramente, tutti coloro che per lavoro o anche solo per semplice hobby, usano SQL Server si saranno più e più volte imbattuti in questo errore:

       
Msg 8152, Level 16, State 30, Line 3
String or binary data would be truncated.
The statement has been terminated
La reazione a questo errore è sempre e solo una:

OK sto inserendo i dati in una tabella, sto scrivendo un testo troppo lungo rispetto alla dimensione di una colonna e mi esce l'errore.
Ma quale sarà questa colonna che causa l'errore?
Adesso dovrò iniziare a controllarle una ad una..

Bene! La novità è che SQL Server 2019 ci dirà qual'è la colonna in cui stiamo cercando di inserire un testo troppo lungo:

       
Msg 2628, Level 16, State 1, Line 3
String or binary data would be truncated in table 'Demo.dbo.MyTable'.
column 'MyColumn'. Truncated value: 'My D'.
Finalmente potremo risparmiare un bel po di tempo!

Questa nuova feature è stata resa disponibile a partire dalla CTP 2.1 anche se solo dietro attivazione della trace flag 460.
Si spera però che con l'uscita della versione definitiva questa utile novità diventi attiva "by default"

Per oggi è tutto! Alla prossimo post!

Luca Biondi @ SQLServerPerformance blog!

 






Next post: Cos’è il database TEMPDB? ...e quindi perché è importante.

Previous post:

Comments

Post a Comment

I Post più popolari

Speaking to Sql Server, sniffing the TDS protocol

Image
Hello friends!  If yesterday you read my post and found it definitely boring (for the topic of course and not for how it was written to the author 😁) well today I promise you that the topic will be much more interesting! Let's talk about Sniffing , let's talk about going to see what happens when we "log in" or when we send a Query to SQL Server.  We will do this by taking a look to the little known tabular data stream (TDS) protocol built on top of the TCP/IP protocol. Ready! The TDS protocol What is the Tabular data stream (TDS) protocol?  The TDS is the protocol used by the SQL Server client Net-Library to communicates with SQL Server . TDS is specific to SQL Server and it is a low-level protocol that specifies both commands and data in a specific arrangement.  TDS encapsulate the TCP/IP protocol. Sniffing TDS packets you can read from the network the requests that your application do to the SQL Server and read the answer .   How to Sniff data from the ne...
Read more

SQL Server, find text in a Trigger, Stored Procedures, View and Function. Two ways and what ways is better

Image
Hi guys, Welcome back! Today a light post about a question that has been asked to me several times. The question is: how to  search for text inside a trigger or a stored procedure ? We have two different ways. A first way using a system view called syscomments: SELECT obj.xtype, text , * FROM sysobjects obj JOIN syscomments com on obj.id = com.id WHERE TEXT like '%text_that_i_am_searching_for%' A second way using a system view called sql_module: SELECT o. name AS Object_Name, o. type_desc , m. definition FROM sys.sql_modules m JOIN sys.objects o ON m. object_id = o. object_id WHERE m. definition Like '%text_that_i_am_searching_for%' ;   Another question is? What differences do we have in using one way instead of the other? Which solution is better? You have to consider that the system view sys.syscomment is obsolete and will be removed sooner or later. So don't use it in production enviroiments. The sys.sql_m...
Read more

SQL Server, Avoid that damn Table Spool!

Image
Hi guys, Welcome back for another post! A light one inspired from what i do during my work: many times I optimize queries rewriting them or adding index and i like it very much! Sometimes you need to use a little imagination, but everything you learn ... sooner or later it will come in handy! Enjoy the reading mates! Avoid the Table Spool, when you can A few days ago I came across a query whose execution time was very high ... or so it was for the client complaining about the problem. Before recreating it, let's create the structures and fill the tables with some data Create table PriceList (Id int identity (1,1) primary Key ,Code Varchar (20)) Insert into PriceList (code) select top 1000 right( '0000' + cast ( row_number () over ( order by id) as varchar (4)),4) from artico Insert into PriceList (code) select top 4000 right( '1000' + cast ( row_number () over ( order by id) as varchar (4)),4) from artico Create table OrdersList (Id int identity...
Read more