Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Downside of VARCHAR(MAX)
Message
 
 
À
Tous
Information générale
Forum:
Microsoft SQL Server
Catégorie:
Conception bases de données
Titre:
Downside of VARCHAR(MAX)
Divers
Thread ID:
01675921
Message ID:
01675921
Vues:
57
Hi,

I have a table - email log -where the application (VFP 9) stores records of each email sent by the application or a user.

The table has a field TO_EMAIL CHAR(100) where the string of all recipient emails is stored. E.g. "user1@company.com, user2@company.com"

A couple of days ago I received an error - generated by SQL SERVER - "String or binary data would be truncated". This error was emailed to me by one of the customer. Clearly they probably created a string of email recipients longer than 100.
In my test DB I change the type of field from CHAR(100) to VARCHAR(MAX). In my testing on my computer it works.

My question, what is or are the downside(s) of changing CHAR(FIXED) to VARCHAR(MAX)?

TIA
"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
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform