Window Server2012 r2 joins the domain and the network and share center display "unknown"

September 7, 2018, 2:40 am

≪ Previous: Retrieving data from Distributor

Hi, I am currently experiencing a problem and hope to find help, as follows:

I deployed alwaysOn, and the machine environment is "window server 2012 r2". I added the machine TEST01 to the domain AD (TEST01 and AD are two different network segments)

Open the network and sharing center of my machine "TEST01", display "unknown", the service for monitoring the status is disabled

At present, I already know that opening the following two services can solve the problem:

Network Location Awareness NlaSvc

Network List Service netprofm

But even then, every time I restart the server or run for a while, it changes back to "unknown".
In response to this phenomenon, I have made the following solutions:
1. Change the above two services from the original "automatic" to "automatic (delayed start)". After restarting, it still does not work and cannot solve the problem.

2. Open domain controller AD and machine TEST01 open port 389. After restarting, it still does not work and cannot solve the problem.

3. Set the default gateway. After rebooting, it will still not work and will not solve the problem.

This problem has been bothering me for a long time, and the current alwaysOn failover will also prompt me that the server connection timed out. What should I do to solve this problem? my English is poor:(

↧

Add column locking Replication

September 10, 2018, 4:24 am

≫ Next: SQL Server replcation - delivering a snapshot through FTP time out after 30 seconds on large files

≪ Previous: Window Server2012 r2 joins the domain and the network and share center display "unknown"

Hi Experts,

I tried to add 7 columns which all allowed NULL with no constraint. The change on the source got deployed successfully but when it was replicated to target replicated 45 DB's. The production DBA's reported a lot of performance issue related to locking of table.

Am still not sure how adding empty Null tables can cause performance degradation when it just a meta data change I guess.

Records around 15 million.

Could you please suggest the possibilities due to which the degradation was caused. Ways to identify the root cause like wait statistics should be good enough to know the root cause or some other approach can be opted.

Thanks & regards

Priya

↧

SQL Server replcation - delivering a snapshot through FTP time out after 30 seconds on large files

September 14, 2009, 1:03 am

≫ Next: delete -delete Conflict In Peer-To-Peer Replication?

≪ Previous: Add column locking Replication

Hi all.

I'm having a issue when delivering/requesting a snapshot through FTP.

After studiyng the SQL logs, the problem seems to be that when the subscriber starts the download through FTP, everything seems to be working fine.
But when hitting a large file (5Mb and up) and the transferperiod exceed 30 seconds, the transfer s aborted and the initial transfer of the snapshot is aborted (starting all over again)

I have tried to enter a higher value for timeout of remote connections under the server settings (this is SQL 2008) Server properties --> Connections --> Allow remote connections to this server --> Remote query timeout == 0

This, and several things has been bumped up on both the distributor and the subscriber without any luc.

Any suggestions? :)

↧

delete -delete Conflict In Peer-To-Peer Replication?

September 14, 2018, 4:54 am

≫ Next: delete -delete Conflict In Peer-To-Peer Replication?

≪ Previous: SQL Server replcation - delivering a snapshot through FTP time out after 30 seconds on large files

Hi All,

i am getting below error in Peer-to-Peer replication , please help to resolve issue...

error:

A delete-delete confict was detected and resolved .The row could not be deleted from the peer since the row does not exist. the incoming delete was skipped

↧

delete -delete Conflict In Peer-To-Peer Replication?

September 14, 2018, 4:54 am

≫ Next: delete -delete Conflict In Peer-To-Peer Replication?

≪ Previous: delete -delete Conflict In Peer-To-Peer Replication?

Hi All,

i am getting below error in Peer-to-Peer replication , please help to resolve issue...

error:

A delete-delete confict was detected and resolved .The row could not be deleted from the peer since the row does not exist. the incoming delete was skipped

↧

delete -delete Conflict In Peer-To-Peer Replication?

September 14, 2018, 7:39 am

≫ Next: The proxy auto-configuration url was not found. Followed all advice RE IE settings still stuck

≪ Previous: delete -delete Conflict In Peer-To-Peer Replication?

Hi All,

i am getting below error in Peer-to-Peer replication , please help to resolve issue...

error:

A delete-delete conflict was detected and resolved .The row could not be deleted from the peer since the row does not exist. the incoming delete was skipped

↧

