|
Home > Archive > MS SQL Server > January 2006 > query performance with large tables
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
query performance with large tables
|
|
| Ken Abe 2006-01-19, 8:23 pm |
| Hi,
I am currently facing two problems: one general and one more specific.
My general issue is improving the performance of queries involving a very
large table. I know that the most efficient optimization is to create indexes
that match the type of queries I run. Are there any other solutions? Can I
gain from splitting the table into several smaller ones?
The more specific problem is related to index creation. I am trying to
create an index that makes sense, but SQL Server 2005 gives a timeout error
after less than a minute. I suppose this is due to the size of the table and
cost of clustering (I set a primary key) but I can't find in BOL how to
increase the timeout value...
Any ideas regarding any of these two questions?
| |
| Andrew J. Kelly 2006-01-19, 8:23 pm |
| If you have proper indexes you should not need to split the table. You can
partition the table but that will not help you if you still don't have
proper indexes.
Don't use the gui to create the index. Use the query Editor and issue a
CREATE INDEX statement instead. The editor defaults to 0 timeout so it will
stay connected as long as it needs to.
--
Andrew J. Kelly SQL MVP
"Ken Abe" <KenAbe@discussions.microsoft.com> wrote in message
news:2A0250DC-54ED-4FDC-A377- 3D5F72BFEB1F@microso
ft.com...
> Hi,
>
> I am currently facing two problems: one general and one more specific.
>
> My general issue is improving the performance of queries involving a very
> large table. I know that the most efficient optimization is to create
> indexes
> that match the type of queries I run. Are there any other solutions? Can I
> gain from splitting the table into several smaller ones?
>
> The more specific problem is related to index creation. I am trying to
> create an index that makes sense, but SQL Server 2005 gives a timeout
> error
> after less than a minute. I suppose this is due to the size of the table
> and
> cost of clustering (I set a primary key) but I can't find in BOL how to
> increase the timeout value...
>
> Any ideas regarding any of these two questions?
>
>
|
|
|
|
|