Showing posts with label windows. Show all posts
Showing posts with label windows. Show all posts

Thursday, March 29, 2012

Adding a second processor

Hello,
We use a client/server application from our vendor running on SQL 2000,
which runs on a Windows 2003 Server in an ADS domain. The server is
currently only running a single Xeon processor and it has the capability for
having 2 processors. Our vendor claims that their application is not "coded
"
to run on a dual-processor machine (a bunch of bull?), but their application
only runs on the client end, not on the server.
The way I see it, it is Windows and SQL that have to be able to handle the
processor, which we all know they can certainly do. Does anyone think that
by adding a second processor, we would be doing any damage to our data and o
r
the application?
The application is Time Matters Enterprise 5.0 (sr2), by LexisNexis and it
is a case management system for a law firm. This is our mission-critical
application.
Thanks, JeffOutside of the fact that your vendor doesn't support it, I really see no
reason why you would want to limit yourself to just one processor. In most
cases, SQL Server would run faster with more CPU's. This is because your
workload is distributed across all of the CPU's. Thus, if you have 100
concurrent queries, 50 would run on one and 50 would run on the other -
ignoring parallelism. However, in most cases parallelism would improve an
individual query's performance, since both CPU's would be used to service
the query. In some cases, parallelism makes specific queries run slower,
but you can turn parallelism off on a per-query basis (or even at the server
level, if you prefer).
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
.
"Jeff" <Jeff@.discussions.microsoft.com> wrote in message
news:56410EBD-043F-4AC4-870B-652141840545@.microsoft.com...
Hello,
We use a client/server application from our vendor running on SQL 2000,
which runs on a Windows 2003 Server in an ADS domain. The server is
currently only running a single Xeon processor and it has the capability for
having 2 processors. Our vendor claims that their application is not
"coded"
to run on a dual-processor machine (a bunch of bull?), but their application
only runs on the client end, not on the server.
The way I see it, it is Windows and SQL that have to be able to handle the
processor, which we all know they can certainly do. Does anyone think that
by adding a second processor, we would be doing any damage to our data and
or
the application?
The application is Time Matters Enterprise 5.0 (sr2), by LexisNexis and it
is a case management system for a law firm. This is our mission-critical
application.
Thanks, Jeff|||I do realize the benefits of a second processor in SQL and that's just it, w
e
don't want to limit ourselves to a single processor. We purchased a new
server recently and only purchased one processor because of what our vendor
told us. It didn't make any sense to me then and it doesn't now. The mobo
on that server is setup for dual-processors. Since the application runs on
the client, I didn't understand why they would tell us that.
More importantly, we no longer have a service contract with that vendor so
they are not going to support us either way unless we get another contract.
My thought is that the worst that can happen is that we have to restore the
database off of a backup and pull the second processor out.
--
Thanks, Jeff
"Tom Moreau" wrote:

> Outside of the fact that your vendor doesn't support it, I really see no
> reason why you would want to limit yourself to just one processor. In mos
t
> cases, SQL Server would run faster with more CPU's. This is because your
> workload is distributed across all of the CPU's. Thus, if you have 100
> concurrent queries, 50 would run on one and 50 would run on the other -
> ignoring parallelism. However, in most cases parallelism would improve an
> individual query's performance, since both CPU's would be used to service
> the query. In some cases, parallelism makes specific queries run slower,
> but you can turn parallelism off on a per-query basis (or even at the serv
er
> level, if you prefer).
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Toronto, ON Canada
> ..
> "Jeff" <Jeff@.discussions.microsoft.com> wrote in message
> news:56410EBD-043F-4AC4-870B-652141840545@.microsoft.com...
> Hello,
> We use a client/server application from our vendor running on SQL 2000,
> which runs on a Windows 2003 Server in an ADS domain. The server is
> currently only running a single Xeon processor and it has the capability f
or
> having 2 processors. Our vendor claims that their application is not
> "coded"
> to run on a dual-processor machine (a bunch of bull?), but their applicati
on
> only runs on the client end, not on the server.
> The way I see it, it is Windows and SQL that have to be able to handle the
> processor, which we all know they can certainly do. Does anyone think tha
t
> by adding a second processor, we would be doing any damage to our data and
> or
> the application?
> The application is Time Matters Enterprise 5.0 (sr2), by LexisNexis and it
> is a case management system for a law firm. This is our mission-critical
> application.
> --
> Thanks, Jeff
>|||The only real issue I see is that of licensing. If you go with a per-CPU
license, you will have to spend some change to do the upgrade. Other than
that, you're fine.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
"Jeff" <Jeff@.discussions.microsoft.com> wrote in message
news:7CA5419B-884D-4D51-8B1C-3DEE16B291F1@.microsoft.com...
I do realize the benefits of a second processor in SQL and that's just it,
we
don't want to limit ourselves to a single processor. We purchased a new
server recently and only purchased one processor because of what our vendor
told us. It didn't make any sense to me then and it doesn't now. The mobo
on that server is setup for dual-processors. Since the application runs on
the client, I didn't understand why they would tell us that.
More importantly, we no longer have a service contract with that vendor so
they are not going to support us either way unless we get another contract.
My thought is that the worst that can happen is that we have to restore the
database off of a backup and pull the second processor out.
--
Thanks, Jeff
"Tom Moreau" wrote:

> Outside of the fact that your vendor doesn't support it, I really see no
> reason why you would want to limit yourself to just one processor. In
> most
> cases, SQL Server would run faster with more CPU's. This is because your
> workload is distributed across all of the CPU's. Thus, if you have 100
> concurrent queries, 50 would run on one and 50 would run on the other -
> ignoring parallelism. However, in most cases parallelism would improve an
> individual query's performance, since both CPU's would be used to service
> the query. In some cases, parallelism makes specific queries run slower,
> but you can turn parallelism off on a per-query basis (or even at the
> server
> level, if you prefer).
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Toronto, ON Canada
> ..
> "Jeff" <Jeff@.discussions.microsoft.com> wrote in message
> news:56410EBD-043F-4AC4-870B-652141840545@.microsoft.com...
> Hello,
> We use a client/server application from our vendor running on SQL 2000,
> which runs on a Windows 2003 Server in an ADS domain. The server is
> currently only running a single Xeon processor and it has the capability
> for
> having 2 processors. Our vendor claims that their application is not
> "coded"
> to run on a dual-processor machine (a bunch of bull?), but their
> application
> only runs on the client end, not on the server.
> The way I see it, it is Windows and SQL that have to be able to handle the
> processor, which we all know they can certainly do. Does anyone think
> that
> by adding a second processor, we would be doing any damage to our data and
> or
> the application?
> The application is Time Matters Enterprise 5.0 (sr2), by LexisNexis and it
> is a case management system for a law firm. This is our mission-critical
> application.
> --
> Thanks, Jeff
>|||"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:uzy8rPbeGHA.5016@.TK2MSFTNGP04.phx.gbl...
> The only real issue I see is that of licensing. If you go with a per-CPU
> license, you will have to spend some change to do the upgrade. Other than
> that, you're fine.
I'll second this.
And second the opinion that the original vendor is full of it. :-)

> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Toronto, ON Canada
> "Jeff" <Jeff@.discussions.microsoft.com> wrote in message
> news:7CA5419B-884D-4D51-8B1C-3DEE16B291F1@.microsoft.com...
> I do realize the benefits of a second processor in SQL and that's just it,
> we
> don't want to limit ourselves to a single processor. We purchased a new
> server recently and only purchased one processor because of what our
vendor
> told us. It didn't make any sense to me then and it doesn't now. The
mobo
> on that server is setup for dual-processors. Since the application runs
on
> the client, I didn't understand why they would tell us that.
> More importantly, we no longer have a service contract with that vendor so
> they are not going to support us either way unless we get another
contract.
> My thought is that the worst that can happen is that we have to restore
the
> database off of a backup and pull the second processor out.
> --
> Thanks, Jeff
>
> "Tom Moreau" wrote:
>
your[vbcol=seagreen]
an[vbcol=seagreen]
service[vbcol=seagreen]
slower,[vbcol=seagreen]
the[vbcol=seagreen]
and[vbcol=seagreen]
it[vbcol=seagreen]
mission-critical[vbcol=seagreen]
>sql

Adding a second processor

