Column Count -vs- Table Count performance trade-offs?

Greetings, folks.

Hoping someone here can give me even a half-informed (or at least
well-argued) opinion on which route to take for better performance (or
indeed if there actually will be any difference) between these two options;

- Hold all data (approximately 100 columns) in a single table, or
- Separate data into smaller tables (of approximately 20 columns each).

Only 5 or so columns will be accessed with any regularity; my concern is
whether there'd be more overhead in having large records in a single table,
or having multiple tables.

For the record, the data'll be in SQL Server 2005 Express and accessed
through classic ASP.

With everything only in design phase at the moment, I'm not very keen on
creating & mass-populating with dummy data to do performance analyses (call
me lazy, but I'd expect someone out there has already gone through the
exercise).

Thanks in advance for your help.

--
Bob Milutinovic
Cognicom - "Australia's Web Presence Specialists"
http://www.cognicom.net.au/
telephone (0417) 45-77-66
facsimile (02) 9824-2240

Re: Column Count -vs- Table Count performance trade-offs?

You should ping Joe Celko (--celko) in
microsoft.public.sqlserver.programming.

I'm certain he'll have constructive advice.

Bob Lehmann

"Bob Milutinovic" wrote in message
news:uXNQ$9s0HHA.728@TK2MSFTNGP05.phx.gbl...
> Greetings, folks.
>
> Hoping someone here can give me even a half-informed (or at least
> well-argued) opinion on which route to take for better performance (or
> indeed if there actually will be any difference) between these two
options;
>
> - Hold all data (approximately 100 columns) in a single table, or
> - Separate data into smaller tables (of approximately 20 columns each).
>
> Only 5 or so columns will be accessed with any regularity; my concern is
> whether there'd be more overhead in having large records in a single
table,
> or having multiple tables.
>
> For the record, the data'll be in SQL Server 2005 Express and accessed
> through classic ASP.
>
> With everything only in design phase at the moment, I'm not very keen on
> creating & mass-populating with dummy data to do performance analyses
(call
> me lazy, but I'd expect someone out there has already gone through the
> exercise).
>
> Thanks in advance for your help.
>
> --
> Bob Milutinovic
> Cognicom - "Australia's Web Presence Specialists"
> http://www.cognicom.net.au/
> telephone (0417) 45-77-66
> facsimile (02) 9824-2240
>
>

Re: Column Count -vs- Table Count performance trade-offs?

"Bob Lehmann" wrote in message
news:OGkocZx0HHA.5740@TK2MSFTNGP04.phx.gbl...

> You should ping Joe Celko (--celko) in
> microsoft.public.sqlserver.programming.
>
> I'm certain he'll have constructive advice.

Thanks Bob, I'll head over there now :-)

--
Bob Milutinovic
Cognicom - "Australia's Web Presence Specialists"
http://www.cognicom.net.au/
telephone (0417) 45-77-66
facsimile (02) 9824-2240