View Complete Post
We setup a replciation peer-to-peer source / destination has sperated publisher and distributor each.
The subscription set without initialize. But the source db got changed before replication indeed. Then we find there was something sent by destination distributor which hold all the process for a long time.
The question is: why is it not sent from source to destination? Does the destination try to question the change but very slow, and get the change back very quickly?
Under normal non-replicated circumstances, we add maintenance plans, scheduled weekly, to rebuild indexs in our SQLServer databases. We have implemented peer to peer replication to run a software project from a major application vendor and the vendor is
stating that "index maintenance plans are unsupported" in this implementation. In order to rebuild indexes, we therefore would need to break replication, rebuild indexes, then re-establish replication.
In short, can index maintenance plans be run against all nodes in a peer-to-peer replication scenario without effecting replication?
I have a WCF service using one-way net.msmq transport to deliver messages to a high availability cluster.
I have followed a few articles I have found on setting up WCF in a cluster environment and essnetially have the following queues
Node A: private$\MI/ManagementInformationService.svc
Node B: private$\MI/ManagementInformationService.svc
Although I am not sure why I need the local queues.
I've installed the WCF application into IIS7 on Node A and Node B. I;ve configured both nodes to the following address:
So, I configure my Web Servers to deliver the MI to the clustered endpoing via WCF net.msmq binding.
At this point, everything works and as messages hit the clustered queue, they are picked up by one of the nodes and processed. However, when I fail over the cluster, the second node does not automatically spring into life, as I would expect it to with WAS.
However, if I browse the WSDL for my service on the now-current node, then it does indeed spring into life and process the messages off the queue.
So I turn on WCF tracing, IISReset fire up the WSDL, IISReset (to flush the WCF Trace log) then see the following:
A warning: Cannot detec
My environment is comprising of 2 SQL servers setup with P2P replication in SQL 2008,ÃÂ 2 Web servers connect to only one SQL server at a time and make changes to the published tables andÃÂ 2 Application servers which connects to both the SQL servers all the timeÃÂ but they only read data.We chose P2P since my app servers are in different locations which read data from both the SQL servers and we use it as HA solution.Since we are changing data at only one SQL server, thought we should never get update-update conflicts but we are now on the same node.A conflict of type 'Update-Update' was detected at peer 3 between peer 1 (incoming), transaction id 0x0000000000725ca2 and peer 1 (on disk), transaction id 0x00000000007259e9 (Source: MSSQLServer, Error number: 22815)We are making changes only at Server A and Server B is my backup server.I made a varchar field updated in 1 row on a table in server A then it getsÃÂ replicated to Server Bthen I made the same field updated for 160 rows on the same table in Server A then it gets replicated to Server Bthen I reverted back the change made to the field on all 160 rows on the same table in Server A then my replication failing with Update-Update conflict.I'm not sure whats causing this because I'm not making any change
Dear friends ,
I am using SQL Server 2008 Express edition in my laptop ,I would like to do high availability samples such as Replication,Mirroring,and Log shipping in my laptop , i have two instances .is it possible to do samples (replication,mirroring,log shipping) plz
guid me how to do.
thanks in advance
Hi, sorry but i'm a sql dummy...:-)
I setup a sql 2008 p2p replication for a database.
Can i specify, on a jbdc connection string, the path of the 2 sql server for automatic failover?
I try failoverPartner variable, but this is only for database mirroring.....
Can u help me?
Thanks in advance
I have P2P replication going from say DB1 to DB2 and we are now just bought a couple more servers say DB3 and DB4. Our goal is to retire DB1 and add one more node in our replication. So we are thinking of setting up our replication so that it'll
first - DB1 to DB2 to DB3 to DB4
Second - when all replications are setup. We'll drop DB1.
The plan seems techincally possible, but I don't know it'll works.
Have anyone done anything like this before? if yes, could you share with us if there is any problem you have encountered.
Thanks a lot in advance.
I am in engineering design field and fairly new to SQL server. One of our applications use SQL server 2005.
I have setup Peer-to-peer replication. As soon as replication setup is completed, I start getting error for logread.exe and distrib.exe on satellite server (this is in India).
I get below error (same for logread.exe):
Distrib.exe Application Error , Application failed to initialize properly(0xx0000142)click ok to terminate the application
I have tried hard to resolve this issue but no success. I have deleted the replication many times and tried recreating but still no success.
user id I have used for Snapshot agent, log read agent has enough DBO permissions on both servers.
Please if someone can help me resolving this issue.
We demonstrate creating a peer-to-peer processing platform where multiple players function together for a common purpose: getting your work done.
MSDN Magazine June 2009
Here we examine the typical cloud platform architecture and some common architectural patterns, along with their implementation on the Windows Azure offering from Microsoft.
MSDN Magazine May 2009
Learn how you can peer-enable business applications by allowing them to share state in a serverless peer network.
MSDN Magazine July 2008
P2P applications face a number of barriers preventing their wide adoption as a productivity solution. Fortunately Windows Vista improves the situation, as you'll learn here.
MSDN Magazine October 2006
Reliability requires the capacity to execute a sequence of operations in a deterministic way, even under exceptional conditions. This allows you to ensure that resources are not leaked and that you can maintain state consistency without relying on application domain unloading (or worse, process restarts) to fix any corrupted state. Unfortunately, in the.NET Framework, not all exceptions are deterministic and synchronous, which makes it difficult to write code that is always deterministic in its ability to execute a predetermined sequence of operations. In this article Stephen Toub will show you why, and explore features of the .NET Framework 2.0 that help you to mitigate these situations and write more reliable code.
MSDN Magazine October 2005
MSDN Magazine September 2003
Peer-to-peer applications such as Napster, Gnutella, and Scour that communicate as peers sharing and receiving information are becoming commonplace as a means for users connected on large networks to take advantage of the vast resources available to them. The Microsoft .NET Framework provides a rich platform for building P2P apps. This article explains the concepts that make up peer-to-peer applications. The peer-to-peer application model, discovering other peers, and querying peers for information are discussed. The article goes on to cover the System.Net namespace for the use of Internet protocols, the System.Web.Services namespace for exposing Web Services, and firewall and port issues. Finally, the role of the .NET Framework in simplifying the design of powerful peer-to-peer applications is outlined.
MSDN Magazine February 2001