Re: table data link - "add extra field" vs "new table with a key"
From: R Reyes (RReyes_at_discussions.microsoft.com)
Date: 02/22/05
- Next message: Debbie: "Add fields vs. Join new table"
- Previous message: John Bell: "RE: what's the logic?"
- In reply to: David Gugick: "Re: table data link - "add extra field" vs "new table with a key""
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 22 Feb 2005 10:47:06 -0800
ok. thanks!
"David Gugick" wrote:
> R Reyes wrote:
> > thanks for responding.
> >
> > sry if i wasn't clear. these images will not be stored inside the
> > database. they will be on the server with the photo's filepath stored
> > in the database column/field.
> >
> > the 30 columns in TBL_CLIENT i referred to are not picture related.
> > they are the clients info such as name, address, phone etc...i just
> > meant to ask if it would be bad to add the photopath column/field a
> > table that already has 30 columns/fields in it, not to add 30 picture
> > path columns/fields.
> >
> > it sounds like i should just add the column/field to TBL_CLIENT with
> > the photo path stored. i asked about the other solution to add a
> > completely new table (TBL_CLIENTPICTURES) with a key because i wanted
> > to see if it wasn't a recommended solution but, i guess it's really
> > fine either way. do you have any comments or objections to using the
> > 2nd solution?
> >
>
> You were clear and my answers were as you requested. Maybe my response
> wasn't completely clear, however. I stick by my original statements:
> What does the database design say about this column? And 30 columns may
> or may not be a lot, depending on what the table looks like. Using a 1:1
> table is employed often, but mostly to remove columns from the parent
> table that may not always be filled in. Many database designs pull the
> address and other contact information out into other tables. That may,
> or may not be appropriate in your case, but it does lend to itself to a
> more flexible design (a client can have zero or more addresses of
> different types, a client can have zero or more contact numbers of
> different types, a client can have zero or more pictures associated with
> their account, etc.)
>
> It also depends on how large the columns are. SQL Server has an 8060
> byte limit for a row size. And large row sizes generally have a negative
> impact on performance.
>
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
>
- Next message: Debbie: "Add fields vs. Join new table"
- Previous message: John Bell: "RE: what's the logic?"
- In reply to: David Gugick: "Re: table data link - "add extra field" vs "new table with a key""
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