Hello,
We use a client/server application from our vendor running on SQL 2000,
which runs on a Windows 2003 Server in an ADS domain. The server is
currently only running a single Xeon processor and it has the capability for
having 2 processors. Our vendor claims that their application is not "coded"
to run on a dual-processor machine (a bunch of bull?), but their application
only runs on the client end, not on the server.
The way I see it, it is Windows and SQL that have to be able to handle the
processor, which we all know they can certainly do. Does anyone think that
by adding a second processor, we would be doing any damage to our data and or
the application?
The application is Time Matters Enterprise 5.0 (sr2), by LexisNexis and it
is a case management system for a law firm. This is our mission-critical
application.
--
Thanks, JeffOutside of the fact that your vendor doesn't support it, I really see no
reason why you would want to limit yourself to just one processor. In most
cases, SQL Server would run faster with more CPU's. This is because your
workload is distributed across all of the CPU's. Thus, if you have 100
concurrent queries, 50 would run on one and 50 would run on the other -
ignoring parallelism. However, in most cases parallelism would improve an
individual query's performance, since both CPU's would be used to service
the query. In some cases, parallelism makes specific queries run slower,
but you can turn parallelism off on a per-query basis (or even at the server
level, if you prefer).
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
.
"Jeff" <Jeff@.discussions.microsoft.com> wrote in message
news:56410EBD-043F-4AC4-870B-652141840545@.microsoft.com...
Hello,
We use a client/server application from our vendor running on SQL 2000,
which runs on a Windows 2003 Server in an ADS domain. The server is
currently only running a single Xeon processor and it has the capability for
having 2 processors. Our vendor claims that their application is not
"coded"
to run on a dual-processor machine (a bunch of bull?), but their application
only runs on the client end, not on the server.
The way I see it, it is Windows and SQL that have to be able to handle the
processor, which we all know they can certainly do. Does anyone think that
by adding a second processor, we would be doing any damage to our data and
or
the application?
The application is Time Matters Enterprise 5.0 (sr2), by LexisNexis and it
is a case management system for a law firm. This is our mission-critical
application.
--
Thanks, Jeff|||I do realize the benefits of a second processor in SQL and that's just it, we
don't want to limit ourselves to a single processor. We purchased a new
server recently and only purchased one processor because of what our vendor
told us. It didn't make any sense to me then and it doesn't now. The mobo
on that server is setup for dual-processors. Since the application runs on
the client, I didn't understand why they would tell us that.
More importantly, we no longer have a service contract with that vendor so
they are not going to support us either way unless we get another contract.
My thought is that the worst that can happen is that we have to restore the
database off of a backup and pull the second processor out.
--
Thanks, Jeff
"Tom Moreau" wrote:
> Outside of the fact that your vendor doesn't support it, I really see no
> reason why you would want to limit yourself to just one processor. In most
> cases, SQL Server would run faster with more CPU's. This is because your
> workload is distributed across all of the CPU's. Thus, if you have 100
> concurrent queries, 50 would run on one and 50 would run on the other -
> ignoring parallelism. However, in most cases parallelism would improve an
> individual query's performance, since both CPU's would be used to service
> the query. In some cases, parallelism makes specific queries run slower,
> but you can turn parallelism off on a per-query basis (or even at the server
> level, if you prefer).
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Toronto, ON Canada
> ..
> "Jeff" <Jeff@.discussions.microsoft.com> wrote in message
> news:56410EBD-043F-4AC4-870B-652141840545@.microsoft.com...
> Hello,
> We use a client/server application from our vendor running on SQL 2000,
> which runs on a Windows 2003 Server in an ADS domain. The server is
> currently only running a single Xeon processor and it has the capability for
> having 2 processors. Our vendor claims that their application is not
> "coded"
> to run on a dual-processor machine (a bunch of bull?), but their application
> only runs on the client end, not on the server.
> The way I see it, it is Windows and SQL that have to be able to handle the
> processor, which we all know they can certainly do. Does anyone think that
> by adding a second processor, we would be doing any damage to our data and
> or
> the application?
> The application is Time Matters Enterprise 5.0 (sr2), by LexisNexis and it
> is a case management system for a law firm. This is our mission-critical
> application.
> --
> Thanks, Jeff
>|||The only real issue I see is that of licensing. If you go with a per-CPU
license, you will have to spend some change to do the upgrade. Other than
that, you're fine.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
"Jeff" <Jeff@.discussions.microsoft.com> wrote in message
news:7CA5419B-884D-4D51-8B1C-3DEE16B291F1@.microsoft.com...
I do realize the benefits of a second processor in SQL and that's just it,
we
don't want to limit ourselves to a single processor. We purchased a new
server recently and only purchased one processor because of what our vendor
told us. It didn't make any sense to me then and it doesn't now. The mobo
on that server is setup for dual-processors. Since the application runs on
the client, I didn't understand why they would tell us that.
More importantly, we no longer have a service contract with that vendor so
they are not going to support us either way unless we get another contract.
My thought is that the worst that can happen is that we have to restore the
database off of a backup and pull the second processor out.
--
Thanks, Jeff
"Tom Moreau" wrote:
> Outside of the fact that your vendor doesn't support it, I really see no
> reason why you would want to limit yourself to just one processor. In
> most
> cases, SQL Server would run faster with more CPU's. This is because your
> workload is distributed across all of the CPU's. Thus, if you have 100
> concurrent queries, 50 would run on one and 50 would run on the other -
> ignoring parallelism. However, in most cases parallelism would improve an
> individual query's performance, since both CPU's would be used to service
> the query. In some cases, parallelism makes specific queries run slower,
> but you can turn parallelism off on a per-query basis (or even at the
> server
> level, if you prefer).
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Toronto, ON Canada
> ..
> "Jeff" <Jeff@.discussions.microsoft.com> wrote in message
> news:56410EBD-043F-4AC4-870B-652141840545@.microsoft.com...
> Hello,
> We use a client/server application from our vendor running on SQL 2000,
> which runs on a Windows 2003 Server in an ADS domain. The server is
> currently only running a single Xeon processor and it has the capability
> for
> having 2 processors. Our vendor claims that their application is not
> "coded"
> to run on a dual-processor machine (a bunch of bull?), but their
> application
> only runs on the client end, not on the server.
> The way I see it, it is Windows and SQL that have to be able to handle the
> processor, which we all know they can certainly do. Does anyone think
> that
> by adding a second processor, we would be doing any damage to our data and
> or
> the application?
> The application is Time Matters Enterprise 5.0 (sr2), by LexisNexis and it
> is a case management system for a law firm. This is our mission-critical
> application.
> --
> Thanks, Jeff
>|||"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:uzy8rPbeGHA.5016@.TK2MSFTNGP04.phx.gbl...
> The only real issue I see is that of licensing. If you go with a per-CPU
> license, you will have to spend some change to do the upgrade. Other than
> that, you're fine.
I'll second this.
And second the opinion that the original vendor is full of it. :-)
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Toronto, ON Canada
> "Jeff" <Jeff@.discussions.microsoft.com> wrote in message
> news:7CA5419B-884D-4D51-8B1C-3DEE16B291F1@.microsoft.com...
> I do realize the benefits of a second processor in SQL and that's just it,
> we
> don't want to limit ourselves to a single processor. We purchased a new
> server recently and only purchased one processor because of what our
vendor
> told us. It didn't make any sense to me then and it doesn't now. The
mobo
> on that server is setup for dual-processors. Since the application runs
on
> the client, I didn't understand why they would tell us that.
> More importantly, we no longer have a service contract with that vendor so
> they are not going to support us either way unless we get another
contract.
> My thought is that the worst that can happen is that we have to restore
the
> database off of a backup and pull the second processor out.
> --
> Thanks, Jeff
>
> "Tom Moreau" wrote:
> > Outside of the fact that your vendor doesn't support it, I really see no
> > reason why you would want to limit yourself to just one processor. In
> > most
> > cases, SQL Server would run faster with more CPU's. This is because
your
> > workload is distributed across all of the CPU's. Thus, if you have 100
> > concurrent queries, 50 would run on one and 50 would run on the other -
> > ignoring parallelism. However, in most cases parallelism would improve
an
> > individual query's performance, since both CPU's would be used to
service
> > the query. In some cases, parallelism makes specific queries run
slower,
> > but you can turn parallelism off on a per-query basis (or even at the
> > server
> > level, if you prefer).
> >
> > --
> > Tom
> >
> > ----
> > Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> > SQL Server MVP
> > Toronto, ON Canada
> > ..
> > "Jeff" <Jeff@.discussions.microsoft.com> wrote in message
> > news:56410EBD-043F-4AC4-870B-652141840545@.microsoft.com...
> > Hello,
> >
> > We use a client/server application from our vendor running on SQL 2000,
> > which runs on a Windows 2003 Server in an ADS domain. The server is
> > currently only running a single Xeon processor and it has the capability
> > for
> > having 2 processors. Our vendor claims that their application is not
> > "coded"
> > to run on a dual-processor machine (a bunch of bull?), but their
> > application
> > only runs on the client end, not on the server.
> >
> > The way I see it, it is Windows and SQL that have to be able to handle
the
> > processor, which we all know they can certainly do. Does anyone think
> > that
> > by adding a second processor, we would be doing any damage to our data
and
> > or
> > the application?
> >
> > The application is Time Matters Enterprise 5.0 (sr2), by LexisNexis and
it
> > is a case management system for a law firm. This is our
mission-critical
> > application.
> >
> > --
> > Thanks, Jeff
> >
> >
>

Tuesday, March 27, 2012

Adding a new node to an existing cluster

I currently have two clustered servers. OS - Windows 2003 (SP1), SQL 2000.
These servers are getting old so what I wanted to do is add two new servers
to the cluster and take the original two offline. I have loaded the new
servers, connected them to our sans, and added them to the cluster. I am at
the point of loading SQL. I have read the books on line and according to BOL,
I should be able to "On the Cluster Management screen, select the node and
click Add'. However, I am not given the option, ALL four servers show up in
the "configured nodes" list. What my question is, if I continue, will ALL
servers be loaded/reloaded with SQL or just the top server (the one I am
trying to load).
You will add SQL to the new servers only, just watch the install screen
carefully, cause you can also uninstall the original two nodes
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.itsummitseries.com/experts/fournier.htm - Cluster Summit
"Marilyn" <Marilyn@.discussions.microsoft.com> wrote in message
news:96494E06-031A-4370-B2AA-C8615627E5FD@.microsoft.com...
>I currently have two clustered servers. OS - Windows 2003 (SP1), SQL 2000.
> These servers are getting old so what I wanted to do is add two new
> servers
> to the cluster and take the original two offline. I have loaded the new
> servers, connected them to our sans, and added them to the cluster. I am
> at
> the point of loading SQL. I have read the books on line and according to
> BOL,
> I should be able to "On the Cluster Management screen, select the node and
> click Add'. However, I am not given the option, ALL four servers show up
> in
> the "configured nodes" list. What my question is, if I continue, will ALL
> servers be loaded/reloaded with SQL or just the top server (the one I am
> trying to load).
|||That is what I am worried about...
I do NOT want to uninstall SQL from the existing nodes. What specifically
should I keep my eye out for?
"Rodney R. Fournier [MVP]" wrote:

> You will add SQL to the new servers only, just watch the install screen
> carefully, cause you can also uninstall the original two nodes
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering Website
> http://msmvps.com/clustering - Blog
> http://www.itsummitseries.com/experts/fournier.htm - Cluster Summit
> "Marilyn" <Marilyn@.discussions.microsoft.com> wrote in message
> news:96494E06-031A-4370-B2AA-C8615627E5FD@.microsoft.com...
>
>
|||Make sure you install from one of the new machines.
Make sure you have someone standing over your shoulder watching the screens
and double checking your work.
Make sure you select ADD and see the server move to the right side (which
means they will be installed).
Make sure think about any and all defaults (this is how I uninstalled my one
node SQL Cluster a few months back, instead of adding a node).
It's very easy to either do it correctly or incorrectly. Like I said, have
someone double check the screen BEFORE you hit next and all should go well.
Lastly make sure you have a good restore on hand. Yes, I said restore, cause
a backup is worthless, unless you can and have actually tried restoring it.
I hate that people brag about backups, brag about restoring Or don't brag
about either, cause lack of either is a firing offense in my book. Ok, I am
off my soap box!
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.itsummitseries.com/experts/fournier.htm - Cluster Summit
"Marilyn" <Marilyn@.discussions.microsoft.com> wrote in message
news:A8424504-3A78-4E91-B18B-42B76B18C8F8@.microsoft.com...[vbcol=seagreen]
> That is what I am worried about...
> I do NOT want to uninstall SQL from the existing nodes. What specifically
> should I keep my eye out for?
> "Rodney R. Fournier [MVP]" wrote:
|||Thank you so much. I understand, however where you say "Make sure you select
ADD and see the server move to the right side (which means they will be
installed)." That was my problem, all four servers are ALREADY on the right
side.
P.S. I am in full agreement on the backup part... ;-)
"Rodney R. Fournier [MVP]" wrote:

