Quantcast
Channel: SQL Server Replication forum
Viewing all 4054 articles
Browse latest View live

Snap-shot replication

0
0

Hi Team,

Last Thursday i have configured snapshot replication at that time it was showing successfully but today i have checked it was failing. below error:

Replication-Replication Transaction-Log Reader Subsystem: agent trans-1 failed. The process could not execute 'sp_replcmds' on 'ggg2'. and

Executed as user: NT AUTHORITY\SYSTEM. Replication-Replication Snapshot Subsystem: agent xxxx failed. Unable to start execution of step 2 (reason: Error authenticating proxy sds\subb2, system error: Logon failure: unknown user name or bad password.).  The step failed. [SQLSTATE 42000] (Error 14151).  The step failed.

Now i got the correct credentials please suggest me where can i have change.

Greatly appreciate anybody help on this.


subu




access to snapshot folder

0
0

Hi All,

Am working on a transactional replication between different domains (say A and B). My plan is to create pull subscription with all agents running in distributor(here distributor and subscriber are same). I place the snapshot folder in domain B and gave access to domain account to that folder which also runs the snapshot agent. When I started the snapshot agent I got the error 'snapshot agent could not access the folder', 
Step -1 -> I unchecked the default folder and gave a named new share folder which located is in same domain B.In this situation also I got a message 'XXX is not a valid path, or it refers to a file instead of a folder. Enter the path to an existing folder'before giving ok.
step -2 -> Hence I checked if the folder can be accessed from publisher using the snapshot agent credentials, which is a success.. after this testing I again did the step 1 now this also succeed.

Now, it's working fine. But wondering how this credential/permissions testing I did in my Step-2 resolved the issue. as I got a error message 'XXX is not a valid path, or it refers to a file instead of a folder. Enter the path to an existing folder' at first and when I did the credential/permissions testing it resolved it.
Please explain why?

Best Regards,
Mughilan



Best Regards Moug

Merge replication and Snapshot replication monitoring

0
0

Hi All,

I have mere publication with 56 subscriptions. I need to monitor their synchronization status twice in a day.

I want to do it using TSQL. Like i will create a table for that and i will schedule a job, which inserts the replication status records and Using SSRS i will to create a report for replication monitoring.

Can anybody help me on this.



Distribution database & In memory

0
0

Hi,

Can I use the In memory new SQL Server 2014 feature on the distribution database.

We use a distributor with a lot of publications and subscriber and facing locks problem on the commands table.

Perhaps, the new lock manager process of the In memory feature can help us.

Is there anyone tried this configuration ??

Thks

Fred

Dropping existing subscriber from a pualisher who has multiple subscriber in Transactional Replication

0
0

Hi Everyone,

We have a transactional replication(one publisher and multiple subscribers). If I drop one of subscribers, will this cause any locking or performance problem for publisher or other subscribers? I am going to do  that using SSMS.

Thanks

Aspet


A.G


How can I view the publishing server of a particular subscribed table?

0
0

Hi All,

I have a table 'REPLI_2' and when I run sp_depends I can see all the subscriptions related SP's like

dbo.sp_MSupd_dborepli_2
dbo.sp_MSins_dborepli_2
dbo.sp_MSdel_dborepli_2

However when I query 'MSreplication_objects' or 'MSreplication_subscriptions' I do not see any entries for the mentioned table 'REPLI_2'

Note : This  table is also a publisher to a different subscriber.

Confused any help would be appreciated.

I want to know from where I am getting the data?


aa




Transactional replication and user-defined data types and table types

0
0

I am new to SQL Server 2012 Transactional Replication. I set up a Publication and a Subscription and selected all tables, views, stored procedures, and user-defined functions. Both the Publisher and the Subscriber are running SQL Server 2012.

The Snapshot Agent worked fine, and the Log Reader is working fine. However, the Distribution Agent job is failing with an error saying "Cannot find data type udt_X", which is a user-defined table type.

I checked the Subscriber database and found that 16 of the 18 user-defined table types had been successfully replicated. What I am trying to understand is why there were two that were not. I have compared them with the ones that were and can find no difference that would seem to account for it.

Both of the missing table types are used by the same, single stored procedure. The error I am getting comes when the Distribution Agent attempts to replicate that stored proc. 

There is also one non-table user-defined data type that did not get replicated. That one I can understand, however, because it is not actually used anywhere.

Why are UDT's not listed in the articles in SSMS, or in sysschemaarticles, or in the script generated by SSMS? If they are not replication articles, why are any of the UDT's being replicated? I assume it is replicating objects that are dependencies for the articles, but if so why would it not replicate these two UDT's when there is a stored proc that definitely has a dependency on them?

Thanks,

Ron Rice

 

Ron Rice



log shipping

0
0

hai ,

i am facing a problem in log shipping that is 

i have created a standby database in secondary server but its not updating , when we update primary database in the primary server.

may i know the reason for that.


Replication problem with Cumulative Update 1 for SQL Server 2012 SP2

0
0

 

Hello,

Last week, I updated my SQL Server 2012 SP1 to SP2 and then Cumulative Update 1.
I did it without any reboot between SP2 and Cumulative Update 1.

Before the update, my replications (Merge and Transactional) were working fine.

After the update - Although data replicate, I get constantly these errors :

- Transactional Replication - Log Reader Agent : 
The last step did not log any message! (Source : MSSQL_REPL, Error number : MSSQL_REPL22037)

- Merge Replication (on all subscribers - All are SQL 2005 Express) : 
The merge process could not perform metadata cleanup by retention in the basis of "DatabaseName" data. If the problem persists, try increasing the query timeout process or reduce the retention period. When solving the problem, restart the synchronization with detailed and specify an output file to write to record history. (Source: MSSQL_REPL, Error Number: MSSQL_REPL-2147199466) 
Get help: http: // help / MSSQL_REPL-2147199466

Conflict of operand types: bigint is incompatible with uniqueidentifier (Source: MSSQLServer, Error number: 206) 
Get help: http: // help / 206 

Conflict of operand types: int is incompatible with uniqueidentifier (Source: MSSQLServer, Error number: 206) 
Get help: http: // help / 206


Also, if I execute the stored procedure : sp_mergemetadataretentioncleanup
I get these errors :
Msg 206, Level 16, State 2, Procedure sp_mergemetadataretentioncleanup, Line 63 
Conflict of operand types: bigint is incompatible with uniqueidentifier 
Msg 206, Level 16, State 2, Procedure sp_mergemetadataretentioncleanup, Line 65 
Conflict of operand types: int is incompatible with uniqueidentifier

Error messages translated from French.

So it seems seems related to this KB article : http://support.microsoft.com/kb/2982019/en-us
It should had been corrected in Cumultative Update 1 but for my case it is not !

To resolve the problem, I tried :

- Uninstalling 2012 SP2 - Cumulative Update 1
Reboot
Start SQL Server (no SQL Agent)
- Uninistalling 2012 SP2
Reboot
Start SQL Server (no SQL Agent)
- Install 2012 SP2
Reboot
Start SQL Server (no SQL Agent)
- Install 2012 SP2 - Cumulative Update 1
Reboot
Start SQL Server (no SQL Agent)
Start SQL Agent

No error during uninstall and install

Everything seems to have worked fine but the problem is still there (SQL is in version 11.0.5532)

So I don't know what to do to correct that except going back to 2012 SP1 but I'm worrying if it's a good idea ?

Does anybody has an idea on how to correct this ?

Thanks for reading and in advance for your help.

Best regards,

Olivier

alwayson to take over replication in 2014

0
0

Hi all,

In our current setup we are using replication, Now they have proposed a plan to remove replication and use linked server instead after migration to alwayson(2014).
Current Setup.
Server 1 -> Publisher
server 2 -> subscriber/data-ware housing (used for BI jobs for ETL)
 
Proposed setup(2014 Instance - using always on)
Server 1-> primary
server 2 -> Secondary (BI jobs will access the secondary alwayson group through linked server,means the connections in SSIS packages will be changed to connect using linked server)

Will the above setup be fruitful when compared with replication? can someone advise the disadvantages in this setup.



Best Regards Moug

User can't see subscription under replication-local subscriptions in SSMS

0
0

The user is not SA, I have setup replication and I have SA rights & its working well (I can see it under SSMS, RM etc). So my question is does the user need any permissions to view the subscription in SSMS, the user can see the publication on the publisher server SSMS. Do I need to add him to the replmonitor role: http://technet.microsoft.com/en-us/library/ms147320(v=sql.105).aspx 

Thanks!


D

Relication

0
0

Hi,

We are using SQL Server Enterprise edition 2005 with 100 users access the server inNode A.

In Node B SQL Server Express edition 2005 using with 150 Users.

We replicating data from Node A to Node B, Node A will be Publisher and Node B will be subscriber.

Please Tell for this method we required any License (Product and Users CAL Users/device) 

Thanks

Manoharan K

Log Records Being Scanned

0
0

We make extensive use of replication on our system (which is Sql Server 2012 SP2 Enterprise).  We have a publisher, 3 subscribers and a distributor.  It is all transactional immediate push.

Lately our replication is running behind many mornings and here are the symptoms:

1.  I look on the distributor and the cpus are all pegged at 100%

2.  The log reader history shows that for hours it has been doing the following:

"Approximately 8000000 log records have been scanned in pass #4, 0 of which where marked for replication"

Basically, for hours the log reader has been scanning log records.  We have our publisher currently set to SIMPLE and the log file is usually "medium" in size - maybe 20-30G.  

To solve the problem, I usually do a restart of the services on the distributor and then that sends the cpu down to more normal levels.  It will do usually a little more scanning but not hours of it and then replication will almost instantly catch up.

Any idea what would cause this?  This is causing production issues almost every night and so any tips on how to debug/solve this would be much appreciated.


Cross-Site data center HA options (replication with DB mirroring?)

0
0

Hi friends,

I'm a software engineer recently asked to look into HA option available that will best fit some requirements at my company. I'm fairly new to the HA technologies in MS sql server, so please correct any misunderstandings I may have.

The requirement is that we want to setup a 2nd data center to host our web-based solution to provide a higher availability (SLA).

As the 2nd data center is geographically away, we would like to use transactional replication for cross-site database synchronization, where a site/db is active while another site/db is passive. We can switch over to the 2nd data center and make it active while making the 1st data center passive if needed. Hence, it seems like peer-to-peer transactional replication will fit this part of the bill well.

The problem is that we know with replication, there's possible data loss due to latency issues. My questions are:

(1) What would be the best HA option here? (replication? failover clustering?)

(2) Can we combine DB mirroring with replication? We want two-way replication, but DB mirroring does not support peer-to-peer replication. So can we still setup two-way replication usingbidirectional replication with DB mirroring?

Ideally, the setup will be like the following: Site 1 has DB1 and DB1_mirror. Site 2 has DB2 and DB2_mirror. Mirroring is set up between DB1 and DB1_mirror, as well as between DB2 and DB2_mirror. Replication is set up between DB1 and DB2. And if a failover occurs from DB1 to DB1_mirror, replication will still work to pass transaction data from DB1_mirror to DB2. And likewise in reverse.

Experts please advise~ thanks.

RMO MergePullSubscription.SynchronizationAgent cannot connect to PublisherFailoverPartner

0
0

Hi Brandon

I've  posted the problem below also on the forum http://www.sqlservercentral.com/Forums/Topic1601162-1549-1.aspx
but till now we had no respons, Is it possible to have a short look at our problem and provide us some advice how to proceed?

thanks in advance

for test purposes we used the example program from Brandon Williams on this url: http://code.msdn.microsoft.com/SQL-Server-Express-Merge-4e01e119
with as parameters for our testlab servers:
        // Define the server, subscription, publication, and database names.
        string subscriberName = "MORSWV447";
        string subscriptionDbName = "TicketOrdersSub";
        string publisherName = "MORSWV558";
        string publisherFailoverPartnerName = "MORSWV559";
        string publicationName = "TicketOrders";
        string publicationDbName = "TicketOrdersPub";
        //string distributorName = "MORSWV560";

to evaluate DRP scenarios we added the parameter agent.PublisherFailoverPartner = (Mirror server name)

If we do the failover while the program is running (but not replicating) it is working.   

Initializing
Connecting to Publisher 'MORSWV558'
Connecting to mirrored instance of Publisher 'MORSWV559'
Retrieving publication information
Retrieving subscription information.
Uploading data changes to the Publisher
No data needed to be merged.
Downloading data changes to the Subscriber
No data needed to be merged.
Merge completed with no data changes processed.
Done!


If we close and restart the program it can't find the failoverpartner anymore.      

Initializing
Connecting to Publisher 'MORSWV558'
The merge process could not connect to the Publisher 'MORSWV558:TicketOrdersPub'. Check to ensure that the server is running.
The merge process could not connect to the Publisher 'MORSWV558:TicketOrdersPub'. Check to ensure that the server is running.
The process could not access database 'TicketOrdersPub' on server 'MORSWV558'.
Cannot open database "TicketOrdersPub" requested by the login. The login failed.
Login failed for user 'xxx'.
Error: The subscription could not be synchronized. Verify that the subscription has been defined correctly.

InnerException = {"The merge process could not connect to the Publisher '(Primary Principal)PublicationDBName)'. Check to ensure that the server is running."}

What did we do wrong here? or is this a bug in the RMO MergePullSubscription.SynchronizationAgent?

We used for all server Microsoft SQL Server standard Edition 2008 R2 SP2 CU3 on Windows Server 2008 R2 Sp2 - 64 Bit.
By using the cmd line executable replmerge.exe we can use this parameter as expected.

thanks in advance for sorting this out.
Paul


Log Reader Agent Profile changes not working...

0
0

Morning all,

I have an issue at the moment which I am trying to troubleshoot with Transactional Replication. I have stopped the Log Reader Agent and created a new Agent profile to use differing Read Batch Size and Polling Interval values. No matter what I change these settings to (lower or higher), it still polls every 5 seconds (default) and processes 500 at a time (default).

I have taken the environment back to scratch, stopping all Replicated Log Reader Agents, making the changes, selecting the new profile and then restarting the agent. However it continually uses the default settings. When you go back into the Log Reader Agent properties, the new profile is ticked and the settings within the profile changed, but it isn't using them.

Having exhausted online resources, I have come cap in hand to see if anyone else has had the same issue and if so, how you resolved it.

Cheers

SQL 2012 Peer Replication and AlwaysOn

0
0

Hi All,

I'm doing some research on SQL 2012, which we are planning to deploy next year, and wanted to be able to combine peer-to-peer replication with AlwaysOn technologies.  We currently have 2 data centres.  In the first one, we have our primary databases, which are log-shipped to the second centre for DR purposes.  The second centre currently read/writes directly to the first center, and so is subject to network latency issues.  We also transactionally read-only replicate our primary databases to a number of other servers for load balancing of other read-only purposes.

What I'd like to do, is to create 2 AlwaysOn availability groups, one at each data centre.  Each group would consist of a primary and active secondary node.  I would like to set-up peer replication between the 2 AGs, using another server as the distributor between them.  That way I can achieve both my HA and load-balancing objectives.  Each primary would be used for read/writes by the users at each data centre, with P2P handling the synchronization between them.  Each active secondary would be used as both automatic failover points and for load-balancing of our read-only loads.

Can anyone tell me if they have ever done this, or if it is supported?  From what I'm reading, I can't see why not as AlwaysOn does support replication.  What about identity range management issues?  I'm assuming I'd have to coordinate the range management between P2P and AlwaysOn.

Any information, links, or recommended books on the subject would be most appreciated.

Regards,

Diane Sithoo


Diane

SQL Server 2014 Replication Limitation

0
0

I need to purchase SQLSvrStdCore 2014 SNGL OLP 2Lic NL CoreLic ,could you please send me the details of SQL Server replication limitation(at one time can replicate maximum Database quantity) with same version.I'm really appreciate your consideration and I look forward to hearing from you.

snapshot excludes foreign key

0
0
We are using merge replication with pull subscriptions on SQL Express 2005 and a publisher on SQL 2012.  We recently upgraded to a merge join filter system. The merge join filters use a column that is also part of a compound foreign key. On the publisher this foreign key employs cascade update/delete with 'not for replication'. However, the snapshot does not create that foreign key. The same table includes other foreign keys which are propagated to the subscribers. Is there an issue with using a single column of a compound foreign key as a merge join filter? Is there an issue with using the cascade option with a merge join filter? We are baffled and have found little, if any, related information on the web or in books online. Perhaps we're searching in the wrong area? Does anyone have any insight into why the FK is not being created as part of the snapshot? Thanks!

SQL 2014 Replication Assemblies version mismatch - Microsoft.SQLServer.RMO and .Replication are .Net 4, SMO, Connection are .Net 2

0
0

I have C# project that I use to create a pull merge replication subscription. This project generates a DLL that has COM interop support. Our main application is not written in a .Net language.  Having the COM support on my subscription assembly allows me to call into the .Net world from our main program.

I have been using this methodology successfully since SQL Server 2005 through 2012.

However, in SQL 2014 some of the assemblies are now version .Net 4 but others are still .Net 2.

Specifically, my project framework target is .Net 4 and it references:

  • Microsoft.SqlServer.ConnectionInfo - .Net 2.x
  • Microsoft.SqlServer.Management.Sdk.Sfc - .Net 2.x
  • Microsoft.SqlServer.Replication - .Net 4
  • Microsoft.SqlServer.Rmo - .Net 4
  • Microsoft.SqlServer.Smo - .Net 2

When I call into my assembly I'm receiving this error:

Mixed mode assembly is built against version 'v2.0.50727' of the runtime and cannot be loaded in the 4.0 runtime without additional configuration information.

I found the following link which discuss this error:

http://social.msdn.microsoft.com/Forums/vstudio/en-US/1f60a379-e2e3-46b9-b343-0235486fc746/mixed-mode-assembly-is-built-against-version-v2050727-of-the-runtime-and-cannot-be-loaded-in-the?forum=clr

The link in that forum to stack overflow talks about adding

<startupuseLegacyV2RuntimeActivationPolicy="true"><supportedRuntimeversion="v4.0"/></startup>

to my application .config file, but my assembly does not have a app.config file.

If anyone can point me in the right direction I would appreciate it.

This link mentions an AdventureWorks example for 2014 replication but I cannot find the source. That might be enough to get me going in the right direction.

http://technet.microsoft.com/en-us/library/ms146892.aspx

Thanks, Rick

Viewing all 4054 articles
Browse latest View live




Latest Images