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


Embed this content in your HTML

Search

Report adult content:

click to rate:

Account: (login)

More Channels


Showcase


Channel Catalog


Channel Description:

Discussions on SQL Server Replication

older | 1 | .... | 63 | 64 | (Page 65) | 66 | 67 | .... | 181 | newer

    0 0

    Hello,

    We received the following error on a subscribers agent

    "The Merge Agent failed after detecting that retention-based metadata cleanup has deleted metadata at the Subscriber for changes not yet sent to the Publisher. You must reinitialize the subscription (without upload)."

    On the support site it mentioned we might be able to fix this problem without a complete reinitialization. Does anyone know how to fix this? I can't find any documentation how to execute a partial initialization.

    The subscriber has a high latency connection to the publisher and a complete initialization might take a few days which we need to avoid if all possible.

    Thanks for the help!

    Jeremy


    0 0
  • 08/29/13--07:34: Snapshot will not run
  • I am trying to create a new publication on a SQL 2008R2 instance that already has two publications running successfully. When the snapshot agent kicks in it is failing. The job created has the following in the history:

    Step 2:

    The replication agent encountered a failure. See the previous job step history message or Replication Monitor for more information.  The step failed.

    Step 3:

    Executed as user: domain\user. Agent shutdown. For more information, see the SQL Server Agent job history for job 'instance-publication-20'. [SQLSTATE 01000] (Message 20557)  Replication-Replication Snapshot Subsystem: agentinstance-publication-20 failed. The replication agent encountered a failure. See the previous job step history message or Replication Monitor for more information.  The step failed. [SQLSTATE 42000] (Error 14151).  The step failed.

    I have tried turning on logging by adding the relevant params to the job step, running from the command line, switching the NT user to myself (a sysadmin), changing snapshot from network path back to default path and publishing other databases. None of this has made any difference, the folder/files for the snapshot do not get created and I can't get any useful output.

    I also switched the owner of the database to be my own account and ran checkdb (no errors). It's compatibility level is 90.


    0 0

    With the help of MANY online articles, I finally have SQL Server 2008 R2 now replicating correctly to a SQL Server 2008 R2 Express database on a Windows 7 machine but when I started testing my Access 2003 application on the replica, I discovered a problem. Certain processes, which work fine against the original SQL Server database, fail with a "Recordset not updateable" error message when run against the SQL Express database. After chasing many ghosts, I ran across a comment stating that "linked ODBC tables with no unique index will always fail" with the not updateable error. But of course, I KNEW all my tables had a primary, unique key - they've always been that way. After confirming this fact on my SQL Server database, I examined the Express version and discovered that all my primary keys (but not the columns themselves) had been removed and a new field called rowguid had been appended to the table as datatype "uniqueidentifier" !!! The Express database was initially "loaded" from the publisher during the first replication process.

    Any ideas on what happened (and how to avoid it) would be greatly appreciated!


    0 0

    Hi All,

    Scenario:

    1 publisher & 2 transactional replication subscribers (all SQL 2005)

    I am getting the below error on publisher for one of the subscribers:

    "Length of LOB data to be replicated exceeds configured maximum 65536"

    --This is seen on only 1 subscriber.

    I am aware of changing the 'max text repl size' parameter (http://technet.microsoft.com/en-us/library/ms179573.aspx)

    Questions:
    1. what is confusing me how it affected only 1 of the subscriber and not both. Both subscribers have the same data published.
    2. Can I find out the exact column that caused this issue?
    As the issue has occured about 5 days (and as there were no proper alerts said), we came to know about this issue late.

    3. Where can I find the replication logs ? I have already checked Replication monitor, eventviewer on Publisher(which shows the above error)?
    Any help is highly appreciated!!

    Thanks




    0 0

    Hi,

    Can anyone help me with my issue...

    I have one (merge) publication (data are managed from, in my case, web application) with several subscribers (data are managed by PDA devices).
    There are around 35 tables that need to be synchronized.
    Because records in each of those tables can be managed in both publication and subscribers, for eachsp_addmergearticle, I've set "@article_resolver = N'Microsoft SQL Server Subscriber Always Wins Conflict Resolver'" because data collected from PDA are more relevant that ones managed from web application, thus Subscribers always must win.

    BUT when I sync. there is still conflicts that requires manually resolving (through "Microsoft Replication conflicts Viewer"). Normally, all I need to do is to "Submit Winner". All I need is that "submitting winner" to be automatically because these kind of "situation" is normal in my application.

    To be more specific, I'll put one scenario for one table (with values from one set of parameters):

    Table settings in DB and in script from publication:

    Table1 (NPID, ParamID, ParamValue)

    exec sp_addmergearticle @publication = N'MyDatabase_Rep', @article = N'Table1', @source_owner = N'dbo', @source_object = N'Table1', @type = N'table', @description = N'', @creation_script = N'', @pre_creation_cmd = N'drop', @schema_option = 0x000000B208034FF1, @identityrangemanagementoption = N'auto', @pub_identity_range = 1000000, @identity_range = 1000, @threshold = 80, @destination_owner = N'dbo', @force_reinit_subscription = 1, @column_tracking = N'false', @article_resolver = N'Microsoft SQL Server Subscriber Always Wins Conflict Resolver', @subset_filterclause = N'', @vertical_partition = N'false', @verify_resolver_signature = 0, @allow_interactive_resolver = N'false', @fast_multicol_updateproc = N'true', @check_permissions = 0, @subscriber_upload_options = 0, @delete_tracking = N'true', @compensate_for_errors = N'false', @stream_blob_columns = N'false', @partition_options = 0

    through web application I've put following values:

    NPID = 98
    ParamID = 299
    ParamValue = 5.00000000

    through one of the PDAs for the same parameter I've put following values:

    NPID = 98
    ParamID = 299
    ParamValue = 35.00000000

    According to the table setting in the replication that subscriber always wins I thought that ParamValue = 35.0000000 will overwrite ParamValue = 5.0000000 BUT values in Table1 was same and when I check "View conflicts" I've notice that there were conflict :"The same row was updated at both 'WM_EU - 7c67c309222d' and 'SERVER.MyDataBase'. The resolver chose the update from 'WM_EU - 7c67c309222d' as the winner." and I need to confirm "Submit Winner"...

    All I need to do is to, somehow, set the replication to handle this conflicts automatically.

    Thanks,

    Stefan


    0 0

    I am new in Merge replication and don't know where to get help.

    i have two databases on same server and one is working fine and secondone is giving me below error. Althought everything is same as it. i have even tried to change not replicate table schema but still getting following error. Can you please help me

    Error messages:
    The schema script 'Office_488.sch' could not be propagated to the subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
    Get help: http://help/MSSQL_REPL-2147201001
    Could not drop object 'dbo.Office' because it is referenced by a FOREIGN KEY constraint. (Source: MSSQLServer, Error number: 3726)
    Get help: http://help/3726


    0 0

    Hello ,

    I know above error because of FOREIGN KEY constraint ,

    i dont want to remove foreign key at both the end and want source table as it is to destination

    what shoul i do.......


    Rahul Hundare


    0 0

    I have created a new Index on one of the columns,

    the table belongs to this column is replicated,

    after adding new index, this index is not moved over to replicated table.

    Please suggest


    k


    0 0

    Hello,

    Until today we used routers and static ip's to make a vpn between the two computers we wanted to have the replication. But in  this case this is not possible because they cannot change the equipment they have. 

    How can i create a transactional replication between 2 remote servers which are not connected through vpn? 

    We have static ip in both of the places.

    thank you


    0 0

    Hi All,

    I'm working with SQL Server 2008 R2 Enterprise.

    I was just reading about Republishing as a way to keep a DR site up to date.

    http://msdn.microsoft.com/en-us/library/ms152553.aspx

    (This link if for 2012, but I'm hoping this would work on a 2008 R2 as well.)

    I don't have an environment ready to test this yet so I was wondering if there was anyone out there who has Republished a subscriber before.

    A couple of things I was wondering about is if anyone knows what happens when the primary site fails and we want to start sending data directly to the subscriber/publisher at the DR site. Is that kind of a set up possible?

    ANother thing is the diagram in the link doesn't show it, but can the subscriber/publisher at he DR site have its own distributor? 

    Tia,

    Mike


    MikeG


    0 0

    Hi Team,

    Can I ENABLE the Change Data Capture(CDC) feature on Subsription Database and its associated replicated tables?

    Should I have to consider any other aspects while Enabling? risk involved?

    (Publisher: Oracle 11g

    Subscriber and Distributor: SQL server 2008 R2)
    Thanks.


    0 0

    Hello, 

    I'm trying to set up peer to peer replication entirely through scripts, but I'm having troubles with creation of all the sp_MSins_..., sp_MSdel_... and sp_MSupd_... stored procedures. As I understand they should be created automatically through sp_addarticle when the @schema_option parameter has the 0x02 flag. However, no such thing occurs - the stored procedures aren't created. I'm using the sp_addarticle e.g. this way:

    exec sp_addarticle @publication = N'Test', @article = N'Tags', @source_owner = N'dbo',

    @source_object = N'Tags', @type = N'logbased', @description = N'', @creation_script = N'',

    @pre_creation_cmd = N'drop', @schema_option = 0x0000000008035DDF,

    @identityrangemanagementoption = N'manual', @destination_table = N'Tags', @destination_owner = N'dbo',

    @status = 24, @vertical_partition = N'false', @ins_cmd = N'CALL [sp_MSins_dboTags0745679936]',

    @del_cmd = N'CALL [sp_MSdel_dboTags0745679936]', @upd_cmd = N'SCALL [sp_MSupd_dboTags0745679936]'

    I would be grateful for any help in this matter.

    Best regards,

    Tadeusz Dracz




    0 0
  • 04/02/13--07:23: log shiping
  • i am setting up log shipping for  about 30 dbs,   everything working fine,  i need to log ship  structure/objects of  a db not data.  is it possible in log shipping?

    any other better way of taking structure of databases?

    thanks

    v


    0 0

    We've merge replication configured in our environment(1 Publisher, 3 Subscribers) and We know by default merge replication is bi-directional. Its working fine in case of inserts i.e, if a row is inserted at publisher then it's getting updated at subscriber and vice versa. The real issue is, if row gets deleted at publisher then its getting deleted at subscriber but, if a row gets deleted in any of 3 subscribers then its not getting deleted at publisher.

    When a row is deleted at publisher then it's getting updated in MSmerge_tombstone(Publisher). But, in case of subscriber, the corresponding row(rowguid) is not getting updated in MSmerge_tombstone(Subscriber). I think that might be the issue, even merge delete trigger exist on these tables(Subscriber). Please help me out, as it is a production issue.

    Publisher(2008R2 sp1-Enterprise), Subscribers(2008R2 sp1-Standard)

    0 0

    Hi,

    We use snapshot replication.

    In order to reduce the down time of the snapshot, we are replicating it with a temporary name and at the end of the replication we rename the table to the original name.

    The rename is done with the paramaneter  @post_snapshot_script of sp_addpublication

    because of security reasons I can't put any file on the SQLServer machine.

    Is there any other way to reduce the snapshot time without placing file on the SQLServer machine.


    Regards, Asi Pesa


    0 0

    I have table Structure Is like 


    USE [VmcSmppLogs76New]
    GO
    /****** Object:  Table [dbo].[SMPP_BulkTransactionDetails]    Script Date: 09/02/2013 10:48:26 ******/
    SET ANSI_NULLS ON
    GO
    SET QUOTED_IDENTIFIER ON
    GO
    SET ANSI_PADDING ON
    GO
    CREATE TABLE [dbo].[SMPP_BulkTransactionDetails](
    	[TransactionDetailsID] [bigint] NOT NULL,
    	[TransactionID] [nvarchar](100) NULL,
    	[SenderID] [varchar](25) NULL,
    	[MobileNo] [varchar](50) NULL,
    	[UserID] [bigint] NULL,
    	[Message] [nvarchar](2000) NULL,
    	[UDH] [varchar](100) NULL,
    	[SMSNo] [int] NULL,
    	[MessageType] [int] NULL,
    	[Priority] [int] NULL,
    	[GatewayID] [int] NULL CONSTRAINT [DF_SMPP_BulkTransactionDetails2_GatewayID]  DEFAULT ((1)),
    	[MessageStatus] [tinyint] NULL CONSTRAINT [DF_SMPP_BulkTransactionDetails2_MessageStatus]  DEFAULT ((0)),
    	[OpMessageID] [varchar](100) NULL,
    	[SentOn] [datetime] NULL,
    	[DeliveredOn] [datetime] NULL,
    	[CreateDate] [datetime] NULL CONSTRAINT [DF_SMPP_BulkTransactionDetails2_CreateDate]  DEFAULT (getdate()),
    	[ThreadID] [int] NULL CONSTRAINT [DF_SMPP_BulkTransactionDetails2_ThreadID]  DEFAULT ((1)),
    	[status] [int] NOT NULL CONSTRAINT [DF_SMPP_BulkTransactionDetails2_status]  DEFAULT ((1)),
    	[IsFlash] [int] NULL CONSTRAINT [DF_SMPP_BulkTransactionDetails2_IsFlash]  DEFAULT ((0)),
    	[ErrorCode] [varchar](50) NULL CONSTRAINT [DF_SMPP_BulkTransactionDetails2_ErrorCode]  DEFAULT ('000'),
    	[CAFId] [varchar](50) NULL,
    	[IMSI] [varchar](100) NULL,
     CONSTRAINT [PK_SMPP_BulkTransactionDetails2] PRIMARY KEY CLUSTERED 
    (
    	[TransactionDetailsID] ASC
    )WITH (PAD_INDEX  = OFF, STATISTICS_NORECOMPUTE  = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS  = ON, ALLOW_PAGE_LOCKS  = ON) ON [PRIMARY]
    ) ON [PRIMARY]
    
    GO
    SET ANSI_PADDING OFF

    In the Above table when I insert millions of records then I got error

    Java.SqlBatchUpdateException: Violation Of Primary KEY constraints ' PK_SMPP_Bulk TransactionDetails2' . Can not insert duplicate key in object 'dbo.SMPP_BulkTransactionDetals'.


    0 0

    Hi All,

    I had configured Sql replication using Sql subscriber,distributer and oracle publisher.Earlier i had removed the Sql subscriber and now when i again added the subscriber i am getting this error in my snapshots agent.i tried to reinitialize the subscriber but still it didn't resolve the error.Kindly Help me out with it. 

    Skipping file 'ADDRESS 2.sch' because it has already been delivered for a previous article or by a previously interrupted snapshot.

    Error messages:
    The process could not bulk copy into table '"dbo"."ADDRESS"'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20037)
    Get help: http://help/MSSQL_REPL20037
    Invalid object name 'dbo.ADDRESS'. (Source: MSSQLServer, Error number: 208)
    Get help: http://help/208
    To obtain an error file with details on the errors encountered when initializing the subscribing table, execute the bcp command that appears below.  Consult the BOL for more information on the bcp utility and its supported options. (Source: MSSQLServer, Error number: 20253)
    Get help: http://help/20253
    bcp "DW_TRN_08"."dbo"."ADDRESS" in "G:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\ReplData\unc\MESE01_DISTRIBUTION_START_1\20130826095142\ADDRESS_2.bcp" -e "errorfile" -t"\n<x$3>\n" -r"\n<,@g>\n" -m10000 -SCIDCSWDMESMPI01 -T -w (Source: MSSQLServer, Error number: 20253)
    Get help: http://help/2025

    0 0

    Hello Pros,

    I enabled or created replication using the 'text book rules'. My replication monitor reports that publisher is OK, distributor is OK, subscribers are OK! Yet, when I make or update the publisher database, I couldn't see the update reflected on the subscribers!How do I solve this please?

    Also, one message from one of the agents states "NO REPLICATED DATA AVAILABLE"

    I've also observed that replication on some of my database only takes effect on tables (I'm limiting my service delivery to replicating only tables) with a PRIMARY KEY CONSTRAINT (at least from my observation). Please why is that so. Will appreciate responses.

    Thank you.


    0 0

    Hi,

    I have 26 publishers/distributors with a central subscriber.

    Sometimes distribution database and log becames too big, I'm not sure why.

    At his moment, I have a distribution log with 184GB, database with 219GB and the publication log with 890MB

    The property IsSyncWithBackup is disabled in the distribution and publication database.

    So, what should I check to identify the cause of this problem ?

    Thank you !


    Dennes - Se resolveu, classifique a mensagem, por favor - [http://www.bufaloinfo.com.br] NOVO DVD Segurança no ASP.NET : http://www.bufaloinfo.com.br/LearingSeriesSegurancaASPNET2.asp


    0 0

    Hi,

    I belived that in a transaction replication we could schedule the snapshot agent to create snapshots once a day (for example) so if a subscriber needs initialization it could use this snapshot, but ignore it if not needed.

    In fact I found information about this in this link - http://technet.microsoft.com/en-us/library/ms151785.aspx - "When snapshots are generated after a subscription is initialized, they are not applied to a Subscriber unless a subscription is marked for reinitialization."

    I have a transactional replication with scheduled snapshots, but the snapshot is always re-initializing subscriptions when is executed. It's a central subscriber model, so I have 26 publishers/distributors  with daily scheduled snapshots and a central subscriber.

    A few hours ago this happend again : At the snapshot schedule all the push subscriptions to the central subscribers was initialized again.

    How can I change this ? I would like only to initialize subscriptions that realy needs this.

    Thank you !


    Dennes - Se resolveu, classifique a mensagem, por favor - [http://www.bufaloinfo.com.br] NOVO DVD Segurança no ASP.NET : http://www.bufaloinfo.com.br/LearingSeriesSegurancaASPNET2.asp


older | 1 | .... | 63 | 64 | (Page 65) | 66 | 67 | .... | 181 | newer