Are you the publisher? Claim or contact us about this channel

Embed this content in your HTML


Report adult content:

click to rate:

Account: (login)

More Channels


Channel Catalog

Channel Description:

Discussions on SQL Server Replication

older | 1 | .... | 109 | 110 | (Page 111) | 112 | 113 | .... | 181 | newer

    0 0

    I am using transaction replication In my Environment. 
    Question: At the time when batches completed from Application team, daily it will take  5  to 10min to apply all commands to replicated database, but from last one weak it is taking 2 to 3 and half hour.
    Can anybody suggest what might be the reason and solution ?

    Resone I think 
    There are more indexes on replicated databae than Production
    In Replicated mdf and ldf files are both on same serveranything else ? 

    Environment on both servers prod as well as replicated

    SQL Server 2008 r2 Standard
    Windows server 2008r2 enterprise
    CPU 64 (Hyper threading Enable)
    64 GB Memory

    0 0

    Hi All,

    I am working on validating replication at the subscriber. When I use 'Validate subscription' I get the following

    Table 'ABC' might be out of synchronization. Rowcounts (actual: 20037794, expected 20037794). Checksum values (actual: 16237222667544, expected: 16237222314440).

    I replicate only particular tables using initiate from backup with pull subscription, Index or store procedures are not replicated. I do not use filter also.. When I send a tracer alert it is a success, but when I do validate subscription I get the above checksum mismatch though the row matches. I feel the replication is running fine as no error threw up but still checksum mismatches.

    when I run 'sp_publication_validation' it gave me positive result. please advise why the checksum value mismatch though the replication is running fine.


    Best Regards Moug

    0 0

    Hi Gurus, I am facing very uncommon issue  when setting up transactional replication. My instance is running on MSSQL 2005 SP3 and same instance act as Distributor and Publisher.

    Step1: Created Distributor with no issues.

    Step2: Enable Pblisher - Same instance and a database under this instance runnning in full recovery mode.

    Step3: Create Publication - Went thru all the steps and selected couple tables(articles) to create initial snapshot. After provide a name to the publication, click ok - its throwing following error for both articles:

    TITLE: New Publication Wizard

    SQL Server Management Studio could not create article 'abc_Table'.


    An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)


    The article 'abc_table ' does not exist. Changed database context to '<publisher_DB> '. (Microsoft SQL Server, Error: 20027)


    Both tables have primary key and available in publisher database. I did setup n number Transactional replications and did not see this kind of error so far. Did not see any help when googled/Binged, Any help is highly appreciated. Thanks in advance for your help.


    Thanks, TTeam

    0 0

    Here are the error messages, any help will be greatly appreciated.  Would like to know if there's a way to see the records that is causing the error and if not, can we skip it?  

    ORA-01455: converting column overflows integer datatype (Source: MSSQL_REPL_ORACLE, Error number: 1455)
    Get help: http://help/1455

    Heterogeneous Logreader encountered an error in call to LoadReplCmds when processing state 'FETCH'. (Source: MSSQL_REPL, Error number: MSSQL_REPL22037)
    Get help: http://help/MSSQL_REPL22037

    tae yang

    0 0

    We have 3 nodes of P2P, A, B,C, and firstly specified B as distributor, when setup topology, sql makes C as distributor as well. So only 2 nodes act as distributor. Actually I want remote server acts as distributor but no such option to choose during configure topology. How can we achieve that?

    Also, do you have any replication monitor solution in case one node fails and can send out email?


    0 0
  • 11/15/14--19:10: Transaction Replication
  • Hi,

          This is vionth ,our dba team  has to decide to move transaction replication from one to another server

    our scenario like this

    server A



    server B


    server A-server B have latest data 

    server C



    server D


    server C-server D have oldest data

    now,our requirement is we want move latest data of(server A-server B) to(server C - server D) by backup or some other way without stopping replication.

    Is this possible? If possible plz give me a suggestion



    0 0

    Hello Experts,

    I'm using merge replication on sql server 2008 R2, with one publisher and three subscribers. 

    I've observed that, the tables are uploading updates to the publisher around 1000, but downloads at another subscriber is showing as around 6 times more.

    ex: at subscriber A, for table X, 1000 updates were uploaded. now when I see at another subscriber B, for the same table X,

    total updates downloaded are 6000.

    is there anything going on? or replication monitor is misleading? please suggest.

    Cheers, Vinod Mallolu

    0 0


    We are upgrading our server from SQL Server 2008 R2 Std. Ed.  to SQL Server 2014 Std. Ed.

    Our server works with Merge and Transactional publications.

    Our current problem happens when trying to generate the first snapshot using the snapshot agent. Since this is the first time, the snapshot will create all the system tables related with replication and the error happens when creating the table MSmerge_conflict_<publication>_<article> because now the snapshot agent is trying to create the constraints from the <article> (a table in our case)  with the same name, so it brings the conflict of having duplicated constraints names and because of that the snapshot agent fails. This didn't happen on 2008 because the snapshot agent didn't try to create the constraints before.

    This is the error that we see on the Snapshot Agent Status: There is already an object named"NewAccountPermission" in the database. Could not create constraint or index. See previous errors.

    The exact T-sql statement that is failing is shown on the replication monitor:

    Error messages:
    Message: There is already an object named 'NewAccountPermission' in the database.
    Could not create constraint or index. See previous errors. 
    Command Text: CREATE TABLE [dbo].[MSmerge_conflict_Roster_AccountPermissions](
    [AccountPermissionID] [int] NOT NULL CONSTRAINT [NewAccountPermission]  DEFAULT ([dbo].[getNewAccountPermissionID]()),
    [PermissionName] [varchar](255) NULL,
    [Description] [varchar](255) NULL,
    [rowguid] [uniqueidentifier] ROWGUIDCOL  NOT NULL

    Digging a bit further I searched and compared the snapshot files that creates this table. Here it can be seen that the snapshot files only differ on the creation or not of the constraint.

    Here is an extract o f the 2014 file called AccountPermissions_3.cft

    CREATE TABLE [dbo].[MSmerge_conflict_Roster_AccountPermissions](
    [AccountPermissionID] [int] NOT NULL CONSTRAINT [NewAccountPermission]  DEFAULT ([dbo].[getNewAccountPermissionID]()),
    [PermissionName] [varchar](255) NULL,
    [Description] [varchar](255) NULL,
    [rowguid] [uniqueidentifier] ROWGUIDCOL  NOT NULL

    Here is the 2008 version of the same file:

    CREATE TABLE [dbo].[MSmerge_conflict_Roster_AccountPermissions](
    [AccountPermissionID] [int] NOT NULL,
    [PermissionName] [varchar](255) NULL,
    [Description] [varchar](255) NULL,
    [rowguid] [uniqueidentifier] ROWGUIDCOL  NOT NULL

    Any ideas on what is going on? Do I have to configure some properties on the publication now to disallow creating the constraints on the msmerge_conflict table?

    Thank you,

    Alejandro Rivera

    0 0
  • 11/17/14--20:07: Can I specify P2P route
  • As last post said, we have 3 nodes of P2P, A(located in HK) , B (US),C (HK) , and when setup publisher A we specified B as distributor, when setup topology, sql makes C as distributor as well. So only 2 nodes act as distributor. Currently replicated data flow is:

    A to C:  A --> B (distributor) --> C              ---  here is the big problem since B is long distance!

    B to C: B (distributor) --> C               ---is normal and acts as expected.

    C to A: C(distributor) --> A                ---is normal and acts as expected.

    A < --> B     ---is normal and acts as expected.

    So the problem is: A and C are all located in same place, so can I change the route of replicated data flow to 

    A to C:  A --> C (distributor) --> C     

    Another question is, currently we stopped subscriber A --> B (distributor) --> C route, only enable  B (distributor) --> C route, so I must set publication A's properties to Never expires, is that right method for keep such long not running subscriber? We need to keep B and C server as warm-backup server. we don't want to rebuild the topology so far since the db is too big and time consuming.


    0 0
  • 11/18/14--07:20: How to kill sleeping spid
  • Finding too many user wise sleeping spid when i execute sp_who2, finding too difficulty in killing one by one.

    requesting your help in guiding me how to proceed to kill all sleeping user wise spid at once.

    0 0

    Need help in IIS8 application pool, as i am getting an error message after creating and allocated to site, the same demo site is working in default app pool but not in newly created apppool.

    Server Error in 'Demo' Application.
    Required permissions cannot be acquired.
    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
    Exception Details: System.Security.Policy.PolicyException: Required permissions cannot be acquired.
    Source Error:
    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

    new app pool has been created under .net version 2.0

    0 0

    the history message from the step:

    Date19/11/2014 08:41:11
    LogJob History (Expired subscription clean up)

    Step ID1

    Job NameExpired subscription clean up

    Step NameRun agent.
    Sql Severity16
    Sql Message ID1934
    Operator Emailed
    Operator Net sent
    Operator Paged
    Retries Attempted0

    Executed as user: IBA\xxx. DELETE failed because the following SET options have incorrect settings: 'ANSI_NULLS, QUOTED_IDENTIFIER'. Verify that SET options are correct for use with indexed views and/or indexes on computed columns and/or filtered indexes and/or query notifications and/or XML data type methods and/or spatial index operations. [SQLSTATE 42000] (Error 1934).  The step failed.

    when I run the step manually I get:

    Msg 1934, Level 16, State 1, Line 1
    DELETE failed because the following SET options have incorrect settings: 'ANSI_NULLS, QUOTED_IDENTIFIER'. Verify that SET options are correct for use with indexed views and/or indexes on computed columns and/or filtered indexes and/or query notifications and/or XML data type methods and/or spatial index operations.
    Msg 20709, Level 16, State 1, Procedure sp_MScleanup_conflict, Line 66
    The merge process could not clean up the conflict table "[MSmerge_conflict_recordings_items]" for publication "recordings".

    I think I know which table (items in db recordings). it has a computed field with a replicated text index on it.

    the computed field definition is:

    (ltrim(isnull([item_title],'')+' ')+isnull([item_desc],'')) which are 2 other fields in the table nvarchar allowing nulls.

    what do I need to do to stop the cleanup job from crashing.




    0 0
  • 11/19/14--22:33: sql server
  • i have sql server which get by the computer i want to install the sql server and run this program how could be possible please give me information.

    0 0

    Hi ,

    We are using transactional replication between 2012 and 2088 R2 servers.Replication is configured on several databases but it is failing  with below error only on one Database.

    Replication-Replication Distribution Subsystem: agent I'job name' failed. The distribution agent failed to create temporary files in 'C:\Program Files\Microsoft SQL Server\110\COM' directory. System returned errorcode 5.

    Login has write permission on this folder.Are there any other reasons?

    Please let me know if there is any solution for this.

    Thanks in advance.

    0 0

    Dear All,

    I have a problem with my Always-on cluster with 3 nodes and 3 availability groups

    Node 1 is the Primary and sometimes the 2 other nodes give the following error in the logs]

    Warn [GUM] Node 3: I was detected as a slow node by Node : 1

    The other problem i have is event id 1196

    Cluster network name resource 'Cluster Name' failed registration of one or more associated DNS name(s) for the following reason : DNS operation refused

    In the SQL log for the primary node it sais DNS: End of slow operation

    I have two questions :
    How do i solve this and
    Does the one have to do with the other ?


    Pascal Galindo

    0 0


    We can monitor replication using replication monitor but i would like to get report every day in the morning which supposed to show me that which replication last synchronized when and were there any errors or not?

    we have almost 100 pub and subscription so its good to get report in the email. Writing query to find these information but need help for tsql.

    Replication status report including last synchronization timestamp, pub name, sub name, comments, pub db name, sub db name

    Thank you in advance.....

    0 0

    I have a publication that is running on 2012 SQL server.  I added several tables, some stored procedure and some views.  Then I selected 'view snapshot agent service' and selected start.  It says running, and then says '9 articles published' (or something like that) but the number is incorrect.  It should be a LOT more than that.  Then when I look at the subscriber, it doesn't have the new tables.  Thanks for any help you can offer.

    0 0

     I have a SQL server 2005, and created a replication function. when I run  the snapshort agent, I found the opration will run the sys.sp_MSsetup_partition_groups, but need a long time, and can't stop it, I don't know what is the problem about the snapshort agent, and sys.sp_MSsetup_partition_groups is running for what?

    0 0

     Hi, I m trying to create a subscription to SQL Server 2000 server from SQL Server 2014 (Publisher and Distributor). But the distribution agent is failing with the error saying :

      SQL server Native Client 1.0 does not support connections to SQL Server 2000 or earlier versions. Client unable to establish connection. 

     How to fix this issue? A linked server has been created on Publisher but its not editable (Greyed out). Can someone help ?

    Thank you!


    0 0

    Dear All,

    We are using SQL Server 2012 with SP2. Recently we started replication our database from DC to DR site through Always On Configuration. After two Days we observerd that our  disk containing log file is having 10 MB space left out of 665 GB. We tried Shrinking the log file but size remins the same. Please help as it is affecting performance our application and database.

older | 1 | .... | 109 | 110 | (Page 111) | 112 | 113 | .... | 181 | newer