Message-Id: <10613.116561@fatcity.com> From: "Steve McClure" Date: Fri, 8 Sep 2000 15:40:34 -0700 Subject: Index Creation question This is a multi-part message in MIME format. ------=_NextPart_000_0191_01C019AB.2091C520 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I have a question about creating an index on a production OLTP database. = This type of work I usually schedule for weekends or late at night when = downtime would cause minimal problems. The client I am currently = working for, as a developer not a DBA--I learn about all things DBA as I = go--, is asking me to do this in the middle of the day. The deal is I = am going away for the weekend and won't be able to do it until next week = when I return. Anyway my reservation has to do with incoming transactions during the = index build. First I have this thought in the back of my head that = creating an index will lock the table, but I can't really say where that = is coming from. Secondly I am certain that it will have a negative = impact on transactions during the index creation. We are talking about = 4 million rows in the table, and it is THE table read and written to = during OLTP. Am I just being paranoid, or should I make them wait? Steve McClure ------=_NextPart_000_0191_01C019AB.2091C520 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

I have a question about creating an = index on a=20 production OLTP database. This type of work I usually schedule for = weekends or late at night when downtime would cause minimal = problems. The=20 client I am currently working for, as a developer not a DBA--I learn = about all=20 things DBA as I go--, is asking me to do this in the middle of the = day. =20 The deal is I am going away for the weekend and won't be able to do it = until=20 next week when I return.

Anyway my reservation has to do with = incoming=20 transactions during the index build. First I have this thought in = the back=20 of my head that creating an index will lock the table, but I can't = really say=20 where that is coming from. Secondly I am certain that it will have = a=20 negative impact on transactions during the index creation. We are = talking=20 about 4 million rows in the table, and it is THE table read and written = to=20 during OLTP.

Am I just being paranoid, or should I = make them=20 wait?

Steve = McClure