Distributions issues

April 22, 2013, 1:29 pm

≪ Previous: In which replication Distributor and subscriber not run under same instance.

Hi team,

when i tire to created the Distribution in production server, i am getting the bellow error.

Note : we are using sql server 2008r2 server

ERROR MESSAGE:

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

Sql server colud not configure abc as distribution
An exception occurred while executing a transact SQL statement or batch.
An error occurred during decryption.there is no remote user 'distribution_admin' mapped to local user'(null)' from remote server 'test_distribution'
Changed database context to 'master'.[microsoft sql server,error:15466]

↧

Publication issue

April 22, 2013, 1:22 pm

≫ Next: Can we install SQL 2008 R2 SP2 only one one Peer in P2P environment?

≪ Previous: Distributions issues

HI team,

we are configuring new publication in local server we are geeing the bellow error..

↧

Can we install SQL 2008 R2 SP2 only one one Peer in P2P environment?

April 22, 2013, 11:40 pm

≫ Next: Questions on Immdiate Updating Subscriptions.

≪ Previous: Publication issue

Hello,

If we have 2 or 3 peers in a SQL 2008 R2 P2P setup and they are all on RTM release, is it feasible to install SP2 only on one peer? A couple of reasons for this question:

1- Can we have different versions of MSSQL running on P2P?

2- Can we delay putting SP2 on the other peer(s) as in days or weeks? Just in case we run into issues after applying SP2 then at least we would not have issues with all the peers.

3- If we plan to upgrade to SQL 2012, would it be possible to add a new peer with SQL 2012, join it with the other peers in SQL 2008 R2? This way we can move the services to SQL 2012 peer without any long downtime?

Thank you.

↧

Questions on Immdiate Updating Subscriptions.

February 24, 2009, 2:16 pm

≫ Next: How to reinitialize a subscriber for a single table without applying entire snapshot and without schema changes

≪ Previous: Can we install SQL 2008 R2 SP2 only one one Peer in P2P environment?

Greetings all! I've got plenty of experience using Transactional replication to replicate data to a reporting server, but not much else.

I may have a requirement to have 6 DB's exist on two different boxes for some time. My requirements would essentially be close to those required for using Transactional replication with immediate updating subscribers for DR purposes. I should be clear that I would be using a SQL 2000 Publisher, a SQL 2005 Subscriber, and a SQL 2005 remote Distributor. So my questions would be:

