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

SQL Server 2012 - Table Replication

$
0
0

1) What Happens if Subscriber Database Restarted Automatically or Network Failure Occurred between Publisher and Subscriber Databases , Do I need to reconfigure the Replication for All databases again ?

2) Is there any possibility that I can SCRIPT OUT the whole Replication Process for PUBLISHER , DISTRIBUTOR and SUBSCRIBER Databases, So that i can quickly configure the Replication if Required?

3) Is this possible that I can Stop Replication for a single Table and Resume it for Replication again?

4) Can I use SQL Server login for configurations of Transactional Replication or is it Must to use windows authentication account ?


Error on P2P replication from one server to another but not reversely

$
0
0

Hi all, 

Our set up is 2016 SQL server and we are using P2P transactional replication among our four servers.

Recently one of the servers is reporting that it is trying to apply command" if COLUMNPROPERTY(OBJECT_ID('MSreplication_subscriptions'), 'distribution_agent', 'AllowsNull') <> 1 BEGIN alter table MSreplication_subscriptions alter column distribution_agent sysname null END"to one of its subscribers and it has failed because "only members of the (null) role can execute this stored procedure". Can anyone please explain what is distributor trying to do? what does this command do to the subscriber? and if this message is benign due to insufficient privilege of the distributor agent, how can I assign distributor agent's role properly?

Thank you

merge replication issue

$
0
0

Hi Team,

i am new to replication we have merge replication in my environment we are getting below error in replication monitor subscriber server,any one help me out how to resolve the issue 

Error messages: The merge process was unable to create a new generation at the 'Publisher'. Troubleshoot by restarting the synchronization with verbose history logging and specify an output file to which to write. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147200994) Get help: http://help/MSSQL_REPL-2147200994

Regards,

Nasar.

SQL Server Job Failure

$
0
0

Executed as user. ...QLSTATE 01000] (Message 0)  /* Executing Step: 1, DbBackup_ _AutoProductMfgTest*/ [SQLSTATE 01000] (Message 0) Execute [\sqlexpress]. _AutoProductMfgTest.dbo.pspDbAdminBackupDatabase @DbName, @BackupPath, @DaysToKeepBackups [SQLSTATE 01000] (Message 0) @FileDateCutoff = 2019-04-09T23:59:01 [SQLSTATE 01000] (Message 0) Backup Database [..._AutoProductMfgTest] To Disk = 'D:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup\ _AutoProductMfgTest\ _AutoProductMfgTest_Backup_20190411000001.bak' WITH NOFORMAT, NOINIT, NAME = 'D:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup\ _AutoProductMfgTest\ _AutoProductMfgTest_Backup_20190411000001.bak' , SKIP, REWIND, NOUNLOAD, STATS = 10 [SQLSTATE 01000] (Message 0)  10 percent processed. [SQLSTATE 01000] (Message 3211) 20 percent processed. [SQLSTATE 01000] (Message 3211)  30 percent processed. [SQLSTATE 01000] (Message 3211) 40 percent processed. [SQLSTATE 01000] (Message 3211)  50 percent processed. [SQLSTATE 01000] (Message 3211) 60 percent processed. [SQLSTATE 01000] (Message 3211)  70 percent processed. [SQLSTATE 01000] (Message 3211) 80 percent processed. [SQLSTATE 01000] (Message 3211)  90 percent processed. [SQLSTATE 01000] (Message 3211) Processed 13288 pages for database '_AutoProductMfgTest', file '_AutoProductMfgTest_Data' on file 1. [SQLSTATE 01000] (Message 4035) 100 percent processed. [SQLSTATE 01000] (Message 3211)  Processed 2 pages for database '_AutoProductMfgTest', file '_AutoProductMfgTest_Log' on file 1. [SQLSTATE 01000] (Message 4035) The statement has been terminated. [SQLSTATE 01000] (Message 3621) BACKUP DATABASE successfully processed 13290 pages in 14.338 seconds (7.592 MB/sec). [SQLSTATE 01000] (Message 3014) RESTORE VERIFYONLY FROM DISK = 'D:\Program Files\Microsoft SQL

Move Published database to new server

$
0
0

I wanted to move the published database to new server.

The distributor is different server and this publisher have 5 subscribers.

I am following below sequence.

1)Stop the log reader and distribution agent job on distributor

2)Take backup of published DB

3)Restore it on new server


After this can someone guide me what should be sequnce of action on publisher,subscriber and distributor?

Old snapshot files not being deleted from working directory

$
0
0
Greetings, the old snapshot files are not deleted from the working directory share for the transactional replication we have set up. Job "Distribution clean up: distribution" is running, and it has  @max_distretention set at 72 hrs. What else might prevent the files from being deleted? There are no errors showing in the job, and the account running the job has permissions to delete from the share/folder. Running SQL Server 2008 R2. Thanks

SQL Snapshot Replication

$
0
0