> Make sure you install from one of the new machines.
> Make sure you have someone standing over your shoulder watching the screens
> and double checking your work.
> Make sure you select ADD and see the server move to the right side (which
> means they will be installed).
> Make sure think about any and all defaults (this is how I uninstalled my one
> node SQL Cluster a few months back, instead of adding a node).
> It's very easy to either do it correctly or incorrectly. Like I said, have
> someone double check the screen BEFORE you hit next and all should go well.
> Lastly make sure you have a good restore on hand. Yes, I said restore, cause
> a backup is worthless, unless you can and have actually tried restoring it.
> I hate that people brag about backups, brag about restoring Or don't brag
> about either, cause lack of either is a firing offense in my book. Ok, I am
> off my soap box!
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering Website
> http://msmvps.com/clustering - Blog
> http://www.itsummitseries.com/experts/fournier.htm - Cluster Summit
> "Marilyn" <Marilyn@.discussions.microsoft.com> wrote in message
> news:A8424504-3A78-4E91-B18B-42B76B18C8F8@.microsoft.com...
>
>
|||For more information about adding a node to a virtual server, refer to the
"How to add nodes to an existing virtual server (Setup)" topic in SQL Server
2000 Books Online.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://www.msmvps.com/clustering - Blog
http://www.itsummitseries.com/experts/fournier.htm - Cluster Summit
"Marilyn" <Marilyn@.discussions.microsoft.com> wrote in message
news:392A3D50-7EFA-4C36-82AB-0D74BE1ABB79@.microsoft.com...[vbcol=seagreen]
> Thank you so much. I understand, however where you say "Make sure you
> select
> ADD and see the server move to the right side (which means they will be
> installed)." That was my problem, all four servers are ALREADY on the
> right
> side.
> P.S. I am in full agreement on the backup part... ;-)
>
> "Rodney R. Fournier [MVP]" wrote:
|||Marilyn
Make sure your specifying the correct SQL Virtual Server name. It sounds
like you might be accidently trying to install a new instance of SQL and all
nodes are showing up.
Are you selecting the "Advanced Options" and getting the option to
"Maintain a Virtual Server for Failover Clustering" the Virtual Server? If
not then your more than likely attempting to install a new instance of SQL.
Regards
cT
"Marilyn" wrote:

> I currently have two clustered servers. OS - Windows 2003 (SP1), SQL 2000.
> These servers are getting old so what I wanted to do is add two new servers
> to the cluster and take the original two offline. I have loaded the new
> servers, connected them to our sans, and added them to the cluster. I am at
> the point of loading SQL. I have read the books on line and according to BOL,
> I should be able to "On the Cluster Management screen, select the node and
> click Add'. However, I am not given the option, ALL four servers show up in
> the "configured nodes" list. What my question is, if I continue, will ALL
> servers be loaded/reloaded with SQL or just the top server (the one I am
> trying to load).
|||I got it! I just went for it. It took about 10 minutes to load with no
problems at all. Thanks for the help and advice. I'm really glad Microsoft
has these newsgroups. I have used them serveral times to find additional
suggestions and ideas. Thanks again. M ;-)
"Charles Tolento" wrote:
[vbcol=seagreen]
> Marilyn
> Make sure your specifying the correct SQL Virtual Server name. It sounds
> like you might be accidently trying to install a new instance of SQL and all
> nodes are showing up.
> Are you selecting the "Advanced Options" and getting the option to
> "Maintain a Virtual Server for Failover Clustering" the Virtual Server? If
> not then your more than likely attempting to install a new instance of SQL.
> Regards
> cT
> "Marilyn" wrote:

Adding a new node to a pre-existing sql2K cluster

