Hello all,

a design question for you:

We currently have a table which is accessed by several different
applications. However, we have been asked to add several huge varchar
columns to hold a bunch of text (a crap idea if you ask me). The varchar
fields will be completed for most but not all of the records. These
fields are only relevant to two of the applications.

Would it be better to have one main table or to have two tables, one for
the basic data and one for all the guff?

I'm thinking two tables although I wasn't sure how much of a performance
issue it would be to have the varchar fields in the same table as the
frequently accessed fields.

Carol.



This email and any files transmitted within it are private and confidential.
If you are not the intended recipient, this email and any attachments within it have been transmitted to you in error.
You are prohibited from using, copying, distributing or otherwise using the information contained within this email.
Nothing in this email message amounts to a contractual or legal commitment on the part of Optilan unless confirmed by a communication signed on behalf of the company.
Any email cannot be guaranteed to be secure, error free or free from viruses. Although every possible care is taken by Optilan, Optilan does not accept any liability whatsoever for any loss or damage which may be caused as a result of the transmission of this message by email.


MS Sql Server LazyDBA home page