adding a new key; planning for millions of records

Hello all,
i'm going to be adding a new column (1 byte) that will become a non-unique
indexed value into a table that i'm adding records into. i know for a fact
that this table will grow from the current thousands to millions of records
over the span of a few ws and have allocated the database file
accordingly.
since i already have the primary key as clustered is there something i can
do so that adding this key as part of insert operations will be done
efficiently? I'm adding tens of thousands of records a day. In a previous
incarnation of this database i had had problems with having to rebuild the
keys occasionally or insert operations would timeout. I know that part of
the problem was fragmentation of the database, but i'd like to give it a
'heads up' to prepare for a large B-tree for this key.
is there a knob that will control this when i create the index?
thanks,
johnJohn,
I'm assuming you're refering to index fragmentation for the 1 byte index.
Might try creating the index with a lower FILLFACTOR to help minimize
fragmentation.
HTH
Jerry
"John Mott" <johnmott59@.hotmail.com> wrote in message
news:usOEf6$0FHA.1132@.TK2MSFTNGP10.phx.gbl...
> Hello all,
> i'm going to be adding a new column (1 byte) that will become a non-unique
> indexed value into a table that i'm adding records into. i know for a fact
> that this table will grow from the current thousands to millions of
> records
> over the span of a few ws and have allocated the database file
> accordingly.
> since i already have the primary key as clustered is there something i can
> do so that adding this key as part of insert operations will be done
> efficiently? I'm adding tens of thousands of records a day. In a previous
> incarnation of this database i had had problems with having to rebuild the
> keys occasionally or insert operations would timeout. I know that part of
> the problem was fragmentation of the database, but i'd like to give it a
> 'heads up' to prepare for a large B-tree for this key.
> is there a knob that will control this when i create the index?
> thanks,
> john
>sql

Add a third node to a cluster

I have two node SQL Enterprise installed on a Windows 2003 cluster running
active -active. I would like to add a third node so that it would become 2
active and 1 passive . Is this feasible ?
Also , can someone tell me how can I make the third node standby for the
other two ? Do I have to install any binary and executable on the third node
/ modify the possible owner ?
Raymond
Look at "How to add nodes to an existing virtual server (Setup)" in BOL. It
gives a step by step on how to do it.
After you ran that, follow the steps in the Service Pack readme that you
have installed on the other nodes.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Norman" <raymond.chan@.hotmail.com> wrote in message
news:u7qvDXwYFHA.2288@.TK2MSFTNGP14.phx.gbl...
>I have two node SQL Enterprise installed on a Windows 2003 cluster running
>active -active. I would like to add a third node so that it would become 2
>active and 1 passive . Is this feasible ?
> Also , can someone tell me how can I make the third node standby for the
> other two ? Do I have to install any binary and executable on the third
> node / modify the possible owner ?
> Raymond
>
|||Norman
To control failover you can use the Preferred Owners List on the Group
Property sheets. However if you have a Windows 2003 Cluster you can implement
AntiAffintityClassNames to make absolutely certain that a node that is in a
passive role take ownership of a group in the event of a failure. See the
following KB for details on how to setup.
http://support.microsoft.com/default...;en-us;Q296799
Regards
CT
"Norman" wrote:

> I have two node SQL Enterprise installed on a Windows 2003 cluster running
> active -active. I would like to add a third node so that it would become 2
> active and 1 passive . Is this feasible ?
> Also , can someone tell me how can I make the third node standby for the
> other two ? Do I have to install any binary and executable on the third node
> / modify the possible owner ?
> Raymond
>
>