|
|
|
SSCertifiable
       
Group: Moderators
Last Login: Thursday, May 09, 2013 12:38 PM
Points: 6,462,
Visits: 1,384
|
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Monday, January 24, 2005 4:59 PM
Points: 175,
Visits: 1
|
|
we use snapshot replication because we do not require the most recent data and the data at the publisher changes once a day/couple of times a week and these are mostly lookup tables and the Subscribers can be disconnected totally if they are not updating.
--Ramesh Sydney
Edited by - ramesh on 10/10/2002 12:56:40 AM
Ramesh
|
|
|
|
|
SSC Journeyman
      
Group: General Forum Members
Last Login: Thursday, April 27, 2006 8:47 AM
Points: 93,
Visits: 1
|
|
I've used transactional where ever possible. However, I am using Snaphot in one case - our database is duplicated to SQLBase. SQLBase ODBC drivers just don't support Transactional! (7.0.1 if anyones interested.)
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Tuesday, March 01, 2005 11:41 AM
Points: 258,
Visits: 1
|
|
In this time of zero latency between systems, snapshot does seem a bit outdated.
But you were right-on with the focus on Business requirements. In many of the large corporations I have worked with, it is not uncommon for management systems to be refreshed only once a week. These are usually centralized datawarehouses - pulling in data from diverse regions and OLTP systems. Even if they went to daily refresh, a snapshot or other type of full refresh is usually in order.
If you are a database professional, business requirements are preeminent.
What's the business problem you're trying to solve?
|
|
|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: Yesterday @ 8:46 AM
Points: 2,750,
Visits: 1,410
|
|
I use snapshots when I need to duplicate a live environment for testing purposes. 1. Receive change request. 2. Snapshot the live to a development machine. 3. Test on the development machine. 4. Make amendments to the development machine and test. 5. Apply to live. 6. GOTO 1.
LinkedIn Profile
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Wednesday, April 12, 2006 2:07 AM
Points: 9,
Visits: 1
|
|
I use transactional replication to gather data fom 33 different SQL servers. A snapshot would be totally useless hense to bandwith issues.
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Sunday, April 24, 2005 7:41 PM
Points: 10,
Visits: 1
|
|
We use snapshot replication. The client is creating a schedule throughout the day. They have to explicitly publish the schedule when it is done, which is a one-shot deal each day and has to be undert he control of the user. I have set up a push [only] subscription.Then I wrote a vb6 app that with the push of ONE button, runs some queries, then executes snapshot.exe (creating a snapshot of the resulting tables from the queries) and lastly runs the distribution object to publish to the web database. It took a LOT of time to learn what I needed to solve this problem, but it has worked out beautifully for the client.
|
|
|
|
|
SSCertifiable
       
Group: Moderators
Last Login: Thursday, May 09, 2013 12:38 PM
Points: 6,462,
Visits: 1,384
|
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Friday, March 18, 2011 9:37 AM
Points: 1,
Visits: 11
|
|
This article is very good, The only Unknown variable to me, (having no experinece on replication) is Performance Issues.
What are the performance issues associated with all types of replication ?
Thanks
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Monday, September 08, 2003 12:00 AM
Points: 3,
Visits: 1
|
|
Replication is good but it can be daunting if you dont know how to do it right, believe me you only get one chance to get it right.
My experience with replication is, if you don't need to query the data on the remote server, use Log-Shipping instead, keep it as a StandBy.
Use transactional replication, it takes a little bit more work than snapshot but bandwith wise is the way to go, unless you have gigabit ethernet all over your network or you dont really move that much traffic on your db.
Performance wise get a good server, specially the one where you put the distributor, the db itself won't choke but your performance will take a hit, anything that takes cpu cyles and memory address space affects performance.
And if you have the dough and want to get real fancy, get Legato RepliStor or Legato Co-Standby, This are the best tools, I've used them both and they are a snap to configure and administer. All your data is replicated instantly and you get a cluster/ failover environment that works like a champ. This tools are some real jewels.
Hope this helps
Gerald Nelson MCP/MCDBA
Gerald Nelson MCP/MCDBA
|
|
|
|