In a transactional replication scenario, should i consider rebuilding
indexes on the subscriber articles? Does that place a lock on the
subscriber? most of those tables are used only for select queries.
Thanks.
IN SQL 2000 is does, with online=on in SQL 2005 EE it does not.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"rt" <rtemple3@.gmail.com> wrote in message
news:1171914789.341188.155130@.l53g2000cwa.googlegr oups.com...
> In a transactional replication scenario, should i consider rebuilding
> indexes on the subscriber articles? Does that place a lock on the
> subscriber? most of those tables are used only for select queries.
> Thanks.
>
|||Just to add to Hilary's anwser, you could use dbcc indexdefrag if concerned
about table locks required when using dbcc dbreindex for SQL Server 2000. In
SQL Server 2005, as well as the Alter Index versions of these DBCC
statements, there is the posibility of using READ_COMMITTED_SNAPSHOT
isolation in the client queries.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
Wednesday, March 21, 2012
Rebuild indexes on subscriber?
Labels:
articles,
consider,
database,
indexes,
lock,
microsoft,
mysql,
oracle,
rebuild,
rebuildingindexes,
replication,
scenario,
server,
sql,
subscriber,
thesubscriber,
transactional
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment