sql server replication: best way to keep updated database copy on same server -- sql server replication

You're in the

sql server replication

group:

best way to keep updated database copy on same server

AF
9/29/2005 10:13:05 AM

sql server replication:

Hi,

I was hoping to get some advise on my SQL 2000 server: I would like an
automatically updated copy of the main database kept on the same server. Any
changes made to this copy would NOT be synchronized to the main database,
however, changes made to the main database need to be immediately synched to
the copy. This would give me an up-to-date copy that can be worked with and
manipulated in ways that would be inappropriate for the actual database. Any
thoughts on the easiest solution would be greately appreciated.

thx,

Re: best way to keep updated database copy on same server

Paul Ibison
9/30/2005 9:15:10 AM

AF,
transactional replication and log shipping are often used for reporting
databases. However you say you want to actually manipulate the data - if
this means data changes are required, then the above 2 methods will not work
(log shipping forces the database into read-only mode and tr will probably
have synchronization errors) so a different solution is required. In this
case I'd use either snapshot replication or ship the backups and restore -
obviously both methods will have a sizeable delay in data transfer.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Re: best way to keep updated database copy on same server

AF
9/30/2005 4:46:04 PM

I checked in to transactional replicaiton, which looks promising. If I could
have the main database update/overwrite the copy every 30 minutes or so, that
should work. Since I am not worried about replicating to a different
physical server, do you know if there is a simpler method for such updates?

I appreciate the help,
AF

[quoted text, click to view]

Re: best way to keep updated database copy on same server

Paul Ibison
10/1/2005 12:39:10 PM

I have concerns about using transactional replication for your purposes. You
mention that there will be manipulation of the data on the subscriber. If by
this you mean data changes, this'll likely cause errors and a failure of the
distribution agent. If you're just doing reads then it'll be ok.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages in the sql server replication group.

View Other Months
April 2003
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007

home · blog · groups

Questions? Comments? Contact the dn