Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a text field that can be 30 characters in length, however it can achieve around 2.000 characters.
For ‘future safety’, it would be nice if this new column could support until 3.000 characters. I think the average size of this field is 250 characters.
Which SQL Server 2000 data type is better to increase performance and disk space?
Do you need unicode or nonunicode data? Use either varchar(3000) or nvarchar (3000). Don’t use text or ntext as they become problematic to query or update.
To design for average length makes no sense.