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

SQL Server 2019 snapshot agent error

$
0
0

Hello,

I was trying to configure an SQL Server 2019 transactional replication, but the snapshot agent returns the following error:

Error messages:
Message: An unspecified error had occurred in the native SQL Server connection component.
Stack:    at Microsoft.SqlServer.Replication.Snapshot.SqlServer.NativeBcpOutProvider.ThrowNativeBcpOutException(CConnection* pNativeConnectionWrapper)
   at Microsoft.SqlServer.Replication.Snapshot.SqlServer.NativeBcpOutProvider.ThrowConnectionFailureException(CConnection* pNativeConnectionWrapper)
   at Microsoft.SqlServer.Replication.Snapshot.SqlServer.NativeBcpOutProvider.InitializeNativeBcpOutProvider(LogMessageCallback logMessageCallback, String strName, String strApplication, String strHost, String strServer, String strNetwork, Int32 encryptionLevel, String strDatabase, SecurityMode securityMode, String strLogin, SecureString strPassword, Int32 bcpBatchSize, Int32 loginTimeout, Int32 queryTimeout, Int32 packetSize, DeadlockPriority deadlockPriority, String strRowDelimiter, String strFieldDelimiter, Byte syncMethod, Boolean forceOdbcBcp, Boolean forceOleDbBcp, Boolean enableMultipleActiveResultSets, Boolean useReadPastHint, Boolean usePageLockHint, Boolean securePassword)
   at Microsoft.SqlServer.Replication.Snapshot.TransSnapshotProvider.InstantiateBcpOutProviderWorker(String strBcpConnectionName)
   at Microsoft.SqlServer.Replication.Snapshot.SqlServerSnapshotProvider.InstantiateBcpOutProvider(String strBcpConnectionName)
   at Microsoft.SqlServer.Replication.Snapshot.SqlServer.BcpOutThreadProvider.Initialize()
   at Microsoft.SqlServer.Replication.WorkerThread.NonExceptionBasedAgentThreadProc()
   at Microsoft.SqlServer.Replication.AgentCore.BaseAgentThread.AgentThreadProcWrapper() (Source: MSSQL_REPL, Error number: MSSQL_REPL55012)
Get help: http://help/MSSQL_REPL55012

Any idea why?

Best regards,

José Cruz


Undistribute commands, distributor to subscriber history query timeout

$
0
0
greetings, have set up a new subscriber for an existing publication. the publisher is a 2008 r2 instance, with 2 existing 2008 r2 and now 1 an additional subscriber which is 2014, all on different servers on the same network. I reinitialized the new subscriptions and ran the snapshot jobs. I had truncated 1 of the tables on the subscriber so I could verify it was actually working as it should eventually have data in the table after the snapshots complete. I have seen some latency so I gave the processes time to complete/push data from distributor to subscribers, but I noticed that I was not getting data in the table i was monitoring. I saw in the distributor to subscriber history there was a query timeout error message and the message the process is running and waiting for a response from the server. I had 582 undistributed commands, and that count was not moving. After an hour of waiting, I restarted the sql service on the distributor, it the undistributed command count did not budge. I then restarted the sql service on the subscriber, and shortly after that the undistributed commands started getting applied. It seems now to have worked but i would like another opinion of what was going on (just latency) or was something hung up and I needed to restart those services? would have liked to been able to get past this without a service restart.  thanks

SQL Server 2012 Standard Clustering - multiple instances

$
0
0

Hi,

We have an existing 2-node Windows 2012 WSFC running SQL. The current instance is a default MSSQLSERVER one. The WSFC has 5 volumes:

Quorum (Witness Disk)
SQL Backups
SQL DB files
SQL log files
TempDB

If we installed another clustered SQL instance to this WSFC, I'm assuming we'll need another 4 volumes (as above excluding the Quorum as that is for the WSFC itself), because multiple clustered SQL instances cannot share the same disks like you can with standalone multiple SQL instances?

Thanks


Clone a Table

$
0
0

Hi There,

I am trying to clone Table A, which warehouses every evening from a different Server.

I cant do right click and Script table as> Create to as that will give me nulls.

I cant do Select * INTO FROM as that would give me a static table 

But instead i want a duplicate table that is as updated from Table A.

Thanks!


Clustering, Shared Storage and Multiple SQL Instances

$
0
0

Hi,

My previous, similar question covered SQL 2012 and WSFC: https://social.technet.microsoft.com/Forums/en-US/4f42e157-6bd1-47b7-b17d-9a8973c5050d/sql-server-2012-standard-clustering-multiple-instances?forum=sqlreplication

I've been doing some reading and understand that SQL 2014 upwards supports Cluster Shared Volumes, which I'm familiar with from my Hyper-V deployments. Does CSV support mean that you can have now have SQL clustering (whether WSFC or "AlwaysOn AGs" and multiple SQL instances connected to the same disks (LUNs)?

My experience from CSV in Hyper-V is that:

all cluster nodes have access to the disks
if 10 VMs are on the same CSV, you can move individual VMs to specific nodes

So if I apply that same logic to SQL with CSV:

2-node "traditional" WSFC SQL cluster, all nodes have access to all disks
multiple instances of SQL sharing those disks (for simplicity, lets say all SQL data is on disk drive D:)
--Instance 1: D:\SQL1\data.mdf, ldf etc.
--Instance 2: D:\SQL2\data.mdf, ldf etc.
moving Instance 1 to cluster node 2 leaves Instance 2 on cluster node 1, but is still able to access D:\SQL2 because of CSV

Without CSV, moving Instance 1 to cluster node 2 would take all resources with it, meaning Instance 2 on cluster node 1 no longer has access to its data

How does this work with AlwaysON Availability Groups? Are they supported with CSVs?

Thanks

Dropping and Re-Creating a Replicated Table

$
0
0

So we have to drop a current Table and then Re-CREATE it with an [ID] IDENTITY data column.

We have a script that will back-up the current table's data contents to a ##Global Temporary Table...wanting to make it global just in case.

As far as the replication piece is concerned, is it as simple as...

  1. <Right-Click> on Local Publication ==> Generate Scripts Script the commands Todrop or disable the components
  2. Run the T-SQL Script that will create the ##Global Temp Table, back-up current data contents, DROP the current Table, CREATE the new Table with an [ID] IDENTITY Data Column, then INSERT-SELECT To New Table FROM ##Global Temporary Table
  3. <Right-Click> on Local Publication ==> Generate Scripts Script the commands Tocreate or enable the components

Just want to make sure we get this right because we certainly don't want to break and corrupt data replication once we Re-CREATE the Table

Thanks for your review and hopeful for a solid response.

Issue with Peer-To-Peer replication on 2017 - conflicts are not solved automatically

$
0
0

I have an issue with Peer-to-Peer replication configured on 2 MSSQL 2017 enterprise servers.

Everything is working fine where the data is changed only on one of the server. However when I start using the SVR2 and putting some data there I'm ending up with issue with conflict. I have the PEERID configured and from my understanding the Peer-To-Peer replication by default is solving the conflicts automatically. Or I'm missing something?

Here is the error I got:

2020-02-01 19:48:15.676 
42000 A conflict of type 'Update-Update' was detected at peer 1 between peer 100 (incoming), transaction id 0x000000001e78c492  and peer 1 (on disk), transaction id 0x000000001e147f74 for Table '[dbo].[user]' with Primary Key(s): [UserID] = 4684,  Current Version '0x01000000747F141E00000000', Pre-Version '0x6400000060C4781E00000000' and Post-Version '0x6400000092C4781E00000000' 22815
2020-02-01 19:48:15.676 
42000 A conflict of type 'Update-Update' was detected at peer 1 between peer 100 (incoming), transaction id 0x000000001e78c494  and peer 1 (on disk), transaction id 0x000000001e147f4f for Table '[dbo].[user]' with Primary Key(s): [UserID] = 3476,  Current Version '0x010000004F7F141E00000000', Pre-Version '0x640000005FC4781E00000000' and Post-Version '0x6400000094C4781E00000000' 22815
2020-02-01 19:48:16.520 Disconnecting from Subscriber 'SVR2'
2020-02-01 19:48:16.520 Connecting to Subscriber 'SVR2'
2020-02-01 19:48:18.020 Error executing a batch of commands. Retrying individual commands.
2020-02-01 19:48:19.129 Agent message code 22815. A conflict of type 'Update-Update' was detected at peer 1 between peer 100 (incoming), transaction id 0x000000001e78c482  and peer 1 (on disk), transaction id 0x000000001e147dae for Table '[dbo].[user]' with Primary Key(s): [UserID] = 4265,  Current Version '0x01000000AE7D141E00000000', Pre-Version '0x6400000047C4781E00000000' and Post-Version '0x6400000082C4781E00000000'
Here are the settings of publication:
https://imgur.com/JfC91LJ

Can I have an AWS RDS as a subscriber ?

$
0
0

Hi,

We have a transactional replication that have an AG as a publisher and a SQL Azure as a subscriber.

I would like to add another subscriber to be an AWS RDS.

Is that possible ? Has someone done this and how ?

Thank you for your help,

S.


Merge Replication download delete rows to subscriber

$
0
0

I have a single article or table that once the subscriber adds data to it, it will sync to the publisher and remain in the publisher but then the publisher downloads delete records to remove if from the subscriber.  This article, as far as I can tell, matches the same properties of other articles that do not do this.  There are no conflict for this publication.  I cannot figure out why, just this one case, would rows be deleted at the subscriber after a successful sync?  Looking for any help please.

On subscriber I cleared - select *  from MSmerge_tombstone

<u1:p></u1:p>

 I entered form data int the subscriber and verified it was present in the table (15 records) and then sync’d and data was gone from table.  I then ran ran select *  from MSmerge_tombstone again and matched 17 records deleted 15 form_data and 2 TEGGObject.

<u1:p></u1:p>

 According to the link at the top Type 5 = Row no longer belongs to the filtered partition. - what does this mean?

<u1:p></u1:p>


<u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p><u1:p></u1:p>

rowguid

tablenick

type

lineage

generation

logical_record_parent_rowguid

logical_record_lineage

61815DAF-970B-401E-B9EA-1A216342785B

19193017

5

0x51C769C7E9C901000000FE5ECD57415401000000FF

2070

NULL

NULL

B67B8473-1614-480C-B5D6-51AF325E8E88

19193017

5

0x51C769C7E9C901000000FE5ECD57415401000000FF

2070

NULL

NULL

FCC81CC1-C449-EA11-9BEB-3800256D3F07

9193053

5

0x51C769C7E9C901000000FE5ECD57415401000000FF

2069

NULL

NULL

FDC81CC1-C449-EA11-9BEB-3800256D3F07

9193053

5

0x51C769C7E9C901000000FE5ECD57415401000000FF

2069

NULL

NULL

FEC81CC1-C449-EA11-9BEB-3800256D3F07

9193053

5

0x51C769C7E9C901000000FE5ECD57415401000000FF

2069

NULL

NULL

FFC81CC1-C449-EA11-9BEB-3800256D3F07

9193053

5

0x51C769C7E9C901000000FE5ECD57415401000000FF

2069

NULL

NULL

00C91CC1-C449-EA11-9BEB-3800256D3F07

9193053

5

0x51C769C7E9C901000000FE5ECD57415401000000FF

2069

NULL

NULL

01C91CC1-C449-EA11-9BEB-3800256D3F07

9193053

5

0x51C769C7E9C901000000FE5ECD57415401000000FF

2069

NULL

NULL

02C91CC1-C449-EA11-9BEB-3800256D3F07

9193053

5

0x51C769C7E9C901000000FE5ECD57415401000000FF

2069

NULL

NULL

03C91CC1-C449-EA11-9BEB-3800256D3F07

9193053

5

0x51C769C7E9C901000000FE5ECD57415401000000FF

2069

NULL

NULL

04C91CC1-C449-EA11-9BEB-3800256D3F07

9193053

5

0x51C769C7E9C901000000FE5ECD57415401000000FF

2069

NULL

NULL

05C91CC1-C449-EA11-9BEB-3800256D3F07

9193053

5

0x51C769C7E9C901000000FE5ECD57415401000000FF

2069

NULL

NULL

06C91CC1-C449-EA11-9BEB-3800256D3F07

9193053

5

0x51C769C7E9C901000000FE5ECD57415401000000FF

2069

NULL

NULL

07C91CC1-C449-EA11-9BEB-3800256D3F07

9193053

5

0x51C769C7E9C901000000FE5ECD57415401000000FF

2069

NULL

NULL

08C91CC1-C449-EA11-9BEB-3800256D3F07

9193053

5

0x51C769C7E9C901000000FE5ECD57415401000000FF

2069

NULL

NULL

09C91CC1-C449-EA11-9BEB-3800256D3F07

9193053

5

0x51C769C7E9C901000000FE5ECD57415401000000FF

2069

NULL

NULL

0AC91CC1-C449-EA11-9BEB-3800256D3F07

9193053

5

0x51C769C7E9C901000000FE5ECD57415401000000FF

2069

NULL

NULL

Here is what the sync log looks like

2020-02-06 16:27:30.682 OLE DB Subscriber 'DESKTOP-H42INT9\SQLEXPRESS': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}<u1:p></u1:p>

