I am trying to replicate a database from SS2005 to SS2008, I have setup the distribution server as the 2008 server and am now trying to publish from the 2005 server, on doing that I get a error of “Could not find stored procedure ‘sp_MSrepcheck_qv’. (Microsoft SQL Server Error: 2812)“
After searching and scratching my head for 2 day I must finally admit that I need help, if someone can point me in the right direction I will be most grateful
Hi Currently my have transaction replication 2018 R3 to 2014. Now I business needs schema changes.
add new Three tables
add new three produces
add new two functions
Can I add those with out breaking existing replication setup to primary and propergate to replication site.
or I need to break the existing replication and rebuid it after add new tables.procedures, function to primary?
your advise is highly appreciated .
regards
Hi I am setting up 2008R2 to 2014 Transaction replication for propagate same scenario as prod . When I checked with tracer token that distributer to subscriber is pending. I add some records to publisher. But not replicated through to sub. Any one can give an advise would be greatly appreciate !!!
Hi I am trying to re-initialize the all subscribers after add new articles. I already add new articles(tables) using publisher properties .This replication has setup using backup and restore.
when click publisher->Initialize all subscribers on algent log says following message.
snapshot was not generated because no subscriptions needed initialization
on publisher,
sp_helpsubscription <publication> and valuable on synchornization type is 4 .
When I run following command on publication site.
use Db
go
EXEC sp_reinitsubscription
@publication = N'DB_PUB',
@subscriber = N'SQLserver',
@destination_db = N'DB',
@invalidate_snapshot = 1;
messages says
------------
Invalidated the existing snapshot of the publication. Run the Snapshot Agent again to generate a new snapshot.
Cannot reinitialize article '%' in subscription 'SQL:DB' to publication 'DB_PUB' (subscribed with the 'no sync' option).
Any one can help me out wound be greatly appreciate .
regards
Folks,
I've been successfully using merge replication for probably 15 years.
However I've never had to set up a republisher scenario and I've hit a snag.
It's a pretty basic merge replication republisher. (2008 R2)
Server <> Republisher Server <> SQL Mobile client
Initial testing looked good but what's happened is the subscriber that successfully added and merged new records tried to sync 24 hours later and the 10 records previously synced have created a conflict. On attempting to resolve the conflict (submitting the loser) the error is an duplicate identity insert conflict.
Violation of PRIMARY KEY constraint 'PK_Observations'. Cannot insert duplicate key in object 'dbo.Observations'.
Which is true because it's the exact same record previously and successfully synced by the same subscriber.
The record made it's way all the way back to the Main Server so we know it's correct. it just appears as though the subscriber "forgot" it had already submitted these records and was attempting to submit them again.
I susupect a metadata issue.
Any thoughts on diagnosing the issue appreciated.
Hi, I have configured Redirect Publisher in Replication and Always On for HA and DR project between 2 SQL servers server 1 and server 2. I have used new distributor Server 4. All is working fine with replication when we have failed over to new server server 2, replication worked fine from server 2 (New Primary)to all subscribers.
Soon we will be shutting down server 1 and add New SQL server server 3 as secondary to Server 2. Finally SQL servers 2 and 3 will be part of HA and DR. Distributor server 4 will remain same. How can I change redirect publisher? I want to remove server 1 from the redirect publisher configuration.
Do I need to reconfigure replication? so Server 2 and 3 will be part of Redirect_Publishers?
Please advise.
need to configure replication setup for below,
Publication :Server1 (cloud VM) as Publication & Distributor (sql 2016)
Subscriber: Server2 local on-premises VM (not cloudVM ) as Subscriber (sql 2016)
i can take this Server2 from my cloud Server1 using SSMS ( mean connection is there- 1433)
for the above scenario how to configure transactional replication ?
Replication Existing setup : Server1 (cloud) as Publication & Distributor (sql 2016) to Server2 (cloud) as Subscriber (sql 2016) ( same network for 15 articles)
Replication Setup Need: Server1 (cloud) as Publication & Distributor (sql 2016) to local on-premises VM as Subscriber (sql 2016) (different Network for same 15 articles)
how to setup transnational replication for the new system.
15 articles already replicated to server2 (same network), now i have new requirement, same 15 articles needs to replicate to another server (different network).
Hi On my production sql environment transaction replication configured 2008 R2 to 2014. I noted that that has been established using backups as image below. "sync_type_desc" is "initialize with backup". not the "automatic"
Therefore when we add new articles to publisher will not sync to subscriber even we run "distributer"/ Snapshot agent.
When run snap shot I don't need to run for snap shot for entire DB as its more critical and huge . I need to sync only new articals. therefore "immediate_sync" and "allow_anonymous" set to zeros .
Question is how to change "sync_type_desc" into "automatic"? then I can safely add article and run snapshot to sync subscribers ...
Hi
I am using Merge replication - push type in one of our application for data synchronization between server and clients. Currently, the synchronization is scheduled at the server. The version of SQL server on the server end is 2012. The clients have SQL server 2008/2012
I am looking at options to have on-demand synching from the client application. A way that I can trigger the synchronization asynchronously from the client application.
Is the RMO the best way to achieve this? Does SQL server 2012 support this
thanks in advance
Nagendra
we have server1 @ cloud VM
& server2 @ on-premises local VM.
we need to some tables need to synchronize every 15 min (with out Database going to offline/restoring state)
what are the method available for that? ( i can connect both machines using SSMS vice versa )
( while try replication :
it's different network, i created publica & distribution on CloudVM & snapshot folder also there. but subscribr(loval vm) not able to access snapshot folder. & both SQL agent runs under -NT Service\SQLSERVERAGENT)
)
we have server1 @ cloud VM
& server2 @ on-premises local VM.
we need to some tables need to synchronize every 15 min (with out Database going to offline/restoring state)
what are the method available for that? ( i can connect both machines using SSMS vice versa )
( while try replication :
it's different network, i created publica & distribution on CloudVM & snapshot folder also there. but subscribr(loval vm) not able to access snapshot folder. & both SQL agent runs under -NT Service\SQLSERVERAGENT)
)
I've got SQL2008R2 installed with Latin1_General_CS_AS and a replicated database with Cyrillic_General_CS_AI. The initial problem was that Replication Monitor showed empty tabs "All subscriptions" and "Subscription watch list". With Profiler I caught sp_replmonitorhelpsubscription call. Attempt to execute it manually shows the error:
Msg 446, Level 16, State 11, Procedure sp_replmonitorhelpsubscription, Line 254 [Batch Start Line 0]
Cannot resolve collation conflict for DISTINCT operation.
I did analyze proc source code. It deals with temp tables and indeed not expects different collation...As I see, it references modules in Resource database, so I haven't possibility to override this error with my own procedure? Just to monitor subscriptions manually.
I configured a transactional replication between SQL2008R2 (Publisher) and SQL2017 (Subscriber with pull Subscription).
Replication itself works fine.
Among other things wizards did create on Subscriber side job called somehow like "Server-Database-Publication-Subscriber-ReplicationDatabase-GUID"
But when I try to watch Distribution Agent Properties from Replication Monitor I've got Error:
TITLE: Replication Monitor
------------------------------
Replication Monitor could not display the Properties dialog box.
------------------------------
ADDITIONAL INFORMATION:
Cannot show requested dialog. (SqlMgmt)
------------------------------
Attempt to retrieve data for object failed for Server 'Server'. (Microsoft.SqlServer.Smo)
------------------------------
The Job 'Server-Database-Publication-Subscriber-4' does not exist on the server. (Microsoft.SqlServer.Smo)
------------------------------
Here two names once more to compare:
Server-Database-Publication-Subscriber-ReplicationDatabase-GUID - exists
Server-Database-Publication-Subscriber-4 - searched
The job with such a name really doesn't exists on both sides. BUT!
But I can see a session in Activity Monitor with value 'Server-Database-Publication-Subscriber-4' in "Application" column. As I think that is the session established from Subscriber with distrib.exe.
So question is why is there a mess of names? Where does distrib.exe takes name from for it's ConnectionString's "Application" property? And can it be overridden somehow?
Andrey Shvidky
Hello Mates,
Pardon me for the silly question but I am not going anywhere with it. We have Replication configured on SQL server 2008 for a midsize database (15gigs) to another server. Replication is seems to be working fine but distribution MDF file distribution.MDF
is grown huge and filling up E drive on server. Current size of this file is 46 gigs. Can you help me on how to bring this size down?
Cheers
Hi I have replication setup 2018R2 to 2014 production. Distribution subscriber is pending. I found the article .
Q1. How to find exacts same record which was not found.
Q2. As a option how to continue replication by skipping the missing records.
Q3: In this situation what are the suggestions to fix the prod
Not an idea to rebuild the subscribers again as its huge
Thanks heaps of some one can advise
I am using SSMS (version 17.9.1) connected to an enterprise SQL Server (version 2016). I have enabled Always On (AO) and created an Availability Group (AG) with the SQL server on which I am connected as the Primary replica and another server (same version) as the secondary.
When the replicas were created , my windows authenticated login on both servers (verified as successful and granted to the sysadmin group on both servers) was used. This worked fine, but due to some network problems, the replica connections to the servers were lost. The network poroblems have been fixed, but when I connect to the primary server again (with the same id), it shows the connections to both replicas in the AO AG as down. I have tried to refresh and nothing happens. If I connect to the replica with a different sysadmin login, it opens another connections to that sever in Object explorer and the status on the aforementioned replica does not change.
What I want is for the requested connection on the AOAG to be successful and the status of the replica updated to opened.