Re: indexes on tables that get dropped?
From: Tenaya (ct_at_ct.ct)
Date: 04/09/04
- Next message: Louis Davidson: "Re: Table Design Question"
- Previous message: Louis Davidson: "Re: Set based solution"
- In reply to: Adria: "indexes on tables that get dropped?"
- Next in thread: Adam Machanic: "Re: indexes on tables that get dropped?"
- Reply: Adam Machanic: "Re: indexes on tables that get dropped?"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 9 Apr 2004 10:18:07 -0400
Adria,
Perhaps you can recommend to your client that instead of a DROP / CREATE
scenario, that they use the TRUNCATE TABLE option to quickly remove data
from the table while preserving the structure of the table. This way index
structures would be also preserved.
Chief Tenaya
"Adria" <a-carbo@tamu.edu> wrote in message
news:17a7601c41e39$aa2e32a0$a601280a@phx.gbl...
> I have a client who is experiencing performance problems
> due to a very complex query. We would like to create an
> index (or two) to help speed up the query. However, the
> table on which the query is based is dropped and re-
> created hourly.
>
> Would creating an index be advantageous or not?
>
> TIA,
> Adria
- Next message: Louis Davidson: "Re: Table Design Question"
- Previous message: Louis Davidson: "Re: Set based solution"
- In reply to: Adria: "indexes on tables that get dropped?"
- Next in thread: Adam Machanic: "Re: indexes on tables that get dropped?"
- Reply: Adam Machanic: "Re: indexes on tables that get dropped?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|