Fellow SQLers,

Can someone explain if sql snapshot replication does a complete refesh from publisher to subscriber every time snapshot cycle is run? Or, if after the initial snapshot,  is it just the changes of the data to those articles in the publisher that gets sent?

thx

MG

OLE DB provider "SQLNCLI11" for linked server "\sqlexpress" returned message "Login timeout expired". [SQLSTATE 01000]

$
0
0

Processed 379 pages for database '_x_x', file '_x_x_Log' on file 1. [SQLSTATE 01000]
BACKUP LOG successfully processed 379 pages in 0.410 seconds (7.219 MB/sec). [SQLSTATE 01000]
BackupSetID = 1 for database '_x_x' [SQLSTATE 01000]
RESTORE VERIFYONLY FROM DISK = 'C:\MSSQL\Backup\x\_x_x_Backup_20190415150006.trn' WITH  FILE = 1,  NOUNLOAD,  NOREWIND [SQLSTATE 01000]
The backup set on file 1 is valid. [SQLSTATE 01000]
End of Script [SQLSTATE 01000]
Test Linked Server Connection: \sqlexpress [SQLSTATE 01000]
OLE DB provider "SQLNCLI11" for linked server "\sqlexpress" returned message "Login timeout expired". [SQLSTATE 01000]
OLE DB provider "SQLNCLI11" for linked server "\sqlexpress" 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.". [SQLSTATE 01000]
Will either of the fix work?

  • Set the remote login timeout to 30 seconds, by using this code:
    sp_configure 'remote login timeout', 30
    go
    reconfigure with override
    go
  • Set the remote query timeout to 0 (infinite wait), by using this code:
    sp_configure 'remote query timeout', 0 
    go
    reconfigure with override
    go
  • or setting the Named Pipes to "Disabled"


DBCC Checkdb

$
0
0

Maintenance Plan: DBCC Checkdb
Duration: 00:00:00
Status: Warning: One or more tasks failed.
Details:
Check Database Integrity Task ()
Check Database integrity on Local server connection
Databases that have a compatibility level of 70 (SQL Server version 7.0) will be skipped.
Databases: All databases
Include indexes
Task start: 2019-04-07T02:00:01.
Task end: 2019-04-07T02:00:01.
Failed:(0) Alter failed for Server ''.

One of the thread has the link to execute the statement:

EXEC

sys.sp_configureN'user options', 0RECONFIGURE

got the message:

Configuration option 'user options' changed from 0 to 0. Run the RECONFIGURE statement to install.

Msg 5832, Level 16, State 2, Line 1

The affinity mask specified does not match the CPU mask on this system.

Please advice to resolve this issue.

AlwaysOn problems

$
0
0

Hello,

Cold you please help, can't find information in documents. 

I am implementing  AlwaysOn async on sql server 2017 enterprise. Initial data synchronization is full db and log backup.

its a non_domain and without Windows server failover clustering, I implement it via certificates.

So, the questions are:

  1. how can I change backup time (I think I saw somewhere default is 15 min)?
  2. where are kept the transaction log backups? 
  3. when I am testing it, want to see can I bring secondary read-write mode(must do manually), database become "not synchronizing" and no action can be done there. How can I change roles of primary and secondary servers and how I can bring primary server to life after. 

Please help me ....

Switching to TLS 1.2 protocol using Web Synchronization between different network domains

$
0
0

We have SQL Replication with the publisher and distributor running on Windows Server 2012 R2 using SQL Server 2016 SP2 within a secure network. The subscriber is running on Windows Server 2008 R2 within a different secure network using web synchronization, calling the replisapi dll, through the firewalls using https. This replication is working and has been for a few years now.

We recently tried to patch both servers to move to TLS 1.2 protocol only. It broke the replication and we re-enabled the other SSL and TLS protocols as a temporary fix. We MUST move to the TLS 1.2 ONLY - SOON.

What more do you need from me to help figure out why it is not working?

We have seen the error messages in the subscriber SQL Agent job log but they are fairly generic.

Where else can we look, and/or what else do we need to enable, to find more details about what is causing the problem?

Merge Agent change default validateInterval setting from 60 minutes

$
0
0

We recently upgraded from SQL Server 2012 to SQL Server 2016.  During this process the validate subscription now occurs every 60 minutes, where before we did manually as needed.  How can I view and possibly change this setting that will work for us?

Thanks,

Toni



Toni

cannot create distribution or find local publications

$
0
0

I am using sql server 2014 express and follwoing the tutorials from Microsoft. I tried to right click replications I can't find configure distribution under there, all I see is "Launch replication monitor", "generate scripts", "update replication passwords", "new" which only leads to "local subscriptions", "reports" and "refresh". I also don't see local publications if I expand replications. The tutorials didin't guide me to create a publisher so when it came time to create a distributor I back tracked and went to "launch replication monitor" and then add publisher but I'm getting an error telling me my server is neither a publisher nor a distributor or I don't have permission to access replication functionality on this server. I went into permissions by right clicking on the instance and going to properties but don't see what to do there. Any suggestions?

