.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Post New Web Links

Replication monitoring

Posted By:      Posted Date: October 01, 2010    Points: 0   Category :Sql Server


On replication monitor publisher is not in connected status.when i am trying to add publisher it is giving message like it was already in connected status.And then i tried to connect distributor then i am getting message

login failed for user .the user is not associated with a trusted sql server connection :error 18452

Authentication mode is in mixed mode.but still i am getting this error.

We are using sql server 2005,standard eddition.

So please help on this issue..

Thanks in Advance..



View Complete Post

More Related Resource Links

Replication Monitoring Questions

We have a pretty extensive replication topology at our organization. The
publications are 99% transactional with a couple of snapshots thrown in for
articles that do not change very often. these are used for some mission
critical BI processes, so making sure they are in sync is one of my top

I am finding it pretty much impossible to ensure that everything is up to
date without manually opening each publication/ subscription in replication
monitor and verifying that the flow of transactions is behaving properly.
This process takes literally hours for me to complete. I had created a job to
run sp_publication_validation against all of the publications coupled with
alerts to email me when validation failed, and this seemed to be working fine
until this morning. During my morning checklist routine, I found two
publication marked as "Critical Performance," with each having 57 seconds of
latency. When I opened the Distributor to Subscriber History tab, I found
both had a status of "Initial snapshot is not available," and apparently had
not been updating properly for roughly a week. My job did not pick these off
as failing validation. I manually ran a subscription validation against both,
and no results were ever returned.

My question to

Replication Monitoring Tools


Hi, Can anyone suggest a Replication Monitoring Tool? We have like 200 servers to monitor. Its been very had for us to manage replicatoin in Replication Monitor. I m looking for something that gives us better view of the Replication flow like Errors, Latency etc..


Thank you

SharePoint's Sandbox: Developing, Deploying and Monitoring Sandboxed Solutions in SharePoint 2010


The challenge in SharePoint development has always been the balance between creating and deploying solutions that you can trust not to damage or impair a SharePoint farm. A new feature in SharePoint 2010, called Sandboxed Solutions, enables farm administrators to feel comfortable that the SharePoint farm is safe, gives site collection administrators the authority to manage applications in their site collection, and provides developers with the flexibility to create solutions they know will be deployed in a safe and rapid manner.

Paul Stubbs

MSDN Magazine November 2009

C++ Q&A: Performance Monitoring, Managed Extensions, and Lock Toolbars


