I have a transactional replication with 4 articles but when I add a new article to it , I have to reinitialize the subscription to make it work,and after that I see the status of snapshot agent , it shows everything is ok, but the table in the subscriber side become empty !!!! why? and what should i do? it's so dangerous for me!! thank u all
delete one side table in replication when reinitialize subscriber
SQL 2012 Web Synchronization on Server 2008R2 x64
I can't get the IIS portion of web synchronization to work. I keep receiving 500 server errors when i try to go to the test page https://server.XXXX.com/directory/replisapi.dll?diag
I have followed the instructions on http://technet.microsoft.com/en-us/library/ff714039.aspx
The SQL server is the same machine that has IIS installed.
Has anyone else had success getting this to work?
Version info:
SQL 2012 Standard 64 bit. 11.0.3128.0
Server 2008 R2 Standard 64 bit.
Default IIS Installation.
Which Hosting Suits Replication
SQL Server Transacational Replication Issue while adding a new article
I have a "PULL" transaction replication toplogy (SQL server 2008 R2 - publisher,subscriber & distributor) in place and is working fie. I added a new article (table) using sp_addarticle and it works fine. Then I tried to add subscription to the new article using sp_adddsubscrition SPROC from the publisher (details below)
EXEC sp_addsubscription @publication = @pub_name, @article = @article_name, @subscriber = @sub_server, @destination_db = @sub_dbname, @subscription_type = N'pull',@update_mode = N'read only', @sync_type = 'sutomatic', @status = 'active', @reserved ='Internal'
I tried with all combination of values in the @sync_type parametr,
The above command fails with the following message:Msg 14100, Level 16, State 1, Procedure sp_MSrepl_addsubscription, Line 533;Specify all articles when subscribing to a publication using concurrent snapshot processing.
The sync_type value parameter is "replication support type" when the subscrition was added orginally to the publication. This trsnslates into a value of 3 (CONCURRENT) in sync_method column on the outpout of sp_helppublication SP execution.
What am I doing wrong? Please advise. Your help is much appreciated.
Thanks in advance
Kirti
Correct Way to Stop Replication While Applying Service Packs to 2008 R2
I am new to this so be gentle...
Running SQL Server 2008 R2 on both servers.
Server A >> running Transaction Replication to Server B.
Server A acting as Publisher and Distributor. Server B is Subscriber of Transaction Replication.
Server B >> running 3 Merge Replication Jobs to Server A.
Server B acting as Publisher and Distributor. Server A is Subscriber of the 3 Merge Replication Jobs.
------
These servers are both basically still sitting at RTM and haven't had any Service Packs applied. We are having memory leak problems with replication and they must both be updated to the latest Service Pack and CU.
Given this scenario, I need to know specifically how to stop replication on both servers so I can apply the Service Packs and updates. Other than the usual backup system and application databases prior to applying service pack and update, is there
anything else I should do? I know how to set replication up for our specific application, but I am a complete newb at stopping replication. Previously, we just stopped and deleted Subs, then pubs, did our business, then rebuilt the replication.
I know that is not the best way to accomplish our goal, and this seems as good a time as any to learn the correct way of making this happen.
I am getting below error when trying to set the peer top peer replication
TITLE: New Publication Wizard
------------------------------
SQL Server could not create publication 'pub_default'.
------------------------------
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
------------------------------
Could not find stored procedure ''.
Changed database context to 'AdventureWorks2008R2'.
Warning: The "immediate_sync" property for publication "pub_default" has been changed to "true" because it is required by Peer-To-Peer.
Warning: The "allow_initialize_from_backup" property for publication "pub_default" has been changed to "true" because it is required by Peer-To-Peer. (Microsoft SQL Server, Error: 2812)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=11.00.2100&EvtSrc=MSSQLServer&EvtID=2812&LinkId=20476
------------------------------
BUTTONS:
OK
------------------------------
Thanks
get the list of all Tables, Views, Stored procedures that are NOT added in a publication for replication
SQL Replication disappears
I recently had to restore a database in SQL2008R2 that was Replicated. Here are the steps taken:
* Backup database A (which is replicated).
* Restore to database B.
* Scripts run on database B.
* Backup database B.
* Restore to database A
Apparently (I'm not convinced), the result of this is that the Replication jobs in SQL management studio have vanished.
Would anyone know if this is likely.
PJ.
How can I replicate 1 table into 2?
I wish to replicate one table into two destination tables. Like cols 1-30 into table 1, cols 1, 31-50 into table 2. How can I accomplish this? Perhaps using views?
Problem with SQL replication
Hi,
I have sql 2008 merge replication to work between 2 Windows Servers running SQL 2008
in a non Active Directory/Domain environment over VPN perfectly :)
But now I want to make replication between one server that is on workgroup NON Active Directory/Domain environment and another that is IN Active Directory/Domain environment.
Setup is exact as the replication that is working perfectly, but in this environment I get error:
The process could not connect to Subscriber 'SERVER\SQLEXPRESS'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20084
SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. (Source: MSSQLServer, Error number: -1)
Thanks,
WebSyncDiagAccess
Am trying to get replication going over https.
Have set up iis and everything seems to be ok but when I navigate to https://server/folder/replisapi.dll?diag I get the following text in the browser.
Access Denied because of no WebSyncDiagAccess.
The account I am using has read and execute permissions on replisapi.dll, I have checked everything I can think of and have searched and searched but can not find any reference to "Access Denied because of no WebSyncDiagAccess." anywhere.
Anyone have any ideas?
Thanks,
Denton
question about replicate indexed view as table
how to start and stop distribution agent in sql server 2008 r2
can some one help me hoe to start and stop distribution agent in sql server with out using TSQL commands ?
Answer will be helpfull... Thanks in advance.
Web replication issue on SQL Server 2008 R2
Hello,
I've setup SQL merge replication over HTTPS on SQL Server 2008 R2. Both servers (the publicator and the subscriber) are running SQL Server 2008 R2 SP1 on Windows Server 2008 R2.
From the subscriber, I can access to the url https://replication.xxx.com/mybase/replisapi.dll?diag without any errors nor warnings (SSL certificate OK). But, on the subscriber host I get a error during the replicationwhen the user used by the replication (AgentAccount) is not logged on the machine.
The error is :
2012-05-09 12:48:41.642 Category:NULL Source: Merge Process Number: -2147221502 Message: The system cannot find the file specified. 2012-05-09 12:48:41.643 Category:NULL Source: Merge Process Number: -2147199373 Message: The Merge Agent failed to connect to the Internet proxy server for user 'AgentAccount' during Web synchronization. Ensure that the proxy server settings are correctly configured in Internet Explorer, or specify the -InternetProxyServer parameter when starting the Merge Agent. 2012-05-09 12:48:41.643 Category:NULL Source: Merge Process(Web Sync Client) Number: -2147024896 Message: The Merge Agent could not connect to the URL 'https://replications.xxx.biz/mybase/replisapi.dll' during Web synchronization. Please verify that the URL, Internet login credentials and proxy server settings are correct and that the Web server is reachable.
When a session is oppened with the user AgentAccount I don't get any errors and the replication is OK. But as soon as I close the session, I get these errors again.
Could anyone help me to fix this issue ? Thank's
Could not delete publication?
I got the following error message when deleting a publication. The user 'Domian\deletedUser' is deleted from AD by IT. Although the deleted user originally created the database DB1. The publication is created by me and the SQL Agent is running using another active domain user.
Is there any way to delete the publication?
Could not obtain information about Windows NT group/user 'Domian\deletedUser', error code 0x534.
Changed database context to 'DB1'. (Microsoft SQL Server, Error: 15404)
Error message:
Msg 15404, Level 16, State 11, Proceduresp_replcmds, Line 1
Could not obtain information about Windows NT group/user 'Domain\deletedUser', error code 0x534.
Merge replication : Give indication on client to inform data is uploaded to publisher
Hi,
we use merge replication to synchronize sales data. The publisher/distributor is a SQL2012 standard edition, the subscribers are SQL2012 express editions. We are using pull subscriptions.
Orders are created on the clients and are initiated with a status 'No upload to publisher'.
The salesperson can check the orders for upload in his application which gives the orders the status 'Upload to publisher'.
The merge process synchronises the order records (ignoring the status).
So the status is more a functional setting, no influence on the merge process.
We tried to make a trigger on the order table on the publisher which fires on insert and for the records with status 'Upload to publisher' we change the status to 'uploaded to publisher' (these records cannot be changed anymore on the subscriber, this is checked
in the application).
We already set this trigger to fire first and last (before or after the merge triggers).
Sometimes this works ok, sometimes it does not, resulting in a failed data validation (rowcount and checksum), in which case the rowcount is correct, but the checksum is not.
Is there a way to make this reliable ? (I would not like to change the validation to rowcount only.)
How to query latency with HistoryVerbose 0
We're using Transactional Replication in SQL 2008R2 SP2
I'm trying to evaluate whether using a HistoryVerbose setting of 0 on the Log Reader and Distribution agents is a worthwhile modification to make, but still need to know Latency in these agents at periods of time.
I know it's possible to use Windows Performance Monitor and enable a couple of replication counters but I have reason to want to do this in T-SQL.
Tracer Tokens don't give you the answer until the token has finished replicating - it tells you about the problem AFTER the problem's happened.
It's also possible to get Current Latency from the MSDistribution_History and MSLogReader_History tables, but this information isn't recorded when the HistoryVerbose setting is 0.
It's possible to calculate what the latency is going to be based on the agent's transactions per second and the number of pending transactions, but querying these values can be costly on the Distribution database.
So there may not be an answer to this other than Windows Performance Monitor, but has anyone managed to query Latency in a light-weight query which isn't reliant on the logging in MSDistribution_History and MSLogReader_History?
Thank you if anyone can help!
Tim Johnstone Senior Technical Consultant Computacenter (UK) Ltd
Transactional replication issues
SQL 2012 for both servers.
Basically I would like to set up a (transactional I think) replication of few articles from serverA to serverB.
I created publication and I created subscription (push) related to serverB.
In the past, on a sql 2005 instance I used distrib.exe on publication server to deliver changes on subscriber and it worked well.
On sql 2012, running distrib.exe does not deliver anything .. and I don't understand why.
Please remember that my main goal is to deliver changes in articles from serverA to serverB "on demand".
Can you please help ?
Any help appreciated, best regards.
Dealing with frequent disconnected states (replication) - advice needed
Hello,
We have a very complex environment and I was wondering if anyone out there in the SQL community had ever dealt with, or had ideas on how to deal with, this unique sort of environment. We support two "homegrown" SQL Database applications over a geographically dispersed area. The remote locations are currently connected via T1s. But, it doesn't end there... At the remote locations, there are vehicles that are often disconnected for, sometimes, months at a time, where folks on those vehicles are entering and accessing data from the applications. We currently use SQL 2008 Merge replication, and, it works... but, it, lately, has had some issues. But, it DOES work... It just doesn't feel like the ideal solution. The way we have it now, our main SQL DB is in our main datacenter... then, at each remote location, there is another SQL server that houses a copy of the database using SQL merge replication. Then, on each vehicle, we have servers that have everything on them (they are domain controllers, SQL servers and web application servers) and, also on the vehicle is a laptop set up to access the application from that server over wireless. When the server on the vehicle can see the domain and the DB server at the remote location, merge replication handles synching those two.
Does anyone have a better solution to this? I guess an example of our situation would be something like if NASA wanted to use our applications and they needed to be able to continue using the application even if they did not have internet or any, for that matter, connectivity.
Thank you in advance for any advice/ideas.
Charlie
Replication-@rowcount_only parameter must be the value 0,1, or 2
SQL 2008 R2
I'm replicating from Server A to Server B using transactional replication. I have 3 publications on Server A, with 3 subscriptions to Server B. 2 are working fine. One keeps giving me errors. The latest error is:
Replication-@rowcount_only parameter must be the value 0,1, or 2
I also have this one in the error log:
Replication-Replication Transaction-Log Reader Subsystem: agent ServerA-2 scheduled for retry. The process could not execute 'sp_replcmds' on 'ServerA'.
I've researched this and have found a few links that offer suggestions. What confuses me is that 2 publications/subscriptions work fine. Any suggestions on why 1 is not working - and what I should do to fix it?
Thanks in advance,
Andre
André