Login | Register   
RSS Feed
Download our iPhone app
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.

Tip of the Day
Language: SQL Server
Expertise: Beginner
Jun 12, 2000



Building the Right Environment to Support AI, Machine Learning and Deep Learning

Datatype Decision

I have a field that stores lots of data (up to 8,000 characters). I thought that I could maybe save disk space if I stored this data as varbinary versus varchar. Is this correct?

If so, I would have to use CAST or CONVERT every time I wanted to display the data or update it. Is this correct?

Which do you think would be an overall better solution: storing this data as varchar, taking up more space, and not having to convert it; or storing it as varbinary, taking up less space, but having to convert it each time it is read or written?

If your data consists of characters, your datatype choices are char: varchar or text (or nchar, nvarchar, ntext for international data). A column of varbinary datatype is expecting only binary data so that doesn't really fit your data requirements.

The char and varchar datatypes can contain up to 8,000 characters of data. Char is of fixed length and stores the data value with padded spaces. Varchar stores only the data value in the database. If your data is going to be over 8,000 characters you must use the text datatype. In your case the varchar datatype should be sufficient and no conversion will be needed.

DevX Pro
Comment and Contribute






(Maximum characters: 1200). You have 1200 characters left.



Thanks for your registration, follow us on our social networks to keep up-to-date