2020-02-06 16:27:30.682 [7%] [507 sec remaining] Percent Complete: 7<u1:p></u1:p>

2020-02-06 16:27:30.682 Downloaded 15 change(s) in 'Form_Data' (15 deletes): 15 total<u1:p></u1:p>

2020-02-06 16:27:30.697 OLE DB Subscriber 'DESKTOP-H42INT9\SQLEXPRESS': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}<u1:p></u1:p>

2020-02-06 16:27:30.697 [7%] [507 sec remaining] Percent Complete: 7<u1:p></u1:p>

2020-02-06 16:27:30.697 Web synchronization progress: 99% complete.<u1:p></u1:p>

Article Download Statistics:<u1:p></u1:p>

                 Form_Data:<u1:p></u1:p>

                                  Deletes: 15<u1:p></u1:p>

                                  Relative Cost: 3.20%<u1:p></u1:p>

<u1:p></u1:p>

 

<u1:p></u1:p>

Can we use replication cloud sql server ???

$
0
0







SQL server requires the actual server name to connect to make connection to ther server … I need to synchronize offline and online … offline means my local database  online means cloud database      thanks

Windows update replisapi.dll

$
0
0

hello i use web sync for merge replication. my sqlserver is sql server 2014. I have an error that I have been looking for days and I cannot find. it is terrible the little information that is given by the error.