The proxy auto-configuration url was not found. Followed all advice RE IE settings still stuck

August 21, 2018, 2:34 am

≫ Next: copying 35 subscriptions.

≪ Previous: delete -delete Conflict In Peer-To-Peer Replication?

Folks,

I'm having trouble configuring a SQL 2008 R2 subscriber on an AWS EC2 server.

I must setup merge replication and subscribers at least once a week for the past couple of years without any issues, or at least ones I can usually find an answer for.

No matter what I've tried, including the IE settings turned off for Connections -> LAN Settings ->Automatically Detect and Use configuration script the error "The proxy auto-configuration url was not found" persists.

Placing the URL in the IE address allows me to get to "SQL Server WebSync ISAPI"

I also have other subscribers working happily with the same publisher.

Is there anything special about AWS that could be causing this? I've never had a server I couldn't configure.

Thanks in advance

↧

copying 35 subscriptions.

September 13, 2018, 12:15 am

≫ Next: Change database compatibility for published database (merge replication)

≪ Previous: The proxy auto-configuration url was not found. Followed all advice RE IE settings still stuck

I have 35 subscribers to a single publisher. How many can I copy?

↧

Change database compatibility for published database (merge replication)

September 19, 2018, 2:17 am

≫ Next: Copy or restore read-only database

≪ Previous: copying 35 subscriptions.

Hello

I have 3x Sql Server 2008 R2 servers running. The first is publisher and distributor. The other 2 are subscribers. Some databases have a merge replication setup. For one of those db's I would like to change the compatibility level from 'Sql Server 2000(80)' to 'Sql Server 2008(100)'. But I'm not sure if I can do that without any problems. Not from an application point of view. Application is our own. I just want to be sure on SQL level replication doesn't brake. The publication already has the compatibility level 'Sql Server 2008 or later'.

Anybody here who has already done that?

Kind regards

Koen

↧

Copy or restore read-only database

September 20, 2018, 12:08 pm

≫ Next: Identity Range Check Problem

≪ Previous: Change database compatibility for published database (merge replication)

Hello,

I'm using SQL Server 2012.

I have a read-only database and I have create a replica from it and a new database should be read-write

I tried to use 'Copy database ...' operation but it failed with this error:

The EXECUTE permission was denied on the object 'xp_instance_regread', database 'mssqlsystemresource', schema 'sys'.
The EXECUTE permission was denied on the object 'xp_instance_regread', database 'mssqlsystemresource', schema 'sys'. (Microsoft SQL Server, Error: 229)

Then someone told me it's because source database is in read-only mode.

My question: how could I make a copy or replica or etc from read-only database? Either using GUI or script (it does not matter for me)

Thanks

susja

↧

Identity Range Check Problem

September 24, 2018, 1:56 am

≫ Next: Replicate data FROM Azure SQL LogicalServer to On Premises SQL Server 2017 Standard Edition - not using Data Sync

≪ Previous: Copy or restore read-only database

Hello all,

This problem always happens whenever a merge replication is used and whenever a table has auto-number (also known as identity).

[SQLSTATE 01000] (Message 0) The insert failed. It conflicted with an identity range check constraint in database 'xxx', replicated table 'dbo.replicated_table', column 'id'. If the identity column is automatically managed by replication, update the range as follows: for the Publisher, execute sp_adjustpublisheridentityrange; for the Subscriber, run the Distribution Agent or the Merge Agent. [SQLSTATE 42000] (Error 50000). The step failed.

I have tried various solutions but none of them seems to work.

I read a post that they released a hotfix available to download for this bug on Microsoft SQL Server 2005, however I am using the 2016 SQL Server.

I tried changing the range of the publisher, subscriber, everything but nothing seems to work.

I am suspecting that the problem would either be:

1) A bug in the replication

2) Something from the application side causing it (The way users insert their data)

Thank you for the time you spent on reading this post, and your answer is much appreciated!

↧

Replicate data FROM Azure SQL LogicalServer to On Premises SQL Server 2017 Standard Edition - not using Data Sync

September 13, 2018, 7:28 pm

≫ Next: Merge Replication not replicating delete to subscribers even I set @delete_tracking = true

≪ Previous: Identity Range Check Problem

We need to replicate data one way from an Azure SQL LogicalServer database in the cloud to our on premises SQL Server 2017 Standard Edition.

