read-only database. Both are SQL 2000+SP4. The web server reads the
read-only database. At times, there will be lots of changes in the data
entry database, thus lots of replications to the read-only database. I
am concerned that the replication may lock the data in the read-only
database, causing slow response to the web server.
I would like to use row versioning so that the read-only database can
supply old data when the same row is being written by replication. I
read that row versioning is a feature in SQL 2005. Is there any
versioning capability in SQL 2000?
Thanks(betbubble@.gmail.com) writes:
Quote:
Originally Posted by
I replicate (transactional replication) my data entry database to a
read-only database. Both are SQL 2000+SP4. The web server reads the
read-only database. At times, there will be lots of changes in the data
entry database, thus lots of replications to the read-only database. I
am concerned that the replication may lock the data in the read-only
database, causing slow response to the web server.
>
I would like to use row versioning so that the read-only database can
supply old data when the same row is being written by replication. I
read that row versioning is a feature in SQL 2005. Is there any
versioning capability in SQL 2000?
No.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx
No comments:
Post a Comment