Large Table

I have a vendor database that looks poorly designed. The table has over 100
columns (Columns 1 through 99 are Tag#1 to Tag #99)!
The table now has close to 300,000 rows and trying to sort the table makes
EM time out. Using query analyzer I stopped the query after 2.5 minutes. D
o
you have any ideas on how to make this faster?
Thanks"Niles" <Niles@.discussions.microsoft.com> wrote in message
news:080B7A39-2A3C-4145-92E9-D26C221A4C0D@.microsoft.com...
>I have a vendor database that looks poorly designed. The table has over
>100
> columns (Columns 1 through 99 are Tag#1 to Tag #99)!
> The table now has close to 300,000 rows and trying to sort the table makes
> EM time out. Using query analyzer I stopped the query after 2.5 minutes.
> Do
> you have any ideas on how to make this faster?
> Thanks
Normalize the tables and do it properly.
Create VIEWS that show the old information in the same format, if you need
to support vendor front-end stuff.
Rick Sawtell
MCT, MCSD, MCDBA|||As far as sorting goes, do you have appropriate indexes set up on the
columns you're trying to sort on?
Clint
"Rick Sawtell" <Quickening@.msn.com> wrote in message
news:%23JiMSDZAGHA.2256@.TK2MSFTNGP11.phx.gbl...
> "Niles" <Niles@.discussions.microsoft.com> wrote in message
> news:080B7A39-2A3C-4145-92E9-D26C221A4C0D@.microsoft.com...
>
> Normalize the tables and do it properly.
> Create VIEWS that show the old information in the same format, if you need
> to support vendor front-end stuff.
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
>|||No, I am not very familiar with indexing yet. This is a vendor db so
normally I let them fix issues but I am not sure they know much about
databases as I had to help them write some scripts. Thanks though.
"Clint" wrote:

> As far as sorting goes, do you have appropriate indexes set up on the
> columns you're trying to sort on?
> --
> Clint
> "Rick Sawtell" <Quickening@.msn.com> wrote in message
> news:%23JiMSDZAGHA.2256@.TK2MSFTNGP11.phx.gbl...
>
>