Article Properties (tables) -- If I set everything to True for Copy Objects And Settings to Subscriber, will my tables be "complete"? Would all constraints, properties, etc. be there? If I had to fail over and start using this server as my primary server, would all queries against these tables work?
I was successfully able to do a test of 1) turn off the Publisher, 2) insert a row into the Subscriber, 3) turn the Subscriber back on, 4) verify that the record made it over to the Publisher. Is there a limit to how long one of these boxes can be offline for and still function (i.e. make it over to the other server once it's turned back on)?

TIA, ChrisRDBA

↧

How to reinitialize a subscriber for a single table without applying entire snapshot and without schema changes

February 16, 2011, 5:30 am

≫ Next: Transactional Replication: Custom Replication Procedures Overwritten with default replication procedures

≪ Previous: Questions on Immdiate Updating Subscriptions.

Hi members,

We have set up transactional replication in our environment. Whenever we reinitialize a subscriber, SQL Server applies the entire snapshot onto subscriber and thus we lose some customized partition changes and indexes on the subscriber database.

How can we overcome this situation? Is there a way we can reinitialize (may be I am not using the right technical word) or synchronize a single table without applying entire snapshot and without recreating tables at the subscriber database??

For example, there is some error in replication and a table could not be updated. Thus during the error period, the table will be out of sync with publisher database. To recover from this situation manually (I know SQL Server will try to synchronize internally), can we select a single table and synchronize it?

Moreover, we also want to know the best practices regarding subscriber reinitialization when a new table is added in publication. As far as I know we can trigger snapshot agent manually but would the snapshot agent apply entire snapshot or a specific table snapshot in this case? We want to avoid entire subscriber reinitialization in this case too.

Regards,

Murtaza

↧

Transactional Replication: Custom Replication Procedures Overwritten with default replication procedures

October 1, 2009, 9:52 am

≫ Next: Replication issue

≪ Previous: How to reinitialize a subscriber for a single table without applying entire snapshot and without schema changes

Problem:

Using Transactional replication, our customized replication procs are sometimes overwritten on the subscriber with the standard MS replication procs for no apparent reason.

Impact:

This is causing business impact due to time to the extra time it takes to address and correct the problem - especially in Development and Test environments where data isn't always up to date.

Platform:

--AND--

Scenario:

A new transactional replication publication is created with one article to one subscriber using a "@Sync_Type = NONE" subscription (due to large table size and the data already existing on the subscriber). By default, the MS replication procs are created on the subscriber in the subscription database (ie. sp_MSins_tablename). I overwrite the default replication procs with my own customized replication procs and all is good.

Some time later, maybe a day, maybe a month or more, replication fails with a data consistency error like "Row was not found at the subscriber when applying replicated command…". I look at the replication procs and see that they are the default MS replication procs and my custom procs have been overwritten by the system at some point, even though there were no alterations to the published table. Please ignore the fact there is a data consistency error - remember this affects us most in development where the data isn't always pristine. Part of the purpose of the custom repl procs is to deal with that type of error without having to ignore those errors.

I would expect the procs to get overwritten with default procs in the event that the published article was altered, but there is no evidence of this.

Looking at the system trace, I can see where SQL Server dropped and recreated the procs, but there is no supporting DML change that would have triggered this behavior.

As a stop-gap measure, I have turned off bit 2 of the Schema_Option column in sysarticles on the publisher. This is the equivalent of the GUI setting "Copy INSERT, UPDATE and DELETE stored procedures = FALSE" in the article properties, but this should not be necessary. The system shouldn't overwrite the custom replication procs for no reason. I'm sure there is a reason, but I can't figure out what it is.

Has anyone else experienced this behavior and effectively dealt with it?

↧

Replication issue

April 23, 2013, 9:51 am

≫ Next: Merge Replication - Subscriber drops subscription randomly!?

≪ Previous: Transactional Replication: Custom Replication Procedures Overwritten with default replication procedures

HI team,

we are creating the publication successfully, after we are configuring the new subscribes successfully,

but here in subscribers server database is created but articles are not creating..

could plz give me any specific region..

Regards,

Chadnu

↧

Merge Replication - Subscriber drops subscription randomly!?

April 14, 2013, 8:01 pm

≫ Next: Merge Meta Data Cleanup

≪ Previous: Replication issue

Hi guys,

I'm hoping if you guys could help to explain the weird situation I'm facing.

On our main Windows Server 2008 R2, we have SQL Server 2012 Standard setup with Merge Replication. The server has around 15 subscribers. One of the subscribers replicates data on a VPN connection set up over a mobile broadband connection. Now what has happened is the mobile connection dropped and the subscriber could not connect to the server through VPN. After a few days when the connection was back up, the replication monitor started giving this error --

Error messages:
The subscription to publication 'abc' could not be verified. Ensure that all Merge Agent command line parameters are specified correctly and that the subscription is correctly configured. If the Publisher no longer has information about this subscription, drop and recreate the subscription. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201019)
Get help: http://help/MSSQL_REPL-2147201019
The subscription could not be found. (Source: MSSQLServer, Error number: 20021)
Get help: http://help/20021

I checked the subscription at the subscriber and indeed the said subscription was missing from there. This has happened for the second time in the last few months and I'm not exactly sure if it's entirely because of the network dropout. I have had similar situations where a subscriber was off-network for a while and when it was connected back to the network, it replicated fine. I tried checking the error logs to get a clue of why this was happening but no success.

It's a pain to drop the database and recreate the subscription back again as it's very time consuming. Any help on why this is happening would be great.

Thanks

↧

Merge Meta Data Cleanup

April 23, 2013, 5:06 am

≫ Next: Transaction Log Growing due to Pending Transaction (Replication)

≪ Previous: Merge Replication - Subscriber drops subscription randomly!?

If a merge replication is dropped and re- created again, how do we clean the meta data associated with it.I used the SP sp_mergemetadataretentioncleanup at the subscriber, with a retention period of 30 days. It is not cleaning up the subscriber meta data.

Any idea how do I proceed with the clean up.

Thanks

↧

Transaction Log Growing due to Pending Transaction (Replication)

April 8, 2013, 8:06 am

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

≪ Previous: Merge Meta Data Cleanup

SQL Server 2005 SP4 with Transactional replication.

I have this Database Log, which keeps growing due to a Pending transaction in the Database Log. (DB in SIMPLE recovery Mode)

If i issue a DBCC OPENTRAN i get :

Replicated Transaction Information:
Oldest distributed LSN : (0:0:0)
Oldest non-distributed LSN : (47839439:351:1)

The following Query using fn_dblog gives me LSN and Transaction ID Info.
select * from::fn_dblog(NULL,'47839439:351:1') -Gives me this result

If i have to Shrink the Log i have to use sp_repldone to mark the transactions as replicated or skipped.

I take precautions in running this statement as this is not always what you want to do manually as it is internally done by the Log Reader Agent.

EXEC sp_repldone @xactid = NULL, @xact_segno = NULL, @numtrans = 0, @time = 0, @reset=1

Now.. What if i Just want to mark just the transaction in question as done.. using the @xactid

How can i translate the CurrentLSN or TransactionID or LogRecord or Transaction SID or any other vlue to--> @xactid.....

↧

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

April 21, 2013, 5:15 pm

≫ Next: SQL Server 2008 Merge Replication: Metadata Cleanup Failure

≪ Previous: Transaction Log Growing due to Pending Transaction (Replication)

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.

↧

SQL Server 2008 Merge Replication: Metadata Cleanup Failure

April 25, 2013, 1:57 am

≫ Next: Transactional Replication from Publisher=SQL2008R2 (DB running in 80 Compatibility Mode) - To Subscriber=SQL2012 ?

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

We are an issue, related to the metadata cleanup. Some time ago we reduced the retention period down from the default to 3 days and did not encounter issues, then last suddenly began to encounter the error below for various publications. It does not occur on every synchronisation. The output from setting agent parameters defined at http://msdn.microsoft.com/en-us/library/ms151872(d=printer,v=sql.100).aspx is shown below

2013-04-24 11:09:13.648 The merge process could not perform retention-based metadata cleanup in database 'XXXXX'. If this failure continues, try increasing the query timeout for this process, or try reducing the retention period. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write.

2013-04-24 11:09:13.648 OLE DB Subscriber 'XXXXXXX': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}

2013-04-24 11:09:13.664 Percent Complete: 57

2013-04-24 11:09:13.664 The merge process could not perform retention-based metadata cleanup in database 'XXXXX'. If this failure continues, try increasing the query timeout for this process, or try reducing the retention period. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write.

2013-04-24 11:09:13.664 OLE DB Distributor 'FULTON-LON1-C': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}

2013-04-24 11:09:13.742 Percent Complete: 0

2013-04-24 11:09:13.742 Category:NULL

Source: Merge Replication Provider

Number: -2147199466

Message: The merge process could not perform retention-based metadata cleanup in database 'XXXX'. If this failure continues, try increasing the query timeout for this process, or try reducing the retention period. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write.

Viewing the synchronisation history in replication monitor for the failed synchronisations shows the following:

Error messages:

The merge process could not perform retention-based metadata cleanup in database 'XXXX'. If this failure continues, try increasing the query timeout for this process, or try reducing the retention period. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199466)

Get help: http://help/MSSQL_REPL-2147199466

Violation of UNIQUE KEY constraint 'UQ__#oldgens__DCDFEE736CD828CA'. Cannot insert duplicate key in object 'dbo.#oldgens'. (Source: MSSQLServer, Error number: 2627)

Get help: http://help/2627

↧

Transactional Replication from Publisher=SQL2008R2 (DB running in 80 Compatibility Mode) - To Subscriber=SQL2012 ?

April 24, 2013, 11:07 am

≫ Next: Replication issue

≪ Previous: SQL Server 2008 Merge Replication: Metadata Cleanup Failure

Is this possible?

We are deciding which SQL version to use for a new subscriber. We would like to use 2012, but I wonder how it would handle the published DB being in 80 (SQL2000) compatibility mode.

TIA.

↧

Replication issue

April 24, 2013, 9:53 am

≫ Next: Failed Rows on Synchronization

≪ Previous: Transactional Replication from Publisher=SQL2008R2 (DB running in 80 Compatibility Mode) - To Subscriber=SQL2012 ?

Hi All,

i have 2 sites,

here i configure the transitional replication site A to site B

site A is publication and distribution,

site B is subscription only.

here problem is in site B database is created but articles are not created.

note:we check the subscription properties showing below error message

THE PROCESS COULD NOT CONNECT TO DISTRIBUTOR..

Regards,

Chandu

↧

Failed Rows on Synchronization

April 25, 2013, 9:09 am

≫ Next: SQL 2008 - Can not execute as the database principle

≪ Previous: Replication issue

I have a subscriber that wasn't synchronizing for a few days due to a timeout (and the agent never seemed to retry again it just said that a progress message hadn't been logged...and was errored out). So I restarted the agent and the sync seemed to work but now its continously saying that its retrying several rows where most if not all fail. My subscription is set to continuous sync and it just seems to be going through a continuous loop where it's retrying rows and almost all rows fail. Usually when all changed get synced up it will say waiting 60 seconds before polling for changes...but i cant ever seem to get to that state. Of course the subscriber is making data changes on their end so i may not get to that point but i am worried that i keep seeing all these failed rows being retried and they all fail. Any ideas whats going on?

↧

SQL 2008 - Can not execute as the database principle

May 13, 2009, 8:19 am

≫ Next: Performance Hit in Production on CDC Latency

≪ Previous: Failed Rows on Synchronization

When I try to drop publication created in 2008 I get a message "Can not execute as the database principle becasue the principle dbo does not exist, this type of principle can not be impersonated".

The dbo does exist in the publisher db and I am sysadmin on the box. What could be the problem?

This is what I am trying

exec

sp_droppublication@publication =N'HLA_ST'

Msg 15517, Level 16, State 1, Procedure sp_replcmds, Line 1

Cannot execute as the database principal because the principal "dbo" does not exist, this type of principal cannot be impersonated, or you do not have permission.

↧

Performance Hit in Production on CDC Latency

April 25, 2013, 10:54 pm

≫ Next: Merge replication uploading on first sync, WHY?

≪ Previous: SQL 2008 - Can not execute as the database principle

Hi All,

We have a major Production Performance Hit on CDC Latency.

CDC latency : 48 hours. (2 days ago was almost real time: )

log file size: 300 GB

DB Size: 1.5 TB

VLF Count: 5209

SAN type: VMAX(Filber Channel)

As of now. the CDC_Commit_Time has hardly any movement. We ar ekinda stuck. If I Kill the SPID now, the Open Tran will take atleast 30 - 45 to roll back.

MaxTrans was 500 till this morning. I Bumped it to. 5000.

MaxScans was 10 till this morning. I bumped it to 100.

How can i get out of it. Please suggest me. We are kinda stuck in a quick sand.

↧

Merge replication uploading on first sync, WHY?

April 25, 2013, 7:21 am

≫ Next: System can't find the file spacified

≪ Previous: Performance Hit in Production on CDC Latency

Hi guys

(SQL 2005 - SQL 2012)

I have 1 Publisher with 40 subscribers running merge replication. I am creating new servers hence new subscribers.
I create a snapshot of the publication DB with the agent. I take one of the 40 subscriber DBs, sync it a couple of time to make sure its up to date with the PUB. I then make a bakup of the subscriber DB. restore that to new server. I remove the bcp files relating to data in the snapshot that I created, then copy this snapshot files to new server. create new subscription on new server, i do not initialize it, i point it to the snapshot folder that i copied before. when i start the syncing, the new server should obviously start downloading all the changes that it missed in this time i am doing all this, as it did with most of the other ones i did so far. instead it started to upload thousands of records to the publisher, which in turn had to sync to all the other subscribers. how/where can i start investigating this? Why is it uploading? Any ideas?

Thanks

↧

System can't find the file spacified

April 25, 2013, 11:30 pm

≫ Next: How many vCPU capacity of SQL Server 2008 R2 Standard Edition in VMWare environment?

≪ Previous: Merge replication uploading on first sync, WHY?

I am working on creating peer-to-peer replication testing.

I have created Peer publication from DEV-> DBTEST.

All log reader agent job working to be fine on DEV but it give me error on DBTEST as follow.

Any help should be greatly appreciated. Please let me know if more information is required.

Executed as user: sqlservices. Replication-Replication Transaction-Log Reader Subsystem: agent DBTEST-Test_PeerReplication-8 failed. The system cannot find the file specified. The step failed. [SQLSTATE 42000] (Error 14151). The step failed.

↧