Transactional Publication Switching Between Multiple IP Addresses and Pipes to Same Remote Server

$
0
0
I have Transactional replication from SQL Server 2016 to remote SQL Server 2016.

Publisher and Distributor on local server, Subscription on remote server.

Using Alias=Server Name, Server=IP Address, Protocol=tcp, Parameters=1433 I can successfully replicate to remote SQL Server database.

New requirements being proposed would have 1) Existing connection for on-going transactional replication and 2) new VPN connection with a different IP Address from the IP Address in #1 to be used for initial population of replicated tables due to large volume.

When I tried setting up a second Alias using a different IP Address but keeping the other information the same it updated the IP Address for the existing Alias.

If I have to switch the IP Address of the server between the 2 pipes being used will this require a complete refresh of the Subscription each time I switch or will replication just keep on going?

Is there anything else I need to consider when doing this?

Thanks!

Replication Scripts Stopped Working..

$
0
0

I have a merge publication that I always create with a script but has now stopped working with what appears to be a complete server problem.

 

The actual command i am executing is a simple

sp_addpublication_snapshot

 

but it fails with

 

Msg 50000, Level 16, State 1, Procedure sp_add_jobstep_internal, Line 253

The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction.

Msg 3931, Level 16, State 1, Procedure sp_MSadd_repl_job_unsafe, Line 376

The current transaction cannot be committed and cannot be rolled back to a savepoint. Roll back the entire transaction.

 

 

I have tried recreating the database from scratch, renaming it, renaming the publication, even disabling the publications altogether but it makes no difference. There is nothing in the sql or event logs and I cant do any work until Ive got past it - help!

 

I am using SQL 2005 SP2 if that makes any difference.

 

Thanks

Andy


Data transfer time in AlwaysOn read_scale

$
0
0

Hello,

I have implemented an AlwaysOn Read_scale, but still have a question and I can't find answer anywhere.

If I did a failover and now my secondary server works as a primary, and after some period of time I can bring my real primary to life, so how long I must keep it as a secondary? I mean, How long it will take to transfer all data that have been collected  during downtime, from new_primary to my real primary?

Can't find data folder in MSSQL

$
0
0

I'm connected to a sql server via remote connection from my computer that has sql server express 2014 on it. I'm trying to do transactional replciation between the two. I'm following along with the tutorials that microsoft has for this and right now setting up servers in preparation for replication according to the tutorials.

On lesson 2 of that guide to set up your tutorials I'm trying to find the filepath on this server that's located at this production facility, the filepath is C:/ProgramFiles/Microsoft SQL Server/MSSQL.X/MSSQL/data this is to create a snapshot folder at the publisher to share it. The thing is though I don't see the data folder in MSSQL and i've looked for it and still can't find it. So my question is how important is it to make this repl_data folder for sharing in that specific directory, can I just make it under MSSQL?

What is better read_scale or AlwaysOn with WSFC?

$
0
0

Hello,

If it is should be without domain, async, with manual failover, with not readable secondary replica(no metter replication type, the main question is cluster creation) AlwaysOn, then is there any sense of cluster/HA ?

I mean, for this parameters both cases seems similar. Or the downtime in the case of failover can be different and switching between two servers that are in one cluster can be faster and less data loss?

Snapshot agent not working properly

$
0
0
TITLE: View Snapshot Agent Status
------------------------------

The agent could not be started.

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=12.0.2000.8&EvtSrc=Microsoft.SqlServer.Management.UI.ReplUtilitiesErrorSR&EvtID=CantStartAgent&LinkId=20476

------------------------------
ADDITIONAL INFORMATION:

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

------------------------------

SQLServerAgent is not currently running so it cannot be notified of this action.
Changed database context to 'Ignition'. (Microsoft SQL Server, Error: 22022)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=12.00.5000&EvtSrc=MSSQLServer&EvtID=22022&LinkId=20476

------------------------------
BUTTONS:

OK
------------------------------

Can't connect to subscriber from publisher

$
0
0

I'm trying transactional replication from a server that I'm plugged into to a server that exists in my vm. However, when I try to create the subscriber from the server i'm remoted into(publisher) I get and error saying it can't connect to the server on my vm. I've already checked the login info to be correct and that both the publisher and subscriber allow remote connections.

Here is the error:

TITLE: Connect to Server
------------------------------

Cannot connect to WIN-T6S43L3VKK9.

------------------------------
ADDITIONAL INFORMATION:

Failed to connect to server WIN-T6S43L3VKK9. (Microsoft.SqlServer.ConnectionInfo)

------------------------------

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=53&LinkId=20476

------------------------------

The network path was not found

------------------------------
BUTTONS:

OK
------------------------------


Viewing all 4054 articles
Browse latest View live


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