In the June 2004 issue of MSDN®Magazine, I described a class called ShowTime that you can use to do simple performance monitoring for your app. ShowTime uses its constructor/destructor to record the start/stop times of its existence so you can instantiate it in a block of code like so: { ShowTime st(_T("Total time is:")); // some lengthy operation } .

Paul DiLascia

MSDN Magazine September 2004

merge replication system tables fragmentation issue

I have Merge replication going on in my environment. The problem is that system tables like MSmerge_content, MS merge _tombstone and MSmerge_genhistory are getting fragmented. We are rebuilding indexes time to time daily. But we want some good fix. Just send some good idea guys?

peer to peer replication, drop and add article of same name

We have peer-to-peer replication set up on our system (2005 EE). I would like to change the metadata of one of the tables (many of the tables actually, but right now I'm just trying to test out the process with just one table). As this is a high-availability system, I would like to stop the replication, make the changes on one node, verify that the changes are working, make the same changes on the other node, then re-enable replication. The ddl changes to the table are extensive enough that I have to clear them before executing. So I will handle re-populating the tables in a later step. Right now I'm just testing the process of stopping, doing ddl, then restarting. I am trying to implement this using scripts so as to minimize my clicking (and thus potential for mistakes) when doing it for real. I find that if I do the following process using the SSMS interface it goes smoothly with no errors (note that each step is conducted on both nodes unless specified): stop sync agents manually remove article: tblName1 with 'publications properties window' close 'publications properties window' make ddl changes to tblName1 (change column names, add columns etc. to a particular table) manually add article: tblName1 with 'publications properties window' re-enable agents But if I try the following, I get 'Peer-To-Peer topologies require identical articles in publications at all n

Transactional replication: Updates to one of my columns (sometimes) does not get replicated from the

hi, This is my scenario: I have a varchar(max) column on a table that is replicated to other servers. I have a stored procedure that does and update to this column and other columns on the table. This is done inside a transaction that also includes other updates. When I call the stored procedure, this one varchar(max) column's value is not replicated. When I just run the single update statement on its own, the value is replicated. Anyone know something about this? Thanks!    

Steps by Step document for configuration Merge Replication in 2005

Hi , Can anyone provide link to configure Merge Replication in 2005 with print screen.Also let me know the difference between Transcation level and Merge Replication. regards Vijay  

transactional replication and sp_MSupd tables

Hi thre, My target server keeps running sp_MSupd sp for different values in profiler and synch status shows "delivering replication commands" I keep waiting but this never ends. and ultimately we run a snapshot and it can't be applied. So recreate the whole replication again. It runs fine for a while but again, the sp_MSupd sp starts running on the target server and the replication goes down again. I don't know how to fix this. any advices?   Regards

Real-time data replication

Are there any ways to replicate sql server production database to a standby database? I notice that there is a feature called 'continuous replication', does it do in real-time? what is the time-lag? Are there any potential data loss (i.e., production transaction committed but production db corrupted before the transaction is sent to standby)? Is the standby database available for read access during the replication?

SQL Server 2005 Merge Replication

We did the following: We setup a database with all of standard tables, views, etc. We then put in place merge replication for a few of the tables within this database, including a tables called "Areas". We can execute SQL statements to insert rows into this table fine. We then applied an update script for this database to change a few tables by adding fields and changing indexes, etc.  We didn't change the "Areas" table though. After the update to the database structure, we get an error when trying to insert into this "Areas" table. The error message was the following: The insert failed. It conflicted with an identity range check constraint in database 'AETest', replicated table 'dbo.Areas', column 'AREPrimaryId'. If the identity column is automatically managed by replication, update the range as follows: for the Publisher, execute sp_adjustpublisheridentityrange; for the Subscriber, run the Distribution Agent or the Merge Agent.  The statement has been terminated.   What would cause such a problem and how do we resolve it?  The structure of the "Areas" table before and after the update is the following: USE   [AETest] GO /****** Object: Table [dbo].[Areas] Script Date: 08/24/2010 17:42:36 ******/ SET   ANSI_NULLS ON GO SET   QUOTED_IDENTIFIER ON GO SET   ANSI_PADDING ON

Merge Replication: How to give read access on snapshot share to a sql account

Hello All, I want to give read access to an sql account(not windows account). Can it be given or not. Someone please tell. Thanks saandii777

transactional replication falling behind. millions of transactions in sp_brosereplcmds

Hi, Hi All, we have transactional replication set up with all the agents running at source database. The synchronization status is stuck at "delivering replication transactions". The replication latency in replication monitor says excellent. when I check sp_browsereplcmds. it ever ends. It has over more than millions of rows of output. We were having trouble with this replciation recently because at the source db. they run a large batch. So we decided to schedule snapshot agent to run exactly after that batch but the snapshot doesn't seem to helping out with the latency. what should be done to resolve the issue. Please help. thanks.

SQL 2008 geography type replication

Hi, I am attempting to get merge replication going between two SQL 2008 servers.  So far, everything has gone off without a hitch with one exception.  We use spatial data on a daily basis in my organization, so we implemented the geography data type.  This data type seems to be causing all of our replication issues.  I can easily create publications and subscriptions for each article in the entire database except the geography field. The error is as follows: "The Merge Agent failed because the schema of the article at the Publisher does not match the schema of the article at the Subscriber. This can occur when there are pending DDL changes waiting to be applied at the Subscriber. Restart the Merge Agent to apply the DDL changes and synchronize the subscription." The real kicker is that the schemas are exactly the same.  If I set the publication to drop and recreate the subscription article, then to convert the geography data type, it works without issue, but then we run into issues with our publication database not matching exactly with our subscription database, which could cause many potential problems with our web front end.   Is there a known issue with replicating the geography data type?  Any help is very much appreciated! - Chad  

Replication falling behind over a WAN

I’ve been stuck on a replication problem for a few weeks now and am getting rather desperate.   We’ve been using replication of our production databases successfully for a couple years now to a local server for reporting purposes, but now we’re attempting to also use it over a WAN for disaster recovery in a remote location.  Our current setup is as follows:   5 production databases on 5 separate servers 5 distributors on 5 separate servers 1 subscriber for all replicated databases   Now we’re trying to add 5 more subscribers for disaster recovery, using the original publications and distributors.  All databases involved are SQL 2005 and we’re using transactional replication with push subscriptions.  So far I’ve been able to get replication working for 3 of the 5 databases, but as soon as the snapshot is delivered for a fourth, replication starts falling behind for that database only, and it never catches up.  Transactions are replicating successfully, but just not nearly fast enough.   I’ve tried replicating each of the two remaining databases separately as the fourth instance, and I’ve tried stopping replication to everything except for these databases, and I get the same results.  The remaining two databases do happen to be the biggest (2-4 GB) and the busiest (up to 400,000 dist

One way replication

I want to achieve replication of a SQL Server 2008 database over a one way connection, meaning that I can transfer files from the source database machine to the target database machine but not the other way around. Besides file transfer there is no means of communication between the servers. The source database will have to be online continuously. The target database too, but it will be used for reading only. How could I get this done? I have tried log shipping. It works but the restore taking place at the target database requires an exclusive lock on the database. But I do not want to abort any sessions on the target database.   Any ideas? Thanks in advance, Frans
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend