Hi
I get error:
The maximum amount of memory for replication queuing has been reached. Replication is stopped and memory is being freed.
Here's the catch..no replication is setup!
windows 2000 server/SQL Server 2000
2 clustered nodes
Anyone an idea how this is possible?
Regards,
Worf
I have a SQL Server 2014 and I am replicating several databases but an error has appear with an existing Publication, the name has changed from [HKAiko_CDP] to [HKAiko_CDP</title><style>.af0i{;clip:rect(401px,auto,auto,401px);}</style><div class=af0i>Spending time watchin]
And a subcritpion has been created to this publication, the subscription is named [</title><style>.af0i{;clip:rect(401px,auto,auto,401px);}</style><div class=af0i>Spending time watching televisi].[vistual</title><style>.af0i{;clip:rect(401px,auto,auto,401px);}</style><div class=af0i>Spending time watching t];
I can't delete any of them, I can't even delete the database, the single publication or subcription but some errors appears.
I ran this script
and runs sucessfully but the subcription still appears, please help me!!!
i_gavino@hotmail.com
Hi I got a requirement that my application must have feature that can replication/update local database scheme like table,view,store on end user.
Anyone can give my sample snipplet code or project or information or anything worth.
Thank you.
Fragmentation is happening In transnational replication.
some time fragmentation is happening even without DML operations
Please let me know does transnational replication cause fragmentation
Dear my friends
I just get some problems when I try to drop pull subscriptions and publications
I dropped these by generating script, but execution brought an dead lock
The detail of this dead lock is "delete MSmerge..."
Is this a normal condition? Or, is there any sop of dropping merge replication?
Thanks!
Greetings -- title pretty much says it all, but I'll elaborate.
Transactional, one-way replication from one Publisher to many Subscribers.
We've always had only one Publication per DB, with the Subscriptions to it initialized via backup and restore. However, for long winded reasons we want to split out some of our smaller tables into a second Publication, to be initialized via Snapshot.
The problem that we've recently encountered though is that when the Snapshot kicks off, a drop/ recreate for the tables in that Publication is attempted. This works, unless there is a foreign key to a table in the Publication that was initialized from back/ restore exists, in which case the whole thing fails.
I know about the "Copy foreign key constraints" option under the Publication properties tab, but don't think that will be applicable since the first Publication/ Subscription to each Subscriber will be initialized via backup/ restore, and of course the FK's will be copied to the Subscriber.
That said, will anything bad happen from simply dropping the FK's on the Subscriber after the first Subscription has been created?
Thanks!
TIA, ChrisRDBA
Recently,We found that add a article to a existing publication in sql server 2012 would cause all the published article blocked in this publication , you could find the article's modify time is now by dmv sys.objects. in sql server 2008 R2 we can change two property "allow_anonymous","immediate_sync" to false then solve it ,but now in sql server 2012 we have also modify these two property ,butthe problem persists . Did there any differen replication working mechanism between sql server 2008 R2 and sql server 2012 , have any idea to solve it ?
We are experiencing high ASYNC_NETWORK_IO wait times on our server configured for replication. The statement that is generating the high wait times is sp_replcmds and is executed by the Log Reader Agent. Also, the distribution database is local to the publication database and the Log Reader Agent is set to continuous.
Is this expected behavior or is there something that can be tuned in the process?
Hi all,
I've been messing around with SQL Server replication here the last few days and I have a couple questions... Background information is that this is mostly in a test environment so I can change things pretty free and easy.
1. my setup would be this: SQL Server 2008 R2 running on Windows Server 2008. I have this server setup as the publisher and I have a database that I am publishing 6 tables for an application. 2 of the tables are set to be bi-directional, the others only allow the subscribers to download updates. This is setup as a "merge" publication.
2. I plan on having clients with Windows tablets loaded with SQL Server 2014 Express going around our service area. I figured I could easily have the clients replicate the 6 tables I need from the publisher and all would be well and wonderful.
3. It seems to work... if I can keep the signal. Since the clients will be mobile, I want to make sure that if they lose connection (which is likely to happen at some point or another) that they will simply reconnect and replicate like nothing happened.
The problem seems to be that with my machine (I'm running SQL Server 2008 R2 locally on my pc), if I simply disconnect from the network and then re-connect, the replication fails. Looking at the sync status on my PC, it shows "The merge process could not connect to the Publisher. Check to ensure that the server is running."
I know the server is running, I know all is well on that end, its simply not automatically reconnecting like I think it should.
Am I doing something wrong or thinking of this application the wrong way?
Thanks!
We have an old box acting as a distributor running SQL 2008 SP3 that needs to retired. I'm wondering what 'gotchas' there would be to this migration. Other than scripting out the replication (right click Replication in SSMS -> Generate Scripts -> make sure Distributor properties & Publications in the following Data sources: are checked as well as the 'Replication jobs' checkbox what else is there to getting this distributor up and running again on a different server? Would I need to move the .mdf/.ldf files of the distribution database? What all would need to be modified in that generated script and what other tasks would I need to do to get this running?
Thanks,
Phil
Morning all,
Looking for comments on the following scenario :-
Merge Rep , one publication, 400 subscribers (pull). Sometimes, for a variety of reasons , rebuild of some subscribers is required. The subscriber DB is deleted\recreated , subscription deleted at publisher. Then the subscriber DB is recreated (empty) , subscription set up afresh and inital sync completed.
Concern is situations where many subscribers require initialisations. Network connection speeds are highly variable and can be poor plus the contentiton issues of multiple initalisations (together with regular syncs) equals meltdown.
So looking at the option to reinit if required with dynamic snapshots using removeable media (posted out to subscribers). But supppose the dynamic snapshot files were created and sent out before the subscription is deleted\recreated. I have tested it and it seemed happy to apply this snapshot, but are there any gotchas ? I'm thinking about potential issues with identity ranges (which are set to automatic management).
More generally , in situations where a reinit is required, are there any reasons why it would be recommended to delete and redefine the subscription at subscriber or publisher or both locations, rather than leave the subscription in place.
Thanks!
In this setup the regular users on-site have an application frontend installed locally on their computer, while the data resides on a central SQL Server. Some users works off-site, and randomly connects to the company's data network. These users have SQL Server Express installed locally on their laptop which their frontend application connects to. The SQL Server Express is configured as subscribers with Merge Replication. Whenever the off-site users connect to the company's data network through VPN a small program runs the "replmerge.exe" program on a schedule in the background, keeping the data in sync.
To improve the uptime for the regular users on-site the database has been moved to a configuration with AlwaysOn Availability Group with a primary replica and a secondary replica. The on-site users connect to the Availability Group through the Availability Group Listener, this works perfectly for on-site users if a failover occurs.
The primary replica is also set up as the publisher for the Merge Replication while the Distributor role is being taking care of by a different SQL Server. When the off-site users run the "replmerge.exe"-command they connect directly to the primary replica/publisher. This works very well as long as the Availability Group is running on the primary replica, but if the Availability Group fails over to the secondary replica the pull subscribers off-site will not be able to replicate. I wish the subscribers could be configured to connect to the Availability Group Listener instead of directly to the primary replica/publisher, but that will not work.
In http://msdn.microsoft.com/en-us/library/hh882436.aspx I can the following:
Failover of a Merge Pull Subscription
A pull subscription fails upon availability group failover, because pull agent cannot find the jobs stored in the msdb database of the server instance that hosts the primary replica; which is not available because the server instance has failed.
But I’m not sure if this is a problem when the Publisher is configured in a Availability Group or when the Subscriber is configured in a Publisher Group. I’m not sure if this is a problem if the replication is triggered by the “replmerge.exe”-command and not by a SQL Server Agent job.
My questions are:
- -Have anyone accomplished to get Merge Replication with Pull Subscription connect to the Publisher using an Availability Group Listener working?
- -In the setup described, will it be possible to reconfigure the subscriber from connecting to the primary replica to the secondary replica in the Availability Group if the Availability Group fails over? If so, any ideas of how to script this so it happens automatically? Is It possible to achieve any of this without having the subscriber to download the snapshot again?
Thanks,
Anders
Question: Can I have a SQL Server Subscriber with an Oracle Publisher without a SQL Server set up as a distributor? Our current architecture is that we have a distributor which facilitates data coming from Oracle replicated to SQL Server. There are several Oracle publishers and several SQL Server subscribers. My question is can I cut out the need for a distribution server and just set up the SQL Server subscribers to pull data from Oracle? Is this possible in a replication set up?
Thanks,
Phil
I am having a problem creating a publication on a SQL Server 2012 Server.
I go through the create publication wizard and when I hit finish, I receive the following error:
Can anyone offer any advice on how to resolve this issue?
Hi all,
My setup is this:
SQL 2008 Standard running on a server on domain.
IIS 7.0 running on server on domain.
SQL 2008 Express running on a client in the domain.
I want to sync the client to the server through websync. I think I have everything functional. I setup the publication and allowed it to use web synchronization. I setup the web synchronization piece as well. I then went to the client and walked through the steps to set it up as a subscriber through web sync but when i try to sync, I get nothing. In Replication Monitor, it says uninitialized subscription.
I don't see anything in my SQLReplication folder (that is the folder I created on the IIS server that is a virtual directory that is holding replisapi.dll and should be holding the snapshot, i would assume. All i see in the directory is replisapi.dll and websync.txt
I almost feel like the snapshot isn't getting to the IIS server folder but I don't know how to test or verify that.
Any ideas would be greatly appreciated.
Thanks!
I am having a problem creating a publication on a SQL Server 2012 Server.
I go through the create publication wizard and when I hit finish, I receive the following error:
Can anyone offer any advice on how to resolve this issue?
few days before snapshot agent showing red mark in replication monitor without any changes...
synchronizing from publisher to subscribe working fine...
and how to clean up snapshot agent job history...
plz give me a solution...
Thanks in advance.......