Hi,
I have inherited a windows 2003 cluster which had SQL 2000 initially
installedon on only one of the two nodes due to a hardware issue which
since been corrected.
I need to add the second node to the SQL2000 cluster instalation only
the documentation on this is very weak.
My production SQL virtual server is already on SP4 but this new node
will have to be done from SP2. Any help or instructions would be geatly
appreciated.
Thank you in advance,
Ken
Here's my notes on SP's and clusters, the hyperlinks are in blue at thend of
the document.
Nik Marshall-Blank MCSD/MCDBA
Linz, Austria
"kenb" <kbunce@.gmail.com> wrote in message
news:1130543443.479453.69900@.z14g2000cwz.googlegro ups.com...
> Hi,
> I have inherited a windows 2003 cluster which had SQL 2000 initially
> installedon on only one of the two nodes due to a hardware issue which
> since been corrected.
> I need to add the second node to the SQL2000 cluster instalation only
> the documentation on this is very weak.
> My production SQL virtual server is already on SP4 but this new node
> will have to be done from SP2. Any help or instructions would be geatly
> appreciated.
> Thank you in advance,
> Ken
>
begin 666 Cluster.doc
MT,\1X*&Q&N$`````````````````````/@.`#`/[_"0`&```````````````!
M````. ``````````$ ``.@.````$```#^____`````#<```#_____________
M_________________________________________________ ___________
M_________________________________________________ ___________
M_________________________________________________ ___________
M_________________________________________________ ___________
M_________________________________________________ ___________
M_________________________________________________ ___________
M_________________________________________________ ___________
M_________________________________________________ ___________
M_________________________________________________ ___________
M_______________________LI<$`?V )! ``^!*_````````$ ``````!@.``
M+!(```X`8FIB:N:'YH<````````````````````````)!!8`+ B ``(3M``"$
M[0``+ H```````````````````````````````````````#__P\````` ````
M``#__P\```````````#__P\``````````````````````*0`` ````"0$````
M````) 0``"0$````````) 0````````D! ```````"0$````````) 0``!0`
M`````````````#@.$````````H T```````"@.#0```````* -````````H T`
M`!0```"T#0``' ```#@.$````````L18``.X```#<#0``< ```$P.````````
M3 X```````!,#@.```````$P.````````)P\``#X```!E#P``% ```'D/```,
M````,!8```(````R%@.```````#(6````````,A8````````R% @.```````#(6
M````````,A8``"0```"?%P``: (```<:``!.````5A8``!4`````````````
M````````````) 0```````"%#P`````````````````````````````G#P``
M`````"</````````A0\```````"%#P```````%86`````````````````` `D
M! ```````"0$````````3 X``````````````````$P.``#;````:Q8``!8`
M``!)$ ```````$D0````````21 ```````"%#P``(@.```"0$````````3 X`
M```````D! ```````$P.````````,!8``````````````````$D0````````
M````````````````````````````````````````````````` ```````````
M````A0\````````P%@.``````````````````21 ```````!)$ ``'@.```,H2
M```8````) 0````````D! ``````````````````````````````````````
M````````````````````````````````````````````%A,`` `````!,#@.``
M`````- -```,````X%.NFH#;Q0$``````````* -````````IP\``&H```#B
M$@.``" ``````````````,!8```````"!%@.``, ```+$6````````ZA(``"P`
M``!5&@.```````!$0```B````51H``! ````6$P``````````````````````
M````````````````````````````````````````````````` ```````````
M```````````6$P``D@.$``%4:```````````````````D! ```````*@.4``"(
M`0``A0\```````"%#P```````$D0````````A0\```````"%# P``````````
M````````````````````````````````````````A0\`````` `"%#P``````
M`(4/````````5A8```````!6%@.```````````````````````````` ``````
M````````````````,Q ``!8`````````````````````````````````````
M`````````(4/````````A0\```````"%#P```````+$6````````A0\`````
M``"%#P```````(4/````````A0\``````````````````#@.$````````. 0`
M```````X! ``Y <``!P,``"$`0``. 0````````X! ```````#@.$````````
M' P````````X! ```````#@.$````````. 0````````D! ```````"0$````
M````) 0````````D! ```````"0$````````) 0```````#_____``````(`
M# $````````````````````````````````````````````````` ````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ````%=I;F1O
M=W,@.,C P,R!C;'5S=&5R(&EN<W1A;&QA=&EO;B]F86EL=7)E+V5V:6-T:6]N
M+V%D9"!397)V:6-E('!A8VL@.;F]T97,-#5-13"!397)V:6-E(%!A8VMS#0U"
M969O<F4@.87!P;'EI;F<@.86YY('-E<G9I8V4@.<&%C:W,@.<')E<&%R92!A(&-O
M;G1I;F=E;F-Y('!L86X@.:6X@.8V%S92!O9B!C871A<W1R;W!H:6,@.9F%I;'5R
M92X-#4UA:V4@.<W5R92!T:&4@.;7-D8BP@.;6%S=&5R(&%N9"!M;V1E;"!D871A
M8F%S97,@.87)E(&)A8VME9"!U<"!T;R!A('-T;W)A9V4@.;65D:6$@.;F]T(&1E
M<&5N9&%N="!O;B!T:&4@.8VQU<W1E<B!B96EN9R!U<&=R861E9 "X@.268@.4U T
M(&EN<W1A;&QA=&EO;B!F86EL<R!T:&5N('1H97-E(&1A=&%B87-E<R!W:6QL
M(&AA=F4@.=&\@.8F4@.<F5S=&]R960@.8F5C875S92!T:&5Y(&%R92!A;65N9&5D
M(&)Y(%-0-"X-#4UA:V4@.<W5R92!Y;W4@.:&%V92!C=7)R96YT(&)A8VMU<',@.
M;V8@.87!P;&EC871I;VX@.9&%T86)A<V5S(&%G86EN(&YO="!O; B!S=&]R86=E
M(&UE9&EA(&1E<&5N9&%N="!O;B!T:&4@.8VQU<W1E<B!B96EN9 R!U<&=R861E
M9"X-#4UA:V4@.<W5R92!T:&%T(%-0,R!I<R!A<'!L:65D(&)E9F]R92!A<'!L
M>6EN9R!34#0N#0U.;V1E($9A:6QU<F4-#55S:6YG(&-L=7-T97(@.861M:6YI
M<W1R871O<B!S=&]P('1H92!C;'5S=&5R('-E<G9I8V4@.;VX@.=&AE(&9A:6QE
M9"!N;V1E(&%N9"!E=FEC="!T:&4@.9F%I;&5D(&YO9&4-#5)E8G5I;&0@.=&AE
M('-E<G9E<B!W:71H('1H92!H;W-T($]3(&%N9"!S86UE('-E<G9I8V4@.<&%C
M:R!A<R!O=&AE<B!N;V1E<R!I;B!T:&4@.8VQU<W1E<BX-#55S:6YG(&-L=7-T
M97(@.861M:6YI<W1R871O<B!A9&0@.=&AE(&YE=R!N;V1E('1O( '1H92!C;'5S
M=&5R+@.T-57-I;F<@.=&AE(%-13"!I;G-T86QL871I;VX@.0T0O9&ES:R!C;W!Y
M(')U;B!T:&4@.4U%,(&EN<W1A;&QA=&EO;BX@.#0U/;B!T:&4@.0V]M<'5T97(@.
M3F%M92!P86=E+"!T>7!E('1H92!V:7)T=6%L('-E<G9E<B!N86UE+"!C;&EC
M:R!6:7)T=6%L(%-E<G9E<BP@.86YD('1H96X@.8VQI8VL@.3F5X="X-#4QE879I
M;F<@.061V86YC960@.3W!T:6]N<R!S96QE8W1E9"P@.8VQI8VL@.3F5X="X-#4QE
M879I;F<@.36%I;G1A:6X@.82!6:7)T=6%L(%-E<G9E<B!F;W(@.1F%I;&]V97(@.
M0VQU<W1E<FEN9R!S96QE8W1E9"P@.8VQI8VL@.3F5X="X-#4]N('1H92!6:7)T
M=6%L(%-E<G9E<B!);F9O<FUA=&EO;B!P86=E+"!C;&EC:R!.97AT+@.T-3VX@.
M=&AE($-L=7-T97(@.36%N86=E;65N="!P86=E+"!C;&EC:R!T:&4@.;F5W(&YO
M9&4L(&-L:6-K($%D9"P@.86YD('1H96X@.8VQI8VL@.3F5X="X-#45N=&5R('1H
M92!R96QE=F%N="!D971A:6QS+@.U!<'!L>2!344P@.4U S('!H>7-I8V%L;'D@.
M;VX@.=&AE(')E8G5I;'0@.;F]D92X-07!P;'D@.4U T('1O('1H92!O=&AE<B H
M;F]N+69A:6QE9"D@.;F]D92 H979E;B!I9B!I="!H87,@.86QR96%D>2!B965N
M(&%P<&QI960I+B!4:&ES('=I;&P@.87!P;'D@.4U T('1O(&)O=&@.@.;F]D97,@.
M8G)I;F=I;F<@.=&AE;2!I;B!L:6YE+B!9;W4@.;6%Y(&YE960@.= &\@.9&5L971E
M($Y%141?4U!?2T59(&9R;VT@.=&AE(')E9VES=')Y(&]F(&)O=&@.@.8V]M<'5T
M97)S(&)E9F]R92!A<'!L>6EN9R!34#0N#0T-#51H92!F;VQL;W=I;F<@.;&EN
M:W,@.<')O=FED92!A;&P@.=&AE(&EN9F]R;6%T:6]N('1H870@.:7,@.<F5Q=6ER
M960N#0T3($A94$523$E.2R B:'1T<#HO+W=W=RYM:6-R;W-O9G0N8V]M+V1O
M=VYL;V%D<R]D971A:6QS+F%S<'@._1F%M:6QY240].39F-S9E9#<M.38S-"TT
M,S P+3DQ-3DM.#DV,SAF-&(T968W)F1I<W!L87EL86YG/65N(B !%$1O=VYL
M;V%D(&1E=&%I;',Z($=U:61E('1O($-R96%T:6YG(&%N9"!#;VYF:6=U<FEN
M9R!A(%-E<G9E<B!#;'5S=&5R(%5N9&5R(%=I;F1O=W,@.4V5R=F5R(#(P, #,5
M#0T3($A94$523$E.2R B:'1T<#HO+W=W=RYS<6PM<V5R=F5R+7!E<F9O<FUA
M;F-E+F-O;2]S<6QS97)V97(R,# P7V-L=7-T97)I;F=?:6YS=&%L;%]M86EN
M+F%S<"(@.`11(;W<@.=&\@.26YS=&%L;"!344P@.4V5R=F5R(#(P, # @.0VQU<W1E
M<FEN9Q4-#1,@.2%E015),24Y+(")H='1P.B\O<W5P<&]R="YM:6-R;W-O9G0N
M8V]M+S]K8FED/3,P,38P,"(@.`11(;W<@.=&\@.8V]N9FEG=7)E($UI8W)O<V]F
M="!$:7-T<FEB=71E9"!4<F%N<V%C=&EO;B!#;V]R9&EN871O<B!O;B!A(%=I
M;F1O=W,@.4V5R=F5R(#(P,#,@.8VQU<W1E<A4-#1,@.2%E015),24Y+(")H='1P
M.B\O=W=W+FUI8W)O<V]F="YC;VTO=&5C:&YE="]P<F]D=&5C:&YO;"]S<6PO
M,C P,"]M86EN=&%I;B]F86EL8VQU<RYM<W!X(B !%$UI8W)O<V]F="!344P@.
M4V5R=F5R(#(P,# @.1F%I;&]V97(@.0VQU<W1E<FEN9Q4-#1,@.2%E015),24Y+
M(")H='1P.B\O=W=W+FUI8W)O<V]F="YC;VTO=&5C:&YE="]P<F]D=&5C:&YO
M;"]S<6PO,C P,"]D97!L;WDO:&%S;V<P,2YM<W!X(B !%%-13"!397)V97(@.
M,C P,"!(:6=H($%V86EL86)I;&ET>2!397)I97,Z($EM<&QE;65N= &EN9R!&
M86EL;W9E<B!#;'5S=&5R:6YG%0T-$R!(65!%4DQ)3DL@.(FAT=' Z+R]W=W<N
M;6-S92YM<R]M97-S86=E,3<U.38V-"YH=&UL(B !%$%D9&EN9R!N97<@.;F]D
M92!T;R!344P@.4U T(&-L=7-T97(5#0T-#0T-#0T-#0T-#0``````````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M```````````&``!)" ``2@.@.``$L(``!/" ``7 @.``%X(``!F" ``60H``&4*
M``!G"@.``CPH``+0*```""P``%0L``"0+``"D"P``I@.L``*T+` `"Z"P``Y0L`
M`/,+```$# ``" P``!,,```C# ``- P``#@.,``!## ``= P``(4,``")# ``
MDPP``*T,``"Z# ``O@.P``,@.,``#:# ``^PP``/X,```/#0``$PT``!4-```6
M#0``Z T``$0.``"+#@.``C X```8/```'#P``" \``&8/``!G#P``:0\``&H/
M``#'#P``R \``/?OZ^;WYM_K]^;KV^O7Z]?;T,;0QM#&T,;0QM#&T,;0QM#&
MT,;0QM#&T+K;MMNNVZ.NFJ[;KMN/```5`@.B!`VI+`0``!@.@.!%F@.R'(P`50@.!
M$!5H,AR,`!9H,AR,`#!*#P``%0((@.0-J``````8(`19H,AR,`%4(`0\#:@.``
M```6:#(<C !5" $&%FCJ#F@.``!86:#(<C !#2A$`3TH#`%%*`P!A2A$``!(5
M:#(<C `6:#(<C `U"(%<"($`#!5H,AR,`!9H,AR,```&%F@.2$3L```86:#(<
MC ``#!5HNP<^`!9HNP<^```)%FB[!SX`/BH!!A9HNP<^```/%6B[!SX`%FA#
M1YT`/BH!#Q5HNP<^`!9HNP<^`#XJ`0`X``8``$H(``!+" ``70@.``%X(``"\
M" ``O0@.``*,)``"D"0``) H``"4*``!8"@.``60H``&8*``!G"@.``R0H``,H*
M```C"P``) L``&$+``!B"P``I0L``*8+```*# ``"PP``#H,```[# ``BPP`
M`/T```````````````#]````````````````_0```````````````/T`````
M``````````#X````````````````^ ```````````````/@.`````````````
M``#X````````````````^ ```````````````/@.```````````````#X````
M````````````^ ```````````````/@.```````````````#X````````````
M````^ ```````````````/@.```````````````#X````````````````\P``
M`````````````/,```````````````#S````````````````ZP``````````
M`````.L```````````````#K````````````````ZP``````` ````````.L`
M``````````````#K````````````````ZP``````````````` ```````````
M!P``$F10`0$`9V0R'(P```0``&=D$A$[```$``!G9+L'/@.```0```!L`!@.``
M+!(``/T````````````````````````````````````````````````` ````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M``````````0$``$!`8L,``",# ``P P``,$,```5#0``%@.T``#(-``!@.#0``
M10X``$8.``!'#@.``2 X``(H.``"+#@.``: \``&D/``#T#P``]0\``) 0``"1
M$ ``'1$``!X1``#$$0``Q1$``" 2```A$@.``(A(``",2``#W````````````
M````]P```````````````/<```````````````#W````````````````]P``
M`````````````/<```````````````#W````````````````]P``````````
M`````/<```````````````#W````````````````]P```````````````/<`
M``````````````#W````````````````]P```````````````/<`````````
M``````#W````````````````]P```````````````/<```````````````#W
M````````````````]P```````````````/<```````````````#W````````
M````````]P```````````````/<```````````````#W````````````````
M]P```````````````/(`````````````````````````````````````````
M````! ``9V02$3L```<``!)D4 $!`&=D,AR,```;R \``,D/``#R#P``\P\`
M`/4/``#V#P``+1 ``"X0```O$ ``CA ``(\0``"1$ ``DA ``.P0``#M$ ``
M[A ``!L1```<$0``'A$``!\1``!V$0``=Q$``'@.1``#"$0``PQ$`` ,01``#%
M$0``QA$``/H1``#[$0``_!$``!X2```?$@.``(!(``"(2```C$@.``)1(``"82
M```G$@.``+!(``/?N]^KWZM_W[O?J]^K4]^[WZO?JR?N]^K%O<6RO:F]Q>JE
MH)B1C0``````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````!A9H
MNP<^```,%6B[!SX`%FB[!SX```\5:+L'/@.`6:+L'/@.`^*@.$)%FB[!SX`/BH!
M!A9H$A$[```0%6A!>BP`%FA!>BP`,$H/```5`@.B!`VHQ!0``!@.@.!%FA!>BP`
M50@.!#P-J`````!9H07HL`%4(`086:$%Z+ ``%0((@.0-J+ 0```8(`19H,AR,
M`%4(`14""($#:B$#```&" $6:#(<C !5" $5`@.B!`VI<`@.``!@.@.!%F@.R'(P`
M50@.!!A9H,AR,```0%6@.R'(P`%F@.R'(P`,$H/```/`VH`````%F@.R'(P`50@.!
M`"<C$@.``)!(``"42```F$@.``)Q(``"@.2```I$@.``*A(``"L2` ``L$@.``^@.``
M`````````````/H```````````````#Z````````````````^@.``````````
M`````/@.```````````````#X````````````````^ ```````````````/@.`
M``````````````#X````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M``````$````$``!G9+L'/@.``"2P`,9!H`1^P@.BX@.L,9!(; (!R*P" <CD* %
M))"@.!26P```7L,0"&+#$`@.R0Q (`````````````````````````````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````2 P$``$0`````
M````````````````````````````````````````````````` ```````````
M````````````````````T,GJ>?FZSA&,@.@."J`$NI"P(````#` ```X,GJ>?FZ
MSA&,@.@."J`$NI"]H```!H`'0`= !P`#H`+P`O`'<`=P!W`"X`;0!I`&,`<@.!O
M`',`;P!F`'0`+@.!C`&\`;0`O`&0`;P!W`&X`; !O`&$`9 !S`"\`9 !E`'0`
M80!I`&P`<P`N`&$`<P!P`'@.`/P!&`&$`;0!I`&P`>0!)`$0`/0`Y`#8`9@.`W
M`#8`90!D`#<`+0`Y`#8`,P`T`"T`- `S`# `, `M`#D`,0`U`#D`+0`X`#D`
M-@.`S`#@.`9@.`T`&(`- !E`&8`-P`F`&0`:0!S`' `; !A`'D`; !A`&X`9P`]
M`&4`;@.```!$!``!$````````````````````````````````` ```````````
M`````````````````````````````````````````-#)ZGGYNLX1C((`J@.!+
MJ0L"`````P```.#)ZGGYNLX1C((`J@.!+J0N@.````: !T`'0`< `Z`"\`+P!W
M`'<`=P`N`',`<0!L`"T`<P!E`'(`=@.!E`'(`+0!P`&4`<@.!F` &\`<@.!M`&$`
M;@.!C`&4`+@.!C`&\`;0`O`',`<0!L`',`90!R`'8`90!R`#(`, `P`# `7P!C
M`&P`=0!S`'0`90!R`&D`;@.!G`%\`:0!N`',`= !A`&P`; !?`&T`80!I`&X`
M+@.!A`',`< ```,4```!$````````````````````````````````````````
M`````````````````````````````````````````````-#)ZGGYNLX1C((`
MJ@.!+J0L"`````P```.#)ZGGYNLX1C((`J@.!+J0M4````: !T`'0`< `Z`"\`
M+P!S`'4`< !P`&\`<@.!T`"X`;0!I`&,`<@.!O`',`;P!F`'0`+@.!C`&\`;0`O
M`#\`:P!B`&D`9 `]`#,`, `Q`#8`, `P````"P$``$0`````````````````
M````````````````````````````````````````````````` ```````````
M````````T,GJ>?FZSA&,@.@."J`$NI"P(````#````X,GJ>?FZS A&,@.@."J`$NI
M"YH```!H`'0`= !P`#H`+P`O`'<`=P!W`"X`;0!I`&,`<@.!O`',`;P!F`'0`
M+@.!C`&\`;0`O`'0`90!C`&@.`;@.!E`'0`+P!P`'(`;P!D`'0`9 0!C`&@.`;@.!O
M`&P`+P!S`'$`; `O`#(`, `P`# `+P!M`&$`:0!N`'0`80!I`&X`+P!F`&$`
M:0!L`&,`; !U`',`+@.!M`',`< !X````!0$``$0`````````````````````
M````````````````````````````````````````````````` ```````````
M````T,GJ>?FZSA&,@.@."J`$NI"P(````#````X,GJ>?FZSA&,@. @."J`$NI"Y0`
M``!H`'0`= !P`#H`+P`O`'<`=P!W`"X`;0!I`&,`<@.!O`',`;P!F`'0`+@.!C
M`&\`;0`O`'0`90!C`&@.`;@.!E`'0`+P!P`'(`;P!D`'0`90!C` &@.`;@.!O`&P`
M+P!S`'$`; `O`#(`, `P`# `+P!D`&4`< !L`&\`>0`O`&@.`80!S`&\`9P`P
M`#$`+@.!M`',`< !X````OP```$0`````````````````````````````````
M````````````````````````````````````````````````` ```T,GJ>?FZ
MSA&,@.@."J`$NI"P(````#````X,GJ>?FZSA&,@.@."J`$NI"TX`` `!H`'0`= !P
M`#H`+P`O`'<`=P!W`"X`;0!C`',`90`N`&T`<P`O`&T`90!S` ',`80!G`&4`
M,0`W`#4`.0`V`#8`- `N`&@.`= !M`&P`````````````````````````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` (8"$0`2``$`
MG `/``0````````````$`````````````````````````````````` ``````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M`````````````$ ``$#Q_P(`0 `,! ``````````!@.!.`&\`<@.!M`&$`; ``
M``(````8`$-*& !?2 $$84H8`&U("0AS2 D(=$@.)" ``````````````````
M`````$0`04#R_Z$`1 `,!0``````````%@.!$`&4`9@.!A`'4`; !T`" `4 !A
M`'(`80!G`'(`80!P`&@.`( !&`&\`;@.!T``````!2`&D`\_^S`%(`# 4`````
M``````P`5 !A`&(`; !E`" `3@.!O`'(`;0!A`&P````<`!?V`P``--8&``$*
M`VP`--8&``$%`P``8?8#```"``L````H`&L`]/_!`"@.```4```````````<`
M3@.!O`" `3 !I`',`= ````(`````````-@.!50*(`\0`V``P$```R'(P````)
M`$@.`>0!P`&4`<@.!L`&D`;@.!K````# `^*@.%"*@.)P: ``_P!&`%9 H@.`!`48`
M# 0``#(<C ```!$`1@.!O`&P`; !O`'<`90!D`$@.`>0!P`&4`<@.!L`&D`;@.!K
M````# `^*@.%"*@.QP `@. ``````+ H```0``" `````_____P````!*````
M2P```%T```!>````O ```+T```"C`0``I $``"0"```E`@.``6 (``%D"``!F
M`@.``9P(``,D"``#*`@.``(P,``"0#``!A`P``8@.,``*4#``"F` P``"@.0```L$
M```Z! ``.P0``(L$``",! ``P 0``,$$```5!0``%@.4``#(%``!@.!0``108`
M`$8&``!'!@.``2 8``(H&``"+!@.``: <``&D'``#T!P``]0<``) (``"1" ``
M'0D``!X)``#$"0``Q0D``" *```A"@.``(@.H``",*```D"@.``)0H``"8*```G
M"@.``* H``"D*```J"@.``*PH``"X*``"8`````# `````````@. ```( `````
M````````F `````P`````````( ```" `````````````)@.`````, ``````
M``" ````@. ````````````"8`````# `````````@. ```( `````````````
MF `````P`````````( ```" `````````````)@.`````, ````````" ````
M@. ````````````"8`````# `````````@. ```( `````````````F `````P
M`````````( ```" `````````````)@.`````, ````````" ````@. ``````
M``````"8`````# `````````@. ```( `````````````F `````P````````
M`( ```" `````````````)@.`````, ````````" ````@. ````````````"8
M`````# `````````@. ```( `````````````F `````P`````````( ```"
M`````````````)@.`````, ````````" ````@. ````````````"8`````# `
M````````@. ```( `````````````F `````P`````````( ```" ````````
M`````)@.`````, ````````" ````@. ````````````"8`````# `````````
M@. ```( `````````````F `````P`````````( ```" `````````````)@.`
M````, ````````" ````@. ````````````"8`````# `````````@. ```( `
M````````````F `````P`````````( ```" `````````````)@.`````, ``
M``````" ````@. ````````````"8`````# `````````@. ```( `````````
M````F `````P`````````( ```" `````````````)@.`````, ````````"
M````@. ````````````"8`````# `````````@. ```( `````````````F ``
M```P`````````( ```" `````````````)@.`````, ````````" ````@. ``
M``````````"8`````# `````````@. ```( `````````````F `````P````
M`````( ```" `````````````)@.`````, ````````" ````@. ``````````
M``"8`````# `````````@. ```( `````````````F `````P`````````( `
M``" `````````````9@.`````, ````````" ````@. ````````````"8````
M`# `````````@. ```( `````````````F `````P`````````( ```" ````
M`````````)@.`````, ````````" ````@. ````````````"8`````# `````
M````@. ```( `````````````F `````P`````````( ```" ````````````
M`)@.`````, ````````" ````@. ````````````"8`````# `````````@. ``
M`( `````````````F `````P`````````( ```" `````````````)@.`````
M, ````````" ````@. ````````````"8`````# `````````@. ```( `````
M````````F `````P`````````( ```" `````````````)@.`````, ``````
M``" ````@. ````````````"8`````# `````````@. ```( `````````````
MF `````P`````````( ```" `````````````)@.`````, ````````" ````
M@. ````````````"8`````# `````````@. ```( `````````````F `````P
M`````````( ```" `````````````)@.`````, ````````" ````@. ``````
M``````"8`````# `````````@. ```( `````````````F `````P````````
M`( ```" `````````````)@.`````, ````````" ````@. ````````````"8
M`````# `````````@. ```( `````````````F `````P`````````( ```"
M`````````````)@.`````, ````````" ````@. ````````````"8`````# `
M````````@. ```( `````````````F `````P`````````( ```" ````````
M`````)@.`````, ````````" ````@. ``````````````````) ,``&$#``!B
M`P``I@.,```H$```+! ``.@.0``#L$``"+! ``C 0``,$$```N"@.``>XD`, `P
M`````````0````0````!````F$)8!WF)`# `, ````````$````#````````
M``````%YB0`P`# ````````!`````@.`````````````!>XD`, ,P````````
M`0````4`````````````!WF)`# #, ````````$````$``````````````%Y
MB0`P`S ````````!`````P`````````````!>XD`, 8P`````````0````4`
M```'````5$58!YI ````, ````````" ````@. ``````````@. =YB0`P"3 `
M```````!````!0`````````````!>8D`, DP`````````0````0`````````
M`````7N)`# *, ````````$````%``````````````<*`````# `````````
M```````&,&0````````'``8``,@./```L$@.``"@.````X`````!@.``BPP``",2
M```L$@.``"P````T````/``````8``"P2```,````BP8```<'``!F!P``:0<`
M`,@.'``#R!P``]0<``"X(``"." ``D0@.``.T(```;"0``'@.D``'<)``#""0``
MQ0D``/L)```>"@.``+ H``!-8%/\5@.!-8%/\5@.!-8%/\5C!-8%/\5@.!-8%/\5
M@.!-8%/\5@. \``/ X```````&\!@.````"" ```@.````$````!`````0````(`
M``! `![Q$ ```/__`````/\`@.(" `/<``! `#P`"\)(````0``CP" ````$`
M```!! ``#P`#\# ````/``3P* ````$`"? 0````````````````````````
M``(`"O (``````0```4````/``3P0@.```!(`"O (`````00````.``!3``OP
M'@.```+\!```0`,L!`````/\!```(``0#"0```#\#`0`!````$? $`````0``
M`/__`@.````T`7P!(`&P`= `Q`# `- `R`#4`,P`R`#$`. `-`%\`2 !L`'0`
M,0`P`#0`,@.`U`#,`,@.`Q`#D`>P@.``'L(```N"@.``````0 $``$![" ``>P@.`
M`"X*````````RP```,\```! !@.``0P8``"X*```'`!P`!P`$``<``````'4"
M``"'`@.``,@.,``$,#```$! ``" 0``#0$```X! ``A00``(D$``"Z! ``O@.0`
M``\%```3!0``30<``%('```N"@.``!P`S``<`,P`'`#,`!P`S` `<`,P`'`#,`
M!P`S``<`,P`'``````!+````70```!8%```Q!0``+@.H```<`! 0`'``4`!P``
M````0 8``$,&```N"@.``!P`$``<``0!!,_5W^&^6F_\/_P__#_\/_P__#_\/
M_P__#Q ``0```````0```````````````````````Q@.```^$T (1A)C^%<8%
M``'0`@.9>A- "8(28_F\H``(````I``$```````$`````````````````` ```
M`! 8```/A* %$828_A7&!0`!H 4&7H2@.!6"$F/Y/2@.``4$H``%%*``!>2@.``
M`@.`!`"D``0````*"`0``````````````````````"A@.```^$< @.1A$S_%<8%
M``%P" 9>A' (8(1,_X=H`````(A(```"``(`+@.`!`````( !````````````
M```````````*& ``#X1 "Q&$F/X5Q@.4``4 +!EZ$0 M@.A)C^AV@.`````B$@.`
M``(``P`N``$````$@. $```````````````````````H8```/A! .$828_A7&
M!0`!$ X&7H00#F"$F/Z': ````"(2 ```@.`$`"X``0````*"`0``````````
M````````````"A@.```^$X! 1A$S_%<8%``'@.$ 9>A. 08(1,_X=H`````(A(
M```"``4`+@.`!`````( !```````````````````````*& ``#X2P$Q&$F/X5
MQ@.4``; 3!EZ$L!-@.A)C^AV@.`````B$@.```(`!@.`N``$````$@. $`````````
M``````````````H8```/A( 6$828_A7&!0`!@.!8&7H2 %F"$F/Z': ````"(
M2 ```@.`'`"X``0````*"`0``````````````````````"A@.```^$ 4!D1A$S_
M%<8%``%0&09>A% 98(1,_X=H`````(A(```"``@.`+@.`!````03/U=P``````
M`````````/_______P$``````/__`0```!(`$0`)"#I<NOT;``D(#P`)"!D`
M"0@.;``D(#P`)"!D`"0@.;``D(&0!V+MH!YS)S"0(``````'![9 7>2HH3`@.``
M````YS)S"0H0#%0!````! `$``X!``#>2HH3W7I&4P$````$``0`#@.$``$@.J
MJ!1D>!TP`@.``````Q'7G%4@.JJ!0#```````"?%H7````````` ````0(``@.`%
M6)D@.+@.)R90$``````)]0KB$````````````!`@.`"`&1X'3!5'J P`0````0`
M! `.`0``51Z@.,)]0KB$!``````"V,'<R-F?_1@.(``````$ 7;#9P>V0%`P``
M````#S%4/[8P=S(#``````#/<() <2L;: $``````#9G_T8%6)D@.`0````0`
M! `.`0``W7I&4P)\6A<!```````*$ Q4!RLG6 $``````"E"0E?/<() `0``
M``0`! `.`0``!RLG6 ````````````$"``(`XTAQ7RE"0E<"``````!^0O9B
M=B[:`0,``````"X"<F4````````````!`@.`"`'$K&V@.`````` ``````!`@.`"
M`)1N.'_C2'%?`P``````7 ````0````(````Y0````````!;````[@.`"`'IU
M"@."7'0T`$500`.-*$0"9&!8`,3 9`$Q_' "49B(`@. <L`$%Z+ `Q!RT`1RTN
M`$@.#,0#0&C(`3%XS`(1>,P#.&CH`$A$[`+L'/@.#O0S\`9#%!`(IS00!?,4D`
M,$5*`*5#30`X/TX`V!E/`%PQ4@.`&<58`)7E7`+HP7 "1*EX`>B-@.`&)+8P#:
M&V4`Z@.YH`"LZ: "^,&X`,@.]P`$\1<0!!%G(`^P5U`/)B@.0`K<80`;4B&`$QN
MA@.`%18<`53"*`#(<C !V'Y(`0T>=`%\FHP!7>*,`QSZE`*HEI@.!C<*8`7B^I
M`)LWJ0!(4JD`\5:I`"\%J@.`0':L`4U:K`*EVL@.#O%[4`$SV[` $D#O #Y+;P`
MZQV^`/U"P !B(L(`C@.+)`+Q&RP#I"<\`SGK0``P]U !8--4`7PG6`-1ZUP`1
M+]D`DVW9`.-UV0#7']T`[4+?`(M^X0`;$>8`7!?G`,8W\@.!7(OD`"P_Z`%Y]
M_@.#_0 . `0!$!@.``1 8``+ VZ (!``$`1 8```````!$!@.````````(0````
M`````"P*``! ```0`$ ``/__`0````<`50!N`&L`;@.!O`'<`;@.#__P$`" ``
M````````````__\!``````#__P```@.#__P````#__P```@.#__ P`````$````
M1Q:0`0```@.(&`P4$!0(#!(=Z`" ```" " ````````#_`0```````%0`:0!M
M`&4`<P`@.`$X`90!W`" `4@.!O`&T`80!N````-1:0`0(`!04!`@.$'!@.(%!P``
M```````0``````````````" `````%,`>0!M`&(`;P!L````,R:0`0```@.L&
M! ("`@.("!(=Z`" ```" " ````````#_`0```````$$`<@.!I`&$`; ```#<F
MD $```(+!@.0#!00$`@.2'`@.`@.````````````````GP$```````!6 `&4`<@.!D
M`&$`;@.!A````(@.`$`'$(B!@.`\- "Y 1H`0````#FF96&G>&:I@.`````&`!T`
M``"$`0``J @.```$`!0````0``Q 2````A $``*@.(```!``4````2````````
M`"$#`/ 0`````0``````````````````````````````````````````` ```
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M``````@.'H 6T`+0`@.8$R- ``$ `9`&0````9````)PH``"<*````````````
M````````````````````````````````````````````````` ```````````
M```````````"`````````````3*#40#P$ `(````````````````````````
M``````````````!(6 `````H\/\/`0`!/P``Y 0``/___W____]_____?___
M_W____]_____?____W^[!SX``````#(``````````````````````/__$@.``
M``````````````````D`3@.!I`&L`2@.!O`&$`;@.!N`&4`"0!.` &D`:P!*`&\`
M80!N`&X`90```````````````````````````! ````&`````0``````# ``
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M``````#^_P``!0$"```````````````````````!````X(6?\ OE/:!"KD0@.`
M*R>SV3 ```!@.`0``$ ````$```"(`````@.```) ````#````G ````0```"H
M````!0```+P````'````R ````@.```#<````"0```/ ````2````_ ````H`
M```<`0``# ```"@.!```-````- $```X```! `0``#P```$@.!```0````4 $`
M`!,```!8`0```@.```.0$```>````! `````````>````! `````````>````
M# ```$YI:TIO86YN90```!X````$`````````!X````,````3F]R;6%L+F1O
M= ``'@.````P```!.:6M*;V%N;F4````>````! ```#8````>````& ```$UI
M8W)O<V]F="!/9F9I8V4@.5V]R9 ```$ `````[AX-! ```$ `````U+I,/5S%
M`4 `````=@.2 @.-O%`0,````!`````P```(0!```#````J @.```,`````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````_O\```4!`@.```````````````````````@.````+5S =6<+AL0DY<(
M`"LL^:Y$````!=7-U9PN&Q"3EP@.`*RSYKBP!``#H````# ````$```!H````
M#P```' ````%````? ````8```"$````$0```(P````7````E ````L```"<
M````$ ```*0````3````K ```!8```"T````#0```+P````,````R0````(`
M``#D! ``'@.````0``````````P```!(````#````!0````,````G"@.`` `P``
M`-@.8"P`+``````````L`````````"P`````````+`````````!X0 ```!````
M`0`````,$ ```@.```!X````&````5&ET;&4``P````$`````U 0```,`````
M````( ````$````X`````@.```$ ````!`````@.````P```!?4$E$7TA,24Y+
M4P`"````Y 0``$$```",! ``) ````,```!F`'P``P````\````#````````
M``,````%````'P```"<```!H`'0`= !P`#H`+P`O`'<`=P!W`"X`;0!C`',`
M90`N`&T`<P`O`&T`90!S`',`80!G`&4`,0`W`#4`.0`V`#8`- `N`&@.`= !M
M`&P``````!\````!```````3! ,```!%`$H``P````P````#``````````,`
M```%````'P```$H```!H`'0`= !P`#H`+P`O`'<`=P!W`"X`;0!I`&,`<@.!O
M`',`;P!F`'0`+@.!C`&\`;0`O`'0`90!C`&@.`;@.!E`'0`+P!P` '(`;P!D`'0`
M90!C`&@.`;@.!O`&P`+P!S`'$`; `O`#(`, `P`# `+P!D`&4`< !L`&\`>0`O
M`&@.`80!S`&\`9P`P`#$`+@.!M`',`< !X````'P````$``````!,$`P```$L`
M5@.`#````"0````,``````````P````4````?````30```&@.`= !T`' `.@.`O
M`"\`=P!W`'<`+@.!M`&D`8P!R`&\`<P!O`&8`= `N`&,`;P!M`"\`= !E`&,`
M: !N`&4`= `O`' `<@.!O`&0`= !E`&,`: !N`&\`; `O`',`<0!L`"\`,@.`P
M`# `, `O`&T`80!I`&X`= !A`&D`;@.`O`&8`80!I`&P`8P!L`'4`<P`N`&T`
M<P!P`'@.``````!\````!```````3! ,````)`$P``P````8````#````````
M``,````%````'P```"H```!H`'0`= !P`#H`+P`O`',`=0!P`' `;P!R`'0`
M+@.!M`&D`8P!R`&\`<P!O`&8`= `N`&,`;P!M`"\`/P!K`&(`:0!D`#T`,P`P
M`#$`-@.`P`# ````?`````0``````$P0#````< `2``,````#`````P``````
M```#````!0```!\```!0````: !T`'0`< `Z`"\`+P!W`'<`=P`N`',`<0!L
M`"T`<P!E`'(`=@.!E`'(`+0!P`&4`<@.!F`&\`<@.!M`&$`;@.!C` &4`+@.!C`&\`
M;0`O`',`<0!L`',`90!R`'8`90!R`#(`, `P`# `7P!C`&P`=0!S`'0`90!R
M`&D`;@.!G`%\`:0!N`',`= !A`&P`; !?`&T`80!I`&X`+@.!A`',`< ```!\`
M```!```````3! ,``````%\``P`````````#``````````,````%````'P``
M`&T```!H`'0`= !P`#H`+P`O`'<`=P!W`"X`;0!I`&,`<@.!O`',`;P!F`'0`
M+@.!C`&\`;0`O`&0`;P!W`&X`; !O`&$`9 !S`"\`9 !E`'0`80!I`&P`<P`N
M`&$`<P!P`'@.`/P!&`&$`;0!I`&P`>0!)`$0`/0`Y`#8`9@.`W`#8`90!D`#<`
M+0`Y`#8`,P`T`"T`- `S`# `, `M`#D`,0`U`#D`+0`X`#D`-@.`S`#@.`9@.`T
M`&(`- !E`&8`-P`F`&0`:0!S`' `; !A`'D`; !A`&X`9P`]`&4`;@.``````
M'P````$``````!,$````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M``````````$````"`````P````0````%````!@.````<````(` ```"0````H`
M```+````# ````T````.````#P```! ```#^____$@.```!,````4````%0``
M`!8````7````& ```/[___\:````&P```!P````=````'@.```!\````@.````
M(0```"(````C````) ```"4````F````_O___R@.````I````*@.```"L````L
M````+0```"X```#^____, ```#$````R````,P```#0````U````-@.```/[_
M___]____.0```/[____^_____O__________________________________
M_________________________________________________ ___________
M_________________________________________________ ___________
M_________________________________________________ ___________
M_________________________________________________ ___________
M_________________________________________________ ___________
M________________________________4@.!O`&\`= `@.`$4`;@.!T`'(`>0``
M````````````````````````````````````````````````` ````````!8`
M!0'__________P,````&"0(``````, ```````!&````````````````P*N\
MFH#;Q0$[````@. ````````!$`&$`= !A````````````````````````````
M````````````````````````````````````````````````" @.`"`?______
M_________P``````````````````````````````````````` ````````!$`
M````$ ```````#$`5 !A`&(`; !E````````````````````````````````
M```````````````````````````````````````.``(!`0``` `8```#_____
M````````````````````````````````````````````````& 0```&4:````
M````5P!O`'(`9 !$`&\`8P!U`&T`90!N`'0`````````````````````````
M`````````````````````````````!H``@.$"````!0```/____\`````````
M````````````````````````````````````````````+B ````````%`%,`
M=0!M`&T`80!R`'D`20!N`&8`;P!R`&T`80!T`&D`;P!N````` ```````````
M````````````````````* `"`?_______________P``````````````````
M`````````````````````````````"<`````$ ````````4`1 !O`&,`=0!M
M`&4`;@.!T`%,`=0!M`&T`80!R`'D`20!N`&8`;P!R`&T`80!T` &D`;P!N````
M```````````X``(!! ```/__________````````````````````````````
M````````````````````+P`````0`````````0!#`&\`;0!P` $\`8@.!J````
M````````````````````````````````````````````````` ```````````
M`!(``@.#_______________\`````````````````````````` ```````````
M````````````````<0``````````````````````````````` ```````````
M````````````````````````````````````````````````` ````````/__
M_____________P``````````````````````````````````` ```````````
M``````````````````$```#^_________________________ ___________
M_________________________________________________ ___________
M_________________________________________________ ___________
M_________________________________________________ ___________
M_________________________________________________ ___________
M_________________________________________________ ___________
M_________________________________________________ ___________
M_________________________________________________ ___________
M_________________________________________________ ___________
M_________________________________________________ ___________
M_________________________________________________ ___________
M________________________________________`0#^_P,*` `#_____!@.D"
M``````# ````````1A\```!-:6-R;W-O9G0@.3V9F:6-E(%=O<F0@.1&]C=6UE
M;G0`"@.```$U35V]R9$1O8P`0````5V]R9"Y$;V-U;65N="XX`/0YLG$`````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
"````
`
end

adding a new column to a large table

SQL Server 2000
Windows 2000 Server
I need to add a new column to a table that will likely have millions of rows
at most customer sites. The table currently has one FK and 2 unclustered
indexes. The new column is an int column. When I run the script to add the
column on our test server (table has about 5 million rows) it takes about
1/2 hour. Unfortunately, we can't have that kind of down time on that
table.
Is there a typical method for doing this more efficiently? Would it help to
drop the indexes before and recreate them after or would that end up taking
the same amount of time anyway? What about creating a temp table, copying
that data into the new table and renaming it?Are you trying to add this column in the middle of the other columns, or at
the end of the other columns? If the middle, try adding to the end and see
if that sppeds things up, Im betting thats whats going on.
"Joel Lyons" <NOSPAMJOELL@.NOVARAD.NET> wrote in message
news:uyRcotfZFHA.1456@.TK2MSFTNGP15.phx.gbl...
> SQL Server 2000
> Windows 2000 Server
> I need to add a new column to a table that will likely have millions of
> rows at most customer sites. The table currently has one FK and 2
> unclustered indexes. The new column is an int column. When I run the
> script to add the column on our test server (table has about 5 million
> rows) it takes about 1/2 hour. Unfortunately, we can't have that kind of
> down time on that table.
> Is there a typical method for doing this more efficiently? Would it help
> to drop the indexes before and recreate them after or would that end up
> taking the same amount of time anyway? What about creating a temp table,
> copying that data into the new table and renaming it?
>|||Here's the script:
ALTER TABLE [dbo].[Images] ADD Version tinyint NOT NULL CONSTRAINT
DF_Images_Version DEFAULT 1
I'd guess that adds to the end, no?
"ChrisR" <noemail@.bla.com> wrote in message
news:%23caxC6fZFHA.3364@.TK2MSFTNGP12.phx.gbl...
> Are you trying to add this column in the middle of the other columns, or
> at the end of the other columns? If the middle, try adding to the end and
> see if that sppeds things up, Im betting thats whats going on.
>
> "Joel Lyons" <NOSPAMJOELL@.NOVARAD.NET> wrote in message
> news:uyRcotfZFHA.1456@.TK2MSFTNGP15.phx.gbl...
>> SQL Server 2000
>> Windows 2000 Server
>> I need to add a new column to a table that will likely have millions of
>> rows at most customer sites. The table currently has one FK and 2
>> unclustered indexes. The new column is an int column. When I run the
>> script to add the column on our test server (table has about 5 million
>> rows) it takes about 1/2 hour. Unfortunately, we can't have that kind of
>> down time on that table.
>> Is there a typical method for doing this more efficiently? Would it help
>> to drop the indexes before and recreate them after or would that end up
>> taking the same amount of time anyway? What about creating a temp table,
>> copying that data into the new table and renaming it?
>>
>|||Yes it does. I just realized you are adding these to customer sires. Are you
logging onto the boxes locally, or over the WAN?
"Joel Lyons" <NOSPAMJOELL@.NOVARAD.NET> wrote in message
news:utoFrFgZFHA.3876@.TK2MSFTNGP12.phx.gbl...
> Here's the script:
> ALTER TABLE [dbo].[Images] ADD Version tinyint NOT NULL CONSTRAINT
> DF_Images_Version DEFAULT 1
> I'd guess that adds to the end, no?
> "ChrisR" <noemail@.bla.com> wrote in message
> news:%23caxC6fZFHA.3364@.TK2MSFTNGP12.phx.gbl...
>> Are you trying to add this column in the middle of the other columns, or
>> at the end of the other columns? If the middle, try adding to the end and
>> see if that sppeds things up, Im betting thats whats going on.
>>
>> "Joel Lyons" <NOSPAMJOELL@.NOVARAD.NET> wrote in message
>> news:uyRcotfZFHA.1456@.TK2MSFTNGP15.phx.gbl...
>> SQL Server 2000
>> Windows 2000 Server
>> I need to add a new column to a table that will likely have millions of
>> rows at most customer sites. The table currently has one FK and 2
>> unclustered indexes. The new column is an int column. When I run the
>> script to add the column on our test server (table has about 5 million
>> rows) it takes about 1/2 hour. Unfortunately, we can't have that kind
>> of down time on that table.
>> Is there a typical method for doing this more efficiently? Would it
>> help to drop the indexes before and recreate them after or would that
>> end up taking the same amount of time anyway? What about creating a
>> temp table, copying that data into the new table and renaming it?
>>
>>
>|||We haven't run the script on an actual customer site yet, only on our test
server which is a close resemblance. When we upgrade the customers, we will
likely remote in and run the script on the actual server.
(thanks for taking the time to help)
"ChrisR" <noemail@.bla.com> wrote in message
news:uOYoAMgZFHA.580@.TK2MSFTNGP15.phx.gbl...
> Yes it does. I just realized you are adding these to customer sires. Are
> you logging onto the boxes locally, or over the WAN?
>
> "Joel Lyons" <NOSPAMJOELL@.NOVARAD.NET> wrote in message
> news:utoFrFgZFHA.3876@.TK2MSFTNGP12.phx.gbl...
>> Here's the script:
>> ALTER TABLE [dbo].[Images] ADD Version tinyint NOT NULL CONSTRAINT
>> DF_Images_Version DEFAULT 1
>> I'd guess that adds to the end, no?
>> "ChrisR" <noemail@.bla.com> wrote in message
>> news:%23caxC6fZFHA.3364@.TK2MSFTNGP12.phx.gbl...
>> Are you trying to add this column in the middle of the other columns, or
>> at the end of the other columns? If the middle, try adding to the end
>> and see if that sppeds things up, Im betting thats whats going on.
>>
>> "Joel Lyons" <NOSPAMJOELL@.NOVARAD.NET> wrote in message
>> news:uyRcotfZFHA.1456@.TK2MSFTNGP15.phx.gbl...
>> SQL Server 2000
>> Windows 2000 Server
>> I need to add a new column to a table that will likely have millions of
>> rows at most customer sites. The table currently has one FK and 2
>> unclustered indexes. The new column is an int column. When I run the
>> script to add the column on our test server (table has about 5 million
>> rows) it takes about 1/2 hour. Unfortunately, we can't have that kind
>> of down time on that table.
>> Is there a typical method for doing this more efficiently? Would it
>> help to drop the indexes before and recreate them after or would that
>> end up taking the same amount of time anyway? What about creating a
>> temp table, copying that data into the new table and renaming it?
>>
>>
>>
>|||I just realized...what about the default value? It has to apply that
default value to all the existing rows. Maybe that's what's taking a long
time. I wonder if disabling some level of logging during this update would
speed that up.
"ChrisR" <noemail@.bla.com> wrote in message
news:uOYoAMgZFHA.580@.TK2MSFTNGP15.phx.gbl...
> Yes it does. I just realized you are adding these to customer sires. Are
> you logging onto the boxes locally, or over the WAN?
>
> "Joel Lyons" <NOSPAMJOELL@.NOVARAD.NET> wrote in message
> news:utoFrFgZFHA.3876@.TK2MSFTNGP12.phx.gbl...
>> Here's the script:
>> ALTER TABLE [dbo].[Images] ADD Version tinyint NOT NULL CONSTRAINT
>> DF_Images_Version DEFAULT 1
>> I'd guess that adds to the end, no?
>> "ChrisR" <noemail@.bla.com> wrote in message
>> news:%23caxC6fZFHA.3364@.TK2MSFTNGP12.phx.gbl...
>> Are you trying to add this column in the middle of the other columns, or
>> at the end of the other columns? If the middle, try adding to the end
>> and see if that sppeds things up, Im betting thats whats going on.
>>
>> "Joel Lyons" <NOSPAMJOELL@.NOVARAD.NET> wrote in message
>> news:uyRcotfZFHA.1456@.TK2MSFTNGP15.phx.gbl...
>> SQL Server 2000
>> Windows 2000 Server
>> I need to add a new column to a table that will likely have millions of
>> rows at most customer sites. The table currently has one FK and 2
>> unclustered indexes. The new column is an int column. When I run the
>> script to add the column on our test server (table has about 5 million
>> rows) it takes about 1/2 hour. Unfortunately, we can't have that kind
>> of down time on that table.
>> Is there a typical method for doing this more efficiently? Would it
>> help to drop the indexes before and recreate them after or would that
>> end up taking the same amount of time anyway? What about creating a
>> temp table, copying that data into the new table and renaming it?
>>
>>
>>
>|||Yes, the defualt value will take a bit. But it doesnt seems to me like Ive
ever experienced that severe of slowness, which is what led to my other
questions. Creating with NULL will be much faster of course... but still
thats a long time. I guess try just to add with NULL for timing tests.
"Joel Lyons" <NOSPAMJOELL@.NOVARAD.NET> wrote in message
news:eLFnFbhZFHA.2520@.TK2MSFTNGP09.phx.gbl...
>I just realized...what about the default value? It has to apply that
>default value to all the existing rows. Maybe that's what's taking a long
>time. I wonder if disabling some level of logging during this update would
>speed that up.
> "ChrisR" <noemail@.bla.com> wrote in message
> news:uOYoAMgZFHA.580@.TK2MSFTNGP15.phx.gbl...
>> Yes it does. I just realized you are adding these to customer sires. Are
>> you logging onto the boxes locally, or over the WAN?
>>
>> "Joel Lyons" <NOSPAMJOELL@.NOVARAD.NET> wrote in message
>> news:utoFrFgZFHA.3876@.TK2MSFTNGP12.phx.gbl...
>> Here's the script:
>> ALTER TABLE [dbo].[Images] ADD Version tinyint NOT NULL CONSTRAINT
>> DF_Images_Version DEFAULT 1
>> I'd guess that adds to the end, no?
>> "ChrisR" <noemail@.bla.com> wrote in message
>> news:%23caxC6fZFHA.3364@.TK2MSFTNGP12.phx.gbl...
>> Are you trying to add this column in the middle of the other columns,
>> or at the end of the other columns? If the middle, try adding to the
>> end and see if that sppeds things up, Im betting thats whats going on.
>>
>> "Joel Lyons" <NOSPAMJOELL@.NOVARAD.NET> wrote in message
>> news:uyRcotfZFHA.1456@.TK2MSFTNGP15.phx.gbl...
>> SQL Server 2000
>> Windows 2000 Server
>> I need to add a new column to a table that will likely have millions
>> of rows at most customer sites. The table currently has one FK and 2
>> unclustered indexes. The new column is an int column. When I run the
>> script to add the column on our test server (table has about 5 million
>> rows) it takes about 1/2 hour. Unfortunately, we can't have that kind
>> of down time on that table.
>> Is there a typical method for doing this more efficiently? Would it
>> help to drop the indexes before and recreate them after or would that
>> end up taking the same amount of time anyway? What about creating a
>> temp table, copying that data into the new table and renaming it?
>>
>>
>>
>>
>|||On Tue, 31 May 2005 10:50:16 -0600, Joel Lyons wrote:
>Here's the script:
>ALTER TABLE [dbo].[Images] ADD Version tinyint NOT NULL CONSTRAINT
>DF_Images_Version DEFAULT 1
Hi Joel,
You're right (in your other post) - adding the default is what takes
time.
Consider breaking it in smaller steps:
1. Add a column, keep it nullable - should be fast.
ALTER TABLE dbo.Images
ADD Version tinyint
go
2. Fill the default value. This will take time, but if you use smallish
batches to process the data, locks will be released in between, so your
other applications will be able to proceed. If you have full recovery
model, then make sure that you back up the transaction log in between
(unless you don't mind it growing to accomodate all the changes).
SET ROWCOUNT 50000 -- experiment to get the optimal setting
DECLARE @.rc int
SET @.rc = 1
WHILE @.rc > 0
BEGIN
UPDATE dbo.Images
SET Version = 1
WHERE Version IS NULL
SET @.rc = @.@.ROWCOUNT
-- BACKUP LOG MyDatabase TO MyDatabaseLog
END
SET ROWCOUNT 0 -- never forget to reset ROWCOUNT!!
3. When all rows have been filled, set the NOT NULL constraint and the
DEFAULT:
ALTER TABLE dbo.Images
ALTER COLUMN Version tinyint NOT NULL
ALTER TABLE dbo.Images
ADD DEFAULT 1 FOR Version
Best, Hugo
--
(Remove _NO_ and _SPAM_ to get my e-mail address)|||When you allow nulls and do not provide a default value, it will be very
very quick, because the new rows are not materialized until the page is
re-written... It works sort of like a virtual column... when you provide a
default value, the values must ACTUALLY be written, so the time it would
take is relative to the IO speed.
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Joel Lyons" <NOSPAMJOELL@.NOVARAD.NET> wrote in message
news:uyRcotfZFHA.1456@.TK2MSFTNGP15.phx.gbl...
> SQL Server 2000
> Windows 2000 Server
> I need to add a new column to a table that will likely have millions of
> rows at most customer sites. The table currently has one FK and 2
> unclustered indexes. The new column is an int column. When I run the
> script to add the column on our test server (table has about 5 million
> rows) it takes about 1/2 hour. Unfortunately, we can't have that kind of
> down time on that table.
> Is there a typical method for doing this more efficiently? Would it help
> to drop the indexes before and recreate them after or would that end up
> taking the same amount of time anyway? What about creating a temp table,
> copying that data into the new table and renaming it?
>|||Very interesting info - thanks all!
I'll try some of these ideas and let you know.
-Joel
"Joel Lyons" <NOSPAMJOELL@.NOVARAD.NET> wrote in message
news:uyRcotfZFHA.1456@.TK2MSFTNGP15.phx.gbl...
> SQL Server 2000
> Windows 2000 Server
> I need to add a new column to a table that will likely have millions of
> rows at most customer sites. The table currently has one FK and 2
> unclustered indexes. The new column is an int column. When I run the
> script to add the column on our test server (table has about 5 million
> rows) it takes about 1/2 hour. Unfortunately, we can't have that kind of
> down time on that table.
> Is there a typical method for doing this more efficiently? Would it help
> to drop the indexes before and recreate them after or would that end up
> taking the same amount of time anyway? What about creating a temp table,
> copying that data into the new table and renaming it?
>|||Joel,
Are you adding the new column executing a script in QA or doing it manually
in EM?
Do it in QA, using "alter table".
AMB
"Joel Lyons" wrote:
> SQL Server 2000
> Windows 2000 Server
> I need to add a new column to a table that will likely have millions of rows
> at most customer sites. The table currently has one FK and 2 unclustered
> indexes. The new column is an int column. When I run the script to add the
> column on our test server (table has about 5 million rows) it takes about
> 1/2 hour. Unfortunately, we can't have that kind of down time on that
> table.
> Is there a typical method for doing this more efficiently? Would it help to
> drop the indexes before and recreate them after or would that end up taking
> the same amount of time anyway? What about creating a temp table, copying
> that data into the new table and renaming it?
>
>|||Could you please show the script you use to add a column ?
Regards.
"Joel Lyons" wrote:
> SQL Server 2000
> Windows 2000 Server
> I need to add a new column to a table that will likely have millions of rows
> at most customer sites. The table currently has one FK and 2 unclustered
> indexes. The new column is an int column. When I run the script to add the
> column on our test server (table has about 5 million rows) it takes about
> 1/2 hour. Unfortunately, we can't have that kind of down time on that
> table.
> Is there a typical method for doing this more efficiently? Would it help to
> drop the indexes before and recreate them after or would that end up taking
> the same amount of time anyway? What about creating a temp table, copying
> that data into the new table and renaming it?
>
>|||Hi Joel,
DEFAULT constraint in your script is not an issue,
default value will only apply on new records, not existent records in your
table.
The real issue is NOT NULL - this will require prety huge I/O.
What you can do, run your script to add a new column without NOT NULL.
This will let you use a new column and populate it.
Then when you will able to schedule a time, make it NOT NULL.
Regards.
"Joel Lyons" wrote:
> SQL Server 2000
> Windows 2000 Server
> I need to add a new column to a table that will likely have millions of rows
> at most customer sites. The table currently has one FK and 2 unclustered
> indexes. The new column is an int column. When I run the script to add the
> column on our test server (table has about 5 million rows) it takes about
> 1/2 hour. Unfortunately, we can't have that kind of down time on that
> table.
> Is there a typical method for doing this more efficiently? Would it help to
> drop the indexes before and recreate them after or would that end up taking
> the same amount of time anyway? What about creating a temp table, copying
> that data into the new table and renaming it?
>
>|||Hi Joel,
DEFAULT constraint in your script is not an issue,
default value will only apply on new records, not existent records in your
table.
The real issue is NOT NULL - this will require prety huge I/O.
What you can do, run your script to add a new column without NOT NULL.
This will let you use a new column and populate it.
Then when you will able to schedule a time, make it NOT NULL.
Regards.
"Joel Lyons" wrote:
> SQL Server 2000
> Windows 2000 Server
> I need to add a new column to a table that will likely have millions of rows
> at most customer sites. The table currently has one FK and 2 unclustered
> indexes. The new column is an int column. When I run the script to add the
> column on our test server (table has about 5 million rows) it takes about
> 1/2 hour. Unfortunately, we can't have that kind of down time on that
> table.
> Is there a typical method for doing this more efficiently? Would it help to
> drop the indexes before and recreate them after or would that end up taking
> the same amount of time anyway? What about creating a temp table, copying
> that data into the new table and renaming it?
>
>