clustered index table updates question - please help
- From: "Derek" <gepetto_2000@xxxxxxxxx>
- Date: 23 Dec 2006 12:46:18 -0800
i have a table that has no index on a date column and a regular index
on
a customer_id column. the customer_id will be somewhat volatile, lots
of updates and
and deletes on this table. this is the design i inherited and i need a
little advice.
table (pertinent columns shown here for brevity)
orderqueue (id int identity primary key, customer_id int, queuedate
datetime not null default getdate())
clustered index on queuedate (new index i was going to add)
non clustered index on customer_id
queries being issued
select * from orderqueue where customer_id is null order by queuedate
insert into orderqueue (customer_id) values (null)
update orderqueue set customer_id = @customer_id where customer_id is
null
delete from orderqueue where customer_id = @customer_id
the updates/deletes will be about 2:1 to selects. i didn't want to
cluster on customer_id/queuedate because i was afraid of blocking on
the updates to the cluster index page.
questions
what is the effect on a cluster index when a non-clustered index is
updated?
looking at query plan, if the majority of the time is being spent by an
update
in actual updating of the cluster index data page, is that "good"? one
test
i ran showed about 35% of the time seeking rows and 65% of the time
doing
a "Clustered Index Update/Update".
any help is appreciated
.
- Follow-Ups:
- Re: clustered index table updates question - please help
- From: Scott Morris
- Re: clustered index table updates question - please help
- Prev by Date: Re: Connect to 2K on machine with both 2K and 2K5
- Next by Date: Connection and /share file and printer/ option in Windows firewall
- Previous by thread: Connect to 2K on machine with both 2K and 2K5
- Next by thread: Re: clustered index table updates question - please help
- Index(es):
Relevant Pages
|