|
|
You're in the
sql server replication
group:Scheduling of snapshot agent
sql server replication:
You can install SQL Server 2005 as a named instance on a box having SQL Server 2000 default already there. As for the scheduling, it really depends on how long the snapshot takes. EG if it takes 5 mins, you'd schedule the snapshot agent to run each hour at 1pm, 2pm, 3pm etc and the distribution agent to run once an hour at 1:10pm, 2:10pm, 3:10pm etc. Cheers, Paul Ibison SQL Server MVP, www.replicationanswers.com (recommended sql server 2000 replication book: http://www.nwsu.com/0974973602p.html)
I am not sure what your question is regarding the alerts. It look like your
list is complete. You can install SQL 2000 and SQL 2005 side by side. You should be running the most recent service pack for both versions. The frequency you run your snapshot agent depends on how current you want your data and how long it takes to generate the snapshot. If it takes over an hour to generate your snapshot your distribution agent will not generate it till the snapshot is complete. Your snapshot agent will not try to generate another snapshot while the first snapshot agent is still running. -- Hilary Cotter Director of Text Mining and Database Strategy RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. This posting is my own and doesn't necessarily represent RelevantNoise's positions, strategies or opinions. 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 [quoted text, click to view] "perhiyar" <dba.hilal@gmail.com> wrote in message news:1151481171.031614.149970@b68g2000cwa.googlegroups.com... > When i configured snapshot replication for the database. It was done > accordingly but in replication alerts i found series of > > alerts like: > > 1. agent custom shutdown > 2. agent failure > 3. agent retry > 4. agent success > 5. expired subscription dropped > 6. Subscriber has failed data validation > 7. Subscriber has passed data validation > 8. Subscription reinitialized after validation failure > > Database is running on SQL Server 2000. I have not installed any > service pack is this the problem of service pack? > > Can i install sql server sql server 2005 in parallel with sql server > 2000 enterprise edition on he same machine? > > I have replicated a database as a snapshot replication. I have > scheduled distribution agent to run at the interval of one hour daily > from 9:00 AM to 5:30 PM. Do i also need to schedule snapshot agent > accordingly? What will be optimal schedule depending on the scheduling > of distribution agent? > > Ali Raza Rajput > Database Administrator >
When i configured snapshot replication for the database. It was done
accordingly but in replication alerts i found series of alerts like: 1. agent custom shutdown 2. agent failure 3. agent retry 4. agent success 5. expired subscription dropped 6. Subscriber has failed data validation 7. Subscriber has passed data validation 8. Subscription reinitialized after validation failure Database is running on SQL Server 2000. I have not installed any service pack is this the problem of service pack? Can i install sql server sql server 2005 in parallel with sql server 2000 enterprise edition on he same machine? I have replicated a database as a snapshot replication. I have scheduled distribution agent to run at the interval of one hour daily from 9:00 AM to 5:30 PM. Do i also need to schedule snapshot agent accordingly? What will be optimal schedule depending on the scheduling of distribution agent? Ali Raza Rajput Database Administrator
Paul thanks for reply
I have configured one of our production database on Server A for snapshot replication. First production database is replicated to Server B on LAN (snaphot agent and distribution agent is configured at the frequency of ten minutes on Server A for Server B ). Then Server B replicates that database on WAN, to our head office, to Server C (snapshot agent and distribution agent is configured at the frequency of 1 hour on Server B for Server C). We have 15 users at head office connected to that production database on Server C, out of which 12 users only view that database while 3 users also insert data. Now 12 users are going fine they are getting replicated data accurately. Now my question is that how can i manage rest of three users (who are inserting data) for snapshot replication. Ali Raza Perhiyar Database Administrator [quoted text, click to view] Paul Ibison wrote:
> These default alerts are perfectly normal for use in replication. > You can install SQL Server 2005 as a named instance on a box having SQL > Server 2000 default already there. > As for the scheduling, it really depends on how long the snapshot takes. EG > if it takes 5 mins, you'd schedule the snapshot agent to run each hour at > 1pm, 2pm, 3pm etc and the distribution agent to run once an hour at 1:10pm, > 2:10pm, 3:10pm etc. > Cheers, > Paul Ibison SQL Server MVP, www.replicationanswers.com > (recommended sql server 2000 replication book: > http://www.nwsu.com/0974973602p.html)
I probably misunderstand - you have users editing the subscriber data which
has been snapshotted? It's difficult to imagine a case where data being edited is allowed to be overwritten by the next synchronizing of the snapshot process - have I missed something? Cheers, Paul Ibison SQL Server MVP, www.replicationanswers.com (recommended sql server 2000 replication book: http://www.nwsu.com/0974973602p.html)
If you are interested in propagating changes between servers, then snapshot
replicaiton is not the right technique. You could use merge with a single publisher which can connect to the other 2 servers, or peer-to-peer replication, or bidirectional transactional replication. Is there a posibility of conflicts between the data changes on each server? If so, then the simplest option would be merge replication. Cheers, Paul Ibison SQL Server MVP, www.replicationanswers.com (recommended sql server 2000 replication book: http://www.nwsu.com/0974973602p.html)
yeah previously these users editing the production database on Server
A.Now i want them to edit production database on Server C (which is replicated through Server B) and those edited records should be replicated back to the Server A via Server B. I think i have to consider 2 way snapshot replication. Flow diagram of snapshot replication: Server A : Publisher+Distributor for ServerB Server B : Publisher+Distributor for Server C and Subscriber to Server A Server C : Subscriber to Server B 1. I have scheduled snapshot agent for duration 9:30 AM to 5:30 PM and distribution agent from 9:40 AM to 5:40 PM on Server B (which is publisher for Server C) now next day our developer started the machine of Server C on 9:45 AM. But when he browse the production database, all the tables were blanked. I do not know what had happened then i manually started agent, it worked. Though I have set the snapshot propety of article to "Delete data in the existing table that matches the row filter " from default "Drop the existing table and recreate it" .. Is it because of that coz i want agent to append only updated data, not the whole table. 2. I am monitoring the snapshot agent and distribution agent.I have noticed the latency for distribution agent upto 352373 (msec) on LAN. I think it is abnormal what do you say? 3. As for as i think total time taken by distribution agent is "latency +duration". Am i right or it is just duration Ali Raza Perhiyar Database Administrator [quoted text, click to view] Paul Ibison wrote:
> I probably misunderstand - you have users editing the subscriber data which > has been snapshotted? It's difficult to imagine a case where data being > edited is allowed to be overwritten by the next synchronizing of the > snapshot process - have I missed something? > Cheers, > Paul Ibison SQL Server MVP, www.replicationanswers.com > (recommended sql server 2000 replication book: > http://www.nwsu.com/0974973602p.html)
thanks for reply
and what about latency is it ok Ali Raza Perhiyar Database Administrator [quoted text, click to view] Paul Ibison wrote:
> If you are interested in propagating changes between servers, then snapshot > replicaiton is not the right technique. You could use merge with a single > publisher which can connect to the other 2 servers, or peer-to-peer > replication, or bidirectional transactional replication. Is there a > posibility of conflicts between the data changes on each server? If so, then > the simplest option would be merge replication. > Cheers, > Paul Ibison SQL Server MVP, www.replicationanswers.com > (recommended sql server 2000 replication book: > http://www.nwsu.com/0974973602p.html)
Depends on loads of factors - the amount of transactions, bandwidth etc but
you can use tracer tokens to measure this on SQL Server 2005 to see if it is acceptable. Certainly usually much lower than log-shipping, where the logs can only be taken at a max frequency of one a minute. Cheers, Paul Ibison SQL Server MVP, www.replicationanswers.com (recommended sql server 2000 replication book: http://www.nwsu.com/0974973602p.html)
Thanks paul for your kind reply that really helps me
Ali Raza Rajput Database Administrator [quoted text, click to view] Paul Ibison wrote:
> Depends on loads of factors - the amount of transactions, bandwidth etc but > you can use tracer tokens to measure this on SQL Server 2005 to see if it is > acceptable. Certainly usually much lower than log-shipping, where the logs > can only be taken at a max frequency of one a minute. > Cheers, > Paul Ibison SQL Server MVP, www.replicationanswers.com > (recommended sql server 2000 replication book: > http://www.nwsu.com/0974973602p.html)
Don't see what you're looking for? Try a search.
|
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 |