all groups > sql server replication > november 2006 >
You're in the

sql server replication

group:

Database Replication



Database Replication Ryan
11/28/2006 7:44:00 PM
sql server replication: we have setup a sql2005 server for reporting. we want to replicate the
transaction databases which used for live applications to that server such
that all reports will be generated in that server.

This reporting server is supposed read-only and with let's say 30 mins delay
from production data.

With this requirement, should we use the transactional replication or there
any method?

Thanks,
Ryan

Re: Database Replication Paul Ibison
11/29/2006 12:00:00 AM
Ryan,
transactional replication is often used for this type of reporting
requirement. You could also enhance the system by using the snapshot
committed isolation levels to maintain access while the distribution agent
is running. The main 'competitor' technology on SQL Server 2005 is database
mirroring with database snapshots. There's no detailed list of pros and
cons, but as I'm a replication guy I'll point out that mirroring doesn't
support FTI and you can't take back ups of snapshots :)
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .

Re: Database Replication ReasonRules NO[at]SPAM gmail.com
11/30/2006 6:38:30 AM
Paul-
I have client who maintains a local SQL 2005 database which has
numerous bulk updates applied throughout the day. They wish to
replicate (most of) this data to their web host which is in another
city. They are trying to decide whether to use Transactional
Replication or once-per-day Merge Replication. (Concurrency is not a
big issue here).

What method would you recommend? What are the most important
considerations?

Thanks,

Paul




[quoted text, click to view]
Re: Database Replication ReasonRules NO[at]SPAM gmail.com
11/30/2006 8:12:21 AM
Thanks, Paul!

Does Transactional require an "always on" connection to the subscriber?


[quoted text, click to view]
Re: Database Replication Paul Ibison
11/30/2006 3:20:07 PM
Merge is generally slower. If there are numerous updates to the same row,
then it can approach transactional times, but I have rarely seen cases of
someone claiming it to be faster. It's geared up for offline updates at teh
subscriber and conflict resolution, neither of which you'll need. I'd
definitely go with transactional.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .

Re: Database Replication Paul Ibison
11/30/2006 4:58:10 PM
No - as long as there is a connection when the distribution agent is
scheduled to run you're ok (different for immediate updating subs but not
relevant in your case).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .

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.
AddThis Social Bookmark Button
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