Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Which column causes the problem?
Message
 
 
À
22/03/2015 15:05:37
Dragan Nedeljkovich (En ligne)
Now officially retired
Zrenjanin, Serbia
Information générale
Forum:
Microsoft SQL Server
Catégorie:
Autre
Versions des environnements
SQL Server:
SQL Server 2014
Application:
Web
Divers
Thread ID:
01617084
Message ID:
01617088
Vues:
23
>>Hi,
>>
>>When my program executes a stored procedure that updates many fields, the following error is generated:
>>
>>
>>String or binary data would be truncated.
>>
>>
>>I know that it means that I am trying to set the value greater than the column type/length allows.
>>
>>Is it possible to have the error to include which column is the problem?
>
>Never! That is against Microsoft's policy!
>
>Or else they have fixed the "file not found" which never tells you which file was it. It's unchanged since 1981 or thereabouts. This immediate amnesia, where the code immediately forgets which file/field/routine caused the error, is a long standing feature which will live longer than we do.

I agree that "fine not found" is very annoying message; to say the least.

I had to find the "offending" field using the old-fashioned method of commenting one or two fields at a time.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform