Hi All,
I replicated couple of table from oracle server to SQL server using sql transactional Replication and found out that the Table size got increased i.e in oracle the table size was 300MB while in Sql server its 475MB but both has equal number of rows.
Kindly let me know if its normal?
Thanks,
TITLE: Replication Monitor
Replication Monitor could not reinitialize one or more subscriptions that support automatic initialization.
Cannot reinitialize the article 'all' in subscription 'anonymous_server:anonymous_db' to publication 'Pub'. The publication is enabled for peer-to-peer transactional replication, which does not allow subscriptions to be reinitialized with a snapshot. Drop and re-create the subscription instead.
Changed database context to 'AdventureWorks2012'. (Microsoft SQL Server, Error: 20800)
Thanks
Hi Guys,
Just encountering a issue when using backup&restore to initialize a subscription where the publisher table contains identity column (and configured as "Not for replication"). As you known, after restoring the backup on the subscriber side, the identity property will be left. Under this situation, SQL Server tries to create the "sp_MSupd" stored procedure which tries to update this column. Did you try to initialize a subscription with backup&restore method, and the publisher table contains an identity column as primary key? If so, can you share your solution?
彼节者有间，而刀刃者无厚；以无厚入有间，恢恢乎其于游刃必有余地矣！
Hi
when i try to delete publication i am getting following long error message.
invalid object name mspub identity range - error 208.
by mistake i deleted some table from my database. and so now i cannot delete publication.
pls help.
Hi I'm unable to script out a publication when I try script out I get this error
Unable to script out a publication. Getting error Msg 18456, Level 14, State 1, Line 1 Login failed for user 'distributor_admin'.
When I tried to see the publisher properties I get this error "The administrative link password required to connect to the distributor has been changed. Enter the new password in the following form"
We are using remote distributor. Any idea why I get this error?
Thanks
SK
Hi there,
I know its a tough question asking but some one might have got one best practice or best way of doing it, so presenting here....
We do have transaction replication( one way) , replication did not work quite some back and reconfigured again. But few tables are having data sync issues.
To have the data sync between pub and subscriber tables, T-sql script will do the task for me? If any one has one please copy me?
regards,
i have a view which is also the part of replication ,
if i alter the view would that change replicate over to the other side?
Regards
k
Hi
i am getting following error with snap shot agent.
The replication agent failed to create the directory '\\192.168.2.4\sdb\snap\unc\WIN-EUK75GDCGAQ_SANKETUNIVERSAL_TEST2\20140307155950\'.
Access to that path is open. No security is set on that folder. If i go to run and type " '\\192.168.2.4\sdb\snap" it opens up the folder and can create delete modify files under this folder from any pc in network.
So any one can access it without permission. BUT still snap shot agent fail to run and give above error. It says" The replication agent failed to create the directory '\\192.168.2.4\sdb\snap\unc\WIN-EUK75GDCGAQ_SANKETUNIVERSAL_TEST2\20140307155950\'.
Folder is shared USB drive on NAS having no security.
Hi.
i am getting following error.
The Queue Reader Agent has encountered the error ''Login failed for user ''NT AUTHORITY\ANONYMOUS LOGON''.'' when connecting to ''db2' on ''pc2\VMSQL'. Ensure that the publication and subscription are defined properly and that both servers are
I have set Transnational Replication with updatable subscription.
please help
I have multiple (remote) databases to aggregate into a single back office database.
The obvious scenario is to use merge replication in push mode (security rules on the remote dbs prevent the faster pull mode from being used).
However, our WAN connections are terribly flaky, with high latency and packet loss, sometimes going offline for days.
I have a *feeling* that transactional replication from the remote dbs to the back office would be a better option but cannot quantify why it may be the better option, especially considering the Agent Profile options are largely similar.
So I have been trying to setup a proof of concept for each scenario:
1) Remote merge/push into the back office - Done.
2) Remote transactional/push into a proxy database at the back office site, then merge/pull the proxys into the back office db - can't seem to get this one working. Each hop will work in isolation. The initial snapshot for the merge of the proxy to the back office works but it never updates. The proxy receives the updates but they never propagate to the back office db.
3) Remote merge/push to a proxy, merge/pull all the proxies. Cannot setup the second hop as the wizard tells me it's not allowed :-/ However there are posts here that say this *is* possible :-/
The replicated data is a simple push of non-overlapping data where the data is not altered in the back office (although it is set to allow alterations at the subscriber or the second subscription kills the replication completely with a trigger).
So the questions I am asking are:
a) Does transactional replication have any advantages over merge replication over the flaky WAN?
b) How do I get the proxy database to participate as both a subscriber and a publisher?
Thanks in advance.
Running SQL Server 2005 SP2. Transactional replication with no updating subscriber. Push to subscriber.
What I am trying to do is implement partition switching on a replicated table. My process looks like:
BEGINTRAN
EXECsp_dropsubscription@publication ='PUBLICATION_LogTest',
@article ='testlog', @subscriber =N'all', @destination_db =N'all'
EXECsp_droparticle@publication ='PUBLICATION_LogTest',
@article ='testlog', @force_invalidate_snapshot = 1
ALTERTABLE testlog switch PARTITION 2 TO Testlog_delete PARTITION 2
EXECsp_addarticle@publication ='PUBLICATION_LogTest',
@article = 'testlog', @source_owner =N'dbo', @source_object = 'testlog',
@type =N'logbased', @pre_creation_cmd =N'none', @schema_option = 0,
@destination_table = 'testlog', @destination_owner =N'dbo'
@force_invalidate_snapshot = 1
COMMIT
EXECsp_startpublication_snapshot@publication ='PUBLICATION_LogTest'
(testlog_delete is not replicated)
When I try to alter the table, I get an error message:
ALTER TABLE SWITCH statement failed because the table 'sand.dbo.testlog' is marked for replication.
If I look in sys.tables after the DROP subscription/article, I see the the has_replication_filter bit = 1 (the is_published = 0, and is_replicated = 0).
Note that none of the tables are filtered vertically or horizontally.
If I start SQL Server in single user mode and use DAC, I can reset the has_replication_filtered bit = (0) with:
EXEC sp_MSsetfilteredstatus <ObjectId>
Then I can do the partition switch.
...but this stored proc is unavailable outside of DAC.
So three questions:
(1) Why causes the has_replication_filter bit to get set to 1 (it is happening on some of my tables, but not all of them)
(2) How can reset this bit outside of DAC
(3) Is there a better way (outside of upgrading to SQL Server 2008) to manage partition switching on a replicated table?
We are currently using merge replication in the following scenario. There is a central SQL2008r2 server that acts as the publisher and distributer. Clients running SQL Express create their individual subscriptions using RMO over VPN.
The snapshot folder is on a UNC share and "Everyone" has full access to the folder.
Occasionally we experience some users unable to access the folder and receive OS 5 error. I think this may be caused by user credentials being out of sync with the domain controller.
When SQL Express on the client attempts to access the snapshot folder, I believe it uses the windows credentials of the logged in user.
Is it possible to specify a generic domain account for SQL Express merge agent to use to connect to the snapshot folder?
Thanks,
--Shane
Hi All,
we are currently using a SQL server 2008 R2, and we have 2 instances of SQL server for 2 different Application in a single server.
For one of the Application, we a Merge replication setup with Sql Server Compact(PDA).
Now we are planning to Move the environments from one DataCenter to another DataCenter.
As the Server is Quite large, the Physical movement of the server is not possible so we had tried to Backup all the database and restore it to a new server.
Please let me know the steps to be followed, in this scenario where i can avoid subscribers re setup in the SQL server Compact(PDAs).
Joji
Hello All,
I am in the process of trying to copying over data from source sql server table to destination sql server table. The requirements being, only the new or updated data needs to be migrated to destination table, once a week. Our source table has 23 million rows and growing.
I researched two different solutions and would like to know if anyone has feedback on these.
1. Merge - used to sync data between source and destination table using SSIS packahe. But the problem for this according to my research, with the amount of data in consideration, the transactional log will grow by leaps and bounds. Not the way.
2. Replication - I have started my research in this matter. Would this be an ideal solution?
Many thanks.
Please help me..
After configuring Transactional Replication with a publisher, distributor , subscriber and with one database and one table . and in subscriber the database in read write mode. so, we can perform changes . Here my question is....
we performed some changes in table (other than primary key column) in subscriber db.
Then both db's have different vales ( publisher db and subscriber db). how will face this scenario?
Hi All,
This weekend we have migrated one of our Core system from SQL Server 2005 SP3 to SQL Server 2008 R2 SP2. Migration went successful. However when we are trying to Configure transaction replication we are getting below Error:
Msg 21854, Level 16, State 1, Procedure sp_MSrepl_addarticle, Line 573
Could not add new article to publication 'abc' because of active schema change activities or a snapshot is being generated.
Background:
Database compability Changed from 90 to 100.
A quick Help would be appreciated.
Best Regards - Viral
Thanks - Viral
Hello,
I have setup transactional replication between Server1 (SQL Server 2012 on windows 2012) and Server2 (SQL Server 2005 on windows 2003 SP2). The replication is push and distributor is on publisher ie Server1.
The snapsots are generated but they can't apply to the subscriber. I get the following error.
'The process could not connect to Subscriber '
Can someone please tell me why I get this error? I have a link server setup between Server1 and Server2. I could connect from SSMS and run query from Server1 to Server2.
What credentials does distributor on Server1 use to connect to subscriber? Am I missing something? How do I troubleshoot this is?
Thanks,
-P
Hi,
I am doing a DR Test where I need to test the mirrored and log shipped secondary database but without stopping the mirroring or log shipping procedures. Is there a way to get the data out of mirrored and log shipped database to another database for update or insert operations?
Database snapshot can be used only for mirrored database but updates cannot be done. Also the secondary database of log shipping cannot used for database snapshot. Any ideas of how this can be implemented?
Thanks,
Preetha
I have a table that i replicated already,
i need to change the column size of that table,
do i have to take any further action to make sure the change is replicated or replication will take care by it self?
Regards
k