P2P reindexing

I was looking at setting up multiple SQL Server 2005 Standard edition
servers using Peer-to-Peer Replication with the goal being able to
reindex one server at a time so as not to have any downtime (via locked
tables). Would this work?
Also, I know log-shipping to a standby server only requires 1 CPU
license which is attractive as CPU licenses are pricey. Still, if I
use P2P only for this reindex purpose (including three nodes for
voting) with only one server being used by customers/users, is a 1 CPU
license good enough?
Thanks!
MichaelI can't seem to find an answer anywhere for these questions:
Can I run ALTER INDEX REBUILD seperately between a live SQL 2005 server
and the hot-standby server? This way, if the live table is locked
during this operation, the hot-standby server would take over the CRUD
statements.
Is it allowed to have a single CPU license for two SQL 2005 server if
one is a hot-standby-only server and the standby-only server is only
used for failover purposes. Note that when tables are locked during
ALTER INDEX REBUILD, I assume the failover would kick in. Is that
possible?
The goal is to have no downtime for executing ALTER INDEX REBUILD.
Thank you,
Michael

p2p replication error too many arguments specified

Currently, we have peer-to-peer replication on two servers (server1 and
server2).
I added a few columns using sp_repladdcolumn stored procedure. Rows inserted
at Server1
are replicated to Server2 without problems, and rows inserted Server2 can
not be replicated to Server1
because of the error below. Any help is appreciated. thanks, D
Command attempted:
if @.@.trancount > 0 rollback tran
(Transaction sequence number: 0x0000008600000EE7000400000000, Command ID: 1)
Error messages:
Procedure or function sp_MSins_dboCustomers0823818373 has too many arguments
specified. (Source: MSSQLServer, Error number: 8144)
Get help: http://help/8144
Procedure or function sp_MSins_dboCustomers0823818373 has too many arguments
specified. (Source: MSSQLServer, Error number: 8144)
Get help: http://help/8144
Paul,
First time at this. Not sure how to quiesce the system. Does
this mean change db to single user?
I've used sp_repladdcolumn to add two columns to the publisher's article.
Both tables at subscriber and publisher do reflect the new columns.
However, stored procedures at the publisher do not receive the changes
while stored procedures at subscriber do.
When a new record is inserted into the table at publisher, the
new record does get distributed. When a new record is inserted
at the subscriber, the record got an error when being distributed.
Thanks, D
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:OwyqlhJwHHA.4612@.TK2MSFTNGP04.phx.gbl...
> 1.. Quiesce the system.
> 2.. Execute the data definition language (DDL) statements to modify the
> schema of published tables. For more information about supported schema
> changes, see Making Schema Changes on Publication Databases.
> 3.. Before resuming activity on published tables, quiesce the system
> again. This ensures that schema changes have been received by all nodes
> before any new data changes are replicated
> The general advice is to do things as above - is that how you made the
> schema change?
> I'm also interested in what has actually happened - do the tables have an
> equal number of columns now? Can you also compare the text of the 2
> sp_MSins_dboCustomers procs (pub and subs) and see if they are different.
> If so, can you tell us which one is correct.
> Cheers,
> Paul Ibison
>

P2P reindexing

I was looking at setting up multiple SQL Server 2005 Standard edition
servers using Peer-to-Peer Replication with the goal being able to
reindex one server at a time so as not to have any downtime (via locked
tables). Would this work?
Also, I know log-shipping to a standby server only requires 1 CPU
license which is attractive as CPU licenses are pricey. Still, if I
use P2P only for this reindex purpose (including three nodes for
voting) with only one server being used by customers/users, is a 1 CPU
license good enough?
Thanks!
MichaelI can't seem to find an answer anywhere for these questions:
Can I run ALTER INDEX REBUILD seperately between a live SQL 2005 server
and the hot-standby server? This way, if the live table is locked
during this operation, the hot-standby server would take over the CRUD
statements.
Is it allowed to have a single CPU license for two SQL 2005 server if
one is a hot-standby-only server and the standby-only server is only
used for failover purposes. Note that when tables are locked during
ALTER INDEX REBUILD, I assume the failover would kick in. Is that
possible?
The goal is to have no downtime for executing ALTER INDEX REBUILD.
Thank you,
Michael

P2P reindexing

I was looking at setting up multiple SQL Server 2005 Standard edition
servers using Peer-to-Peer Replication with the goal being able to
reindex one server at a time so as not to have any downtime (via locked
tables). Would this work?
Also, I know log-shipping to a standby server only requires 1 CPU
license which is attractive as CPU licenses are pricey. Still, if I
use P2P only for this reindex purpose (including three nodes for
voting) with only one server being used by customers/users, is a 1 CPU
license good enough?
Thanks!
MichaelI can't seem to find an answer anywhere for these questions:
Can I run ALTER INDEX REBUILD seperately between a live SQL 2005 server
and the hot-standby server? This way, if the live table is locked
during this operation, the hot-standby server would take over the CRUD
statements.
Is it allowed to have a single CPU license for two SQL 2005 server if
one is a hot-standby-only server and the standby-only server is only
used for failover purposes. Note that when tables are locked during
ALTER INDEX REBUILD, I assume the failover would kick in. Is that
possible?
The goal is to have no downtime for executing ALTER INDEX REBUILD.
Thank you,
Michael