how i can update the replisapi.dll dll. where can i find updates? could I take for example the dll of sql 2016 or higher and put it instead?

Thank you very much for your answers
pascal
ps
excuse me my english i'm french

Transactional replication while adding distribution in publication

$
0
0

The linked server has been created but failed a connection test. Do you want to keep the linked server?


ADDITIONAL INFORMATION:

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


SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. OLE DB provider "SQLNCLI11" for linked server "Server\Instance" returned message "Login timeout expired". OLE DB provider "SQLNCLI11" for linked server "Server\Instance" returned message "A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.". (Microsoft SQL Server, Error: -1)

Web Synchronisation error -2147209352 :The server returned an invalid or unrecognized response

$
0
0

Hello everybody

we use Web synchronisation in my business.
It's very important for us.

the error that I cannot resolve is as follows :

2020-02-16 23: 26: 20.057 OLE DB Subscriber 'SRV-PREV': {call sys.sp_MSadd_merge_history90 (?,?,
2020-02-16 23: 26: 20.057 Percent Complete: 0

2020-02-16 23: 26: 20.057 The server returned an invalid or unrecognized response
2020-02-16 23: 26: 20.057 Repl Agent Status: 6
2020-02-16 23: 26: 20.057 OLE DB Subscriber 'SRV-PREV': {call sp_MSmergeupdatelastsyncinfo (?,?,
2020-02-16 23: 26: 20.072 Percent Complete: 0
2020-02-16 23: 26: 20.072 Category: NULL
Source: Merger process
Number: -2147209352

I tried everything to understand this error but I can't seem to get more information for resolve it

  •   the parameters-HistoryVerboseLevel 3 -OutputVerboseLevel 4 :does not give more information on the error
  • Initializing the subscription does not solve anything

  • Delete the subscription and recreate the subscription does not solve anything

I don't know what to do to solve the problem.

I found a link to the forum which dates from 2011.
I asked my team to do what is asked. delete and recreate the replication virtual directory and its pool.
I expect them to do it

I very much hope that this will solve the problem. miracles do exist ;-)

cordially

Pascal

Script to Monitor Undistributed Commands on Subscriber

$
0
0

Hi All,

I am a SQL DBA with no scripting knowledge. I am looking for a simple script which sends an email if "pendingcmdcount" value is greater than x. 

to summarize , 

I want to make use of below query 

USE DISTRIBUTION
GO
EXECUTE sp_replmonitorsubscriptionpendingcmds  
  @publisher ='****', -- Put publisher server name here
  @publisher_db = '****', -- Put publisher database name here
  @publication ='****',  -- Put publication name here
  @subscriber ='****', -- Put subscriber server name here
  @subscriber_db ='****', -- Put subscriber database name here
  @subscription_type ='0' -- 0 = push and 1 = pull

which typically returns just 1 row for "pendingcmdcount" and "estimatedprocesstime" 

How can i make use of TSQL in such a way that an email is triggered if value returned under "pendingcmdcount" is greater than a certain number. I have the code for email. I am looking for logic.

Thanks a lot in advance. 



MultiSubnet AlwaysOn Avilability Group and Transaction Replication

$
0
0
Hello Everyone,

We are using MultiSubnet AlwaysOn Avilability Group and Transaction Replication. I followed instructions mention on below link.

https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/configure-replication-for-always-on-availability-groups-sql-server?view=sql-server-ver15

Initially I did a test with one test database and everything woked fine for me. Multisubnet failover & Failback was tested as well.

But when I implemented that on Actual Prod, we are facing some issue:

Scenario: AlwaysOn Setup: Node 1,2,3 in Datacenter DC1 and Node 4,5 in Datacenter DC2. Total 4 Publications from 3 different databases. Separate dedicated Server for Replication Distributor Role with a dedicated distributor DB for that AlwaysOn setup. Node 1 is Primary node. Currently Replication is configured with following flow: Node 1 -> Distributor -> Subscriber. Whenever I run sys.sp_redirect_publisher stored proc to redirect publisher from node 1 to Availability Group Listener Name, Log Reader Agent started thowing error:

2020-02-06 14:49:20.787 Status: 32768, code: 53044, text: 'Validating publisher'.
2020-02-06 14:51:47.484 Status: 0, code: 21879, text: 'Unable to query the redirected server 'AlwaysOnListenerName' for original publisher 'Node 1' and publisher database 'PublicationDB' to determine the name of the remote server; Error 7303, Error message 'Error 7303, Level 16, State 1, Message: Cannot initialize the data source object of OLE DB provider "SQLNCLI11" for linked server "[25A3CE0F-294E-4BC1-B4F3-4E87B305855C]".'.'.
2020-02-06 14:51:47.484 Status: 0, code: 22037, text: 'Errors were logged when validating the redirected publisher.'.
2020-02-06 14:51:47.484 Errors were logged when validating the redirected publisher.
2020-02-06 14:51:47.796 Disconnecting from OLE DB DistLog 'DistributorServerName'
2020-02-06 14:51:47.796 Disconnecting from OLE DB Publisher 'Node 1'

Anyone faced this situation in past and if yes, please share the solution.

Thank you!

Pre/Post Snapshot Script Support for SQL 2019 on Linux

$
0
0

I have setup transactional replication between a SQL 2019 instance on Linux (publisher and distributor) and a SQL 2019 Express instance on Windows (subscriber). Data replication is working as expected, however, the post snapshot script fails with an error:

Command attempted:
/apps/streamline/repldata\unc\LXSISQL1_SISL_APP_WEBSERVICES_SISLAPP\20200216000028\SISLAPP_PostSnapshot_1.sql
(Transaction sequence number: 0x0000276E00000040005100000008, Command ID: 65)

Error messages:
Failed to obtain the SQL Server utilities installation path from the registry. (Source: MSSQL_REPL, Error number: MSSQL_REPL20155)
Get help: http://help/MSSQL_REPL20155

Are pre/post snapshot scripts supported by SQL on Linux?  I cannot seem to find any reference to this either way.

Thanks!

Alex

How do you drop a publication that is gone from SSMS but shows up in replication monitor? Here's what I've tried...

$
0
0

Hello,

I had  two test databases on one server that I had been experimenting with for transactional replication.  I wanted to delete the publication from one database and the subscription from the other and finally delete both databases.  I deleted the publication, the subscription , the jobs related to them and finally the databases.  I must confess that i wasn't as careful as I would be if I hadn't planned on just deleting everything.  So what I have now is nothing appearing in SSMS under local publications or local subscriptions for these two test databases (but pubs and subs for other useful things) but in replication monitor the publication shows up with a red x.  

I cannot use sp_droppublication  @publication='my pub name' because the publication database is gone.  Can I do anything to remove this publication from replication monitor?  This isn't a production server yet it has some users who would be severely inconvenienced if I have to drop all replication and rebuild.  Is there any other way?

Thanks.


What are the techniques and suggestion for database performance increase

$
0
0
I have a ERP application which having the single database and its having huge data(150 GB approx) on it. Now my applications are getting slowdown due to the database hit continuously. Shall I proceed with the single database or can I use some replication for reports, So that may the hit will be reduce in main database. If anyone did it in VPS servers, please suggest me.

REMOVING REPLICATION

$
0
0

We are running a transactional replication with 2 DB publication. Configuration is below:

 SVR_A = DISTRIBUTOR + PUBLISHER
 SVR_B = SUBSCRIBER

Due to a system upgrade, I'm planning to re-initialize replication from scratch. So I have the steps on removing the existing replication.

 

[1] ON SVR_A - DROP SUBSCRIPTION
 USE Published_DB;
 EXEC sp_dropsubscription @publication = N'Published_DB_Publication', 
  @subscriber = N'all', 
  @destination_db = N'Published_DB', 
  @article = N'all';
 
[2] ON SVR_B - CLEANUP SUBSCRIPTION
 USE Subscription_DB;
 EXEC sp_subscription_cleanup @publisher = @SVR_A, @publisher_db = 'Published_DB', @publication = 'Published_DB_Publication'


[3] ON SVR_A - DROP PUBLICATION
 USE Published_DB;
 EXEC sp_droppublication @publication = N'Published_DB_Publication'; 

[4] ON SVR_A - REMOVE REPLICATION
 EXEC sp_removedbreplication 'Published_DB_Publication';

[5] ON SVR_A - REMOVE SUBSCRIBER
 EXEC sp_dropsubscriber @subscriber = 'SVR_B' 


[6] ON SVR_A - REMOVE PUBLISHER AND DISTRIBUTOR
 USE Master;
 EXEC sp_dropdistpublisher @publisher='SVR_A';
 EXEC sp_dropdistributiondb 'distribution'; 
 EXEC sp_dropdistributor; 

Did I miss anything?

Thanks



The last step did not log any message! (Source: MSSQL_REPL, Error number: MSSQL_REPL22037)

$
0
0

We have one publication and in replication monitor we have one error in subscription watch list like below: "The last step did not log any message! (Source: MSSQL_REPL, Error number: MSSQL_REPL22037) Get help: http://help/MSSQL_REPL22037"

And 

1. our sql server version is 

Microsoft SQL Server 2016 (SP1-CU7-GDR) (KB4057119) - 13.0.4466.4 (X64)   Dec 22 2017 11:25:00   
Copyright (c) Microsoft Corporation  Standard Edition (64-bit) on Windows Server 2016 Datacenter 10.0 <X64> (Build 14393: ) (Hypervisor) 

2. product level is sp1.  

Our questions are:

1. how to check the details for this error.

2. If we couldn't do sql server upgrade, is there any workaround way?

Thanks a lot!

Viewing all 4054 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>