We cannot use SQL Data Sync as it uses 'Eventual Consistency', meaning the data eventually syncs however that may not be in the order that the writes occurred in the Azure SQL Database.

We require transactional consistency. As in when a write happens on the primary database, this is then replicated in order to the subscribing database.

I would use regular SQL Replication however this is not available in Azure SQL LogicalServer.

What other option do I have ?

I was looking into AlwaysOn High Availability but that looks more like a hot standby setup.

Thanks,

↧

Merge Replication not replicating delete to subscribers even I set @delete_tracking = true

September 26, 2018, 5:12 am

≫ Next: Transactional Replication on Always On

≪ Previous: Replicate data FROM Azure SQL LogicalServer to On Premises SQL Server 2017 Standard Edition - not using Data Sync

I'm currently testing a merge replication setup and I've discovered a problem with it. I run a delete statement on two tables on my publisher and after running SQL Data Compare I found that some rows on both tables did not delete. There are no errors reported in the replication monitor. My question is, how can I troubleshoot further what went wrong here?

when I reconfiguration merge replication setup more than once it work correctly!! why???

↧

Transactional Replication on Always On

June 28, 2018, 8:07 pm

≫ Next: SQL Server Replication to Azure SQL Database Failed: Provide the Actual Name of the Server

≪ Previous: Merge Replication not replicating delete to subscribers even I set @delete_tracking = true

In our AlwayOn environment I have two SQL servers 2012 Ent.edition (SERVER A, and SERVER B). I setup a transaction replication for [database A ], pointing to listener which shouldn't cause any issue if a failover happened. Tested, worked just fine after a failover, but when I shut off one of the servers in AOAG ,in test environment, replication stops working. There is no error on the replication monitor. For testing purpose,I have inserted few records on the database it works fine on AOAG, but on the Subscriber the data modification is not replicated until I bring up the other server. Once the server is up, then the replication start to work. I'm pretty sure, I might be missing something, this can't be this way by design.

Any Idea/recommendation ?

Here is what I have for Replication on AOAG.

Distribution Server A ( contains Distribution database ) - SQLSERVER 2012 This on a remote server.
two subscribers - Sv1 and sv2 - SQLSERVER 2012 Enterprise
Publishers ( SERVER A and B - from AOAG ) - SQLSERVER 2012

↧

SQL Server Replication to Azure SQL Database Failed: Provide the Actual Name of the Server

September 28, 2018, 4:59 am

≫ Next: dropping merge publication is extremely slow

≪ Previous: Transactional Replication on Always On

Hi All,

I am using an Azure SQL database. Free Trial Subscription

I was able to connect to the database from SSMS (Management Studio) and from Portal Query Editor.

I configured a database publisher on my local SQL Server (SQL 2014). everything works fine until i choose to create a subscription which is the Azure database . When i try to connect it gives me

Cannot connect to myserver.database.windows.net. SQL Server Replication requires the actual server name to make a connection to the server. Specify the actual server name myserver . (Replication.Utilities)

I tried the solution from https://stackoverflow.com/questions/8212032/sql-server-replication-requires-the-actual-server-name-to-make-a-connection-to-t

but it keeps saying the Could not find procedure sp_addserver . it is no more supported

Appreciate any help

↧

dropping merge publication is extremely slow

September 29, 2018, 12:19 pm

≫ Next: Problem in removing replication for one publication

≪ Previous: SQL Server Replication to Azure SQL Database Failed: Provide the Actual Name of the Server

Sometimes i need to refresh the databases and need to drop merge publication. I export the drop script and do it. I noticed some times it takes lot of time to remove the publication and it is stuck. How to run it quickly? any best practice?thank you.

↧

Problem in removing replication for one publication

September 29, 2018, 4:52 pm

≫ Next: How to copy Standby/Read-only database

≪ Previous: dropping merge publication is extremely slow

Hi,

We have implemented transaction replication that is working fine.

One publisher with 3 publications and one subscriber.

Today we added another publication on same publisher & added another server as subscriber. Something went wrong with configuration & we did not succeed. In fact log reader agent did not start with error "the process could not execute sp_replcmds".

We removed subscription & publication and repeated the process again but in vain.

I used following scripts to remove subscription & publication.

-- This batch is executed at the Publisher to remove -- a pull or push subscription to a transactional publication.DECLARE @publication AS sysname; DECLARE @subscriber AS sysname; SET @publication = N'AdvWorksProductTran';SET @subscriber = $(SubServer); USE [AdventureWorks2012] EXEC sp_dropsubscription @publication = @publication, @article = N'all', @subscriber = @subscriber; GO

--EXEC sp_removedbreplication 'AdventureWorks2012'

DECLARE @publicationDB AS sysname; DECLARE @publication AS sysname; SET @publicationDB = N'AdventureWorks';SET @publication = N'AdvWorksProductTran';-- Remove a transactional publication.USE [AdventureWorks2012] EXEC sp_droppublication @publication = @publication; -- Remove replication objects from the database.USE [master] EXEC sp_replicationdboption @dbname = @publicationDB, @optname = N'publish', @value = N'false'; GO

Still no luck. When I launch replication monitor , it shows names of those publications with

red marked. Distribution database is also there. Some agent jobs are still there for this publication.

Any help will be highly appreciated.

Thanks.

↧

How to copy Standby/Read-only database

October 1, 2018, 5:11 pm

≫ Next: Setting up transactional replication fails with error 3933 on sp_addlogreader_agent when using a remote distributor

≪ Previous: Problem in removing replication for one publication

Not sure why I can't open the thread I opened recently hence I'm opening this one instead.

Hello,

I'm using SQL Server 2012.

I have a read-only database and I have create a replica from it and a new database should be read-write

I tried to use 'Copy database ...' operation but it failed with this error:

Then someone told me it's because source database is in read-only mode.

My question: how could I make a copy or replica or etc from read-only database? Either using GUI or script (it does not matter for me)

Thanks

---

’ve got dba role for the database in order to exclude permission issue.

Nevertheless when I tried to copy Standby dB I’ve got an error.

Folks: could you suggest which steps should be taken in order to make a copy of Standby/read-only database?

Thanks

susja

↧

Setting up transactional replication fails with error 3933 on sp_addlogreader_agent when using a remote distributor

October 4, 2018, 4:49 am

≫ Next: Distribution agent could not apply a generated snapshot file

≪ Previous: How to copy Standby/Read-only database

Hi,

I've got the following set up:

One server cluster (active/passive) Windows Server 2012 with SQL Server 2014 (12.0.5589.7) as publisher
One server running Windows Server 2012 with SQL Server 2014 (12.0.5589.7) as distributor
One server cluster (active/passive) Windows Server 2012 with SQL Server 2014 (12.0.5589.7) as subscriber

The "publisher" has an alias pointing to itself on non-standard port and appears to be Linked to itself when looking at LinkedServers.

I've tried setting up the source SQL Server as both distributor and publisher, in which case everything runs smoothly.
However, when I try to set it up the way we want it (using another server as distributor, still inside the same network)
I run into problems at this point:

exec [BAMPrimaryImport].sys.sp_addlogreader_agent 
@job_login = N'nnn\SVC-SqlReplUsr', 
@job_password = 'mypassword', 
@publisher_security_mode = 0, 
@publisher_login = N'repl_admin', 
@publisher_password = N'mypassword', 
@job_name = null

The error I get is:

Msg 3933, Level 16, State 1, Procedure sp_MSrepl_addlogreader_agent, Line 184 [Batch Start Line 7] Cannot promote the transaction to a distributed transaction because there is an active save point in this transaction.

I've tried running dbcc opentran, but there are no open transactions.
I've also tried:

EXEC sp_configure 'remote proc trans', '0';
RECONFIGURE;

To no avail.

I've tried Googling this but now I start to realize that this is well above my knowledge. Does anyone have any ideas what to try next?

↧

Distribution agent could not apply a generated snapshot file

March 8, 2015, 4:12 am

≫ Next: SQL 2017 returns "The merge process could not replicate one or more INSERT statements to the 'subscriber'."

≪ Previous: Setting up transactional replication fails with error 3933 on sp_addlogreader_agent when using a remote distributor

In my case , some main info as follows . after add a article into one publication , then manually execute sp_startpublication_snapshot to generate snapshot ,and with no errors , but distribution agent didnot apply it . How to fix ?

Type:Transaction Replication

sync_method:database snapshot character

allow_anonymous:false

immediate_sync:false

snapshot_in_defaultfolder:false

alt_snapshot_folder:[new path]

repl_freq:continuous

↧