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

Security issue in SQL Server replication in SQL 2008 Express edition

$
0
0

Hi,

I am trying to do merge replication through web sync in SQL server 2008 express edition. i tried the merge replication using RMO with C# code but no luck. i am getting the security related error.

my Publisher and distribution are on SQL server 2008 R2 Standard edition. machine name "Printserver",
I created subscription on SQL server 2008 express edition.

I hosted the web service for merge syncronization on another machine named "ANUJVMWIN7".

I installed SSL cerificate on all the machine (server, hosted server and subscriber machine.)

here is the error description.

The upload message to be sent to Publisher ‘PRINTSERVER’ is being generated
The merge process is using Exchange ID ’0B23EBE2-D502-4D92-A9A1-88B8F738CFFC’ for this web synchronization session.
A security error occurred

A security error occurred

The Merge Agent could not connect to the URL ‘https://ANUJVMWIN7.prospecta.in/WebSyncTest/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.

The same process i tested with the SQL server 2008 standard edition and all the things are working fine. i could able to merge the databases but no luck with SQL 2008 express edition.

Please help.

Thanks
Anuj Sharma


Thanks Anuj Sharma Software Engineer


Change snapshot location for subscription

$
0
0
Hi,

  I had published a database and there are many subscriber to it. All these days it was working fine. Recently I created subscriber, the subscription is downloading data from old snapshot instead of new one. I deleted old snapshot, created new one and the subscribed again. But again the subscription pointing to old snapshot though the snapshot folder does not exists. 

I checked the location for snapshot which is pointing to correct folder. Ex: The snapshot is pointing to

\\myserver\c$\sqldata\mssql\replicationData\ftp\MyDatabase_replcopy

when I looked into the above location it has folder with name "20140130121212"

When I tried subscribing newly it starts extracting the files but at some point it stops with the error

The schema script '\\myserver\c$\sqldata\mssql\replicationData\ftp\MyDatabase_replcopy\20131112500602\Test_Storedproc_1203.sch' could not be propagated to the subscriber.

The snapshot folder does not contains folder like "20131112500602".

Dont know from where it is taking. 

One more thing is its happening for only new subscribers and already existing subscribers does not have any issues.

Any idea how can I resolve it with out dropping existing subscribers or republishing the database?

Thanks in advance,
Pavan

Pavan

Login privilege to access subscription DB tables got change once subscription been created.

$
0
0

we  have 2 servers namely (Server1) and (server2) with 2 logins (login1, login2) apart from sa account respectively in each server.

Server1 is the publisher.

Server2 is the subscriber.

Replication Type: Merge replication

subscription type: PUSH.

Issue:

In server1 and sever2 we have 50 tables in a database DB1.

Among 50tables login1 have privilege (Select, alter, delete, insert) to access 40 tables and

login2 have privilege (Select, alter, delete, insert) to access 30 tables.

Before replication setup login 1 and login 2 have access privileges to respective tables.

After replication setup

step1: Publisher setup - No issues till here

Step2: Subscription setup

used sp_addmergesubscription and sp_addmergepushsubscription_agent SP's

After completing the step2 the privileges in Server2(subscriber) forlogin1 and login2 got messed up they can access only few ( namely 5) tables which is not in article list.  and no issues with privileges inserver 1(publisher) for that same login.

login1 and login2 owns Public server roles not system admin.

can anybody say why the table access privileges only in Server2(subscriber) forlogin1 and login2 got changed.







Transactional Replication - Creating Snapshot after adding a new table

$
0
0

Hello,

 

Sorry for my English..

 

Could you tell me if it is possible not to create entire snapshot after adding a new table? Our database is very big and it takes a lot of time to make snapshot.

 

Also could someone tell me exactly how works blocking of tables while creating snapshot?

I've read in BOL that if Snapshot Replication is used then all tables are blocked while creating snapshot for replication. And if Transactional Replication is used, snapshot is created in parallel mode and tables are not blocked and users can work with them. I understand that in second case each table is blocked while it is processing and after processing it is unblocked and next table is blocked. Is it so?

 

Also I am interested how actually tables are blocked? For SELECT/UPDATE/INSERT or how? Where can I read information about it?

 

Thanks,

Vitaliy

 

replication from two publisher into one database (Transactional Replication)

$
0
0
Hi! I have a specific problem that I have not found a solution
i have two source database with same schema:

server1.database1..table1(id,databaseid,name,description)
server1.database1..table2(id,databaseid,sometext,somevalue)
server1.database1..table3(id,databaseid,blah,blahblah,onemoreblah)
...

server2.database2..table1(id,databaseid,name,description)
server2.database2..table2(id,databaseid,sometext,somevalue)
server2.database2..table3(id,databaseid,blah,blahblah,onemoreblah)
...

and one destination database with same schema:
server3.database3..table1(id,databaseid,name,description)
server3.database3..table2(id,databaseid,sometext,somevalue)
server3.database3..table3(id,databaseid,blah,blahblah,onemoreblah)
...

(id,databaseid) is Composite Primary Key.

server1.database1 is very large database with over 1000 transaction in minute, and it is replicated to server3.database3 with Transactional Replication (database1 is publisher, database3 si subscriber).

Server2.database2 is large, but much smaller then database1 and It is updated weekly.

My question is how to update server3.database3 with data from server2.database2, without negative impact on the replication (transactional replication where server1 is publisher and server3 is subscriber) ? 

Can i just update data in server3.database3 from server2.database2? 
How transactional replication will react to the rows, which are exist in the subscriber (server3), but does not exist in a publisher(server1)?

Thank you!!!

I am getting below error when trying to set the peer top peer replication

$
0
0

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

conflicts on a single table

$
0
0

I am having a conflict issue on just one table out of 37 table articles

The database is for Food recipes I have 3 users making changes, they each have their own menus so they should not work on anyone else's dishes [tblRecipe] but they do need to be able to copy and view other users dishes.
Each dish is in a menu and a dish type and has 2 child tables one for ingredients and one to methods

The problem: is in [tblRecipe]
When a user makes changes to one of their dishes and synchronises a conflict is thrown, even when no one else has synchronised, they will also get conflicts for other users dish changes even though they have not made any changes to the other users dishes.
It trust my users when they say they have not changed other users data

The database is sqlserver 2005 it is merge replication
the publisher is set to win
37 table articles mostly bidirectional
there is no row filtering
I have scripted the publication and as far as I can see all bidirectional articles have the same properties.

I would be gratefull if someone can give me some pointers to a solution or some things I can try


jnc

Sink Two Databases

$
0
0

Hi

I want to Know How can i update database located remotely on Go-daddy's Server whenever I update or delete record on my local sever database(on laptop) Efficiently.

Do I have to Use Triggers or is there More Efficiently Way in C# that Updates Go-daddy's server automatically whenever I make changes to my local Database or on timely basses

Thanks..


locks in replication

$
0
0

Hi,

What locks does snapshot replication, transactional replication, merge replication holds.

How to identify the date when database is published?

$
0
0

Hi,

  Is there any way to find when the database is published (i mean date). One of the database on our server is created long back and dont have record when it is published.

Thanks in advance,

Pavan

  


Pavan

Merge Replication with FTP (Pull)

$
0
0

Hello,

I'm currently testing Merge replicaiton.

I need to have at least one Subscriber wich do not have TCP/IP port open for it's SQL Server Instance.

I have configured my Publisher to deploy snaphot in a ftp. But my Pull Subscriber can't get the initial snapshot (with the DB schema).

On the Publisher Replication Monitor I have these error:

Error messages:

The schema script '' could not be propagated to the subscriber.

(Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)

Get help: http://help/MSSQL_REPL-2147201001

The process could not connect to FTP site 'ftp.XXXX.XX' using port 21.

(Source: MSSQL_REPL, Error number: MSSQL_REPL20032)

Get help: http://help/MSSQL_REPL20032

220 Microsoft FTP Service

550 No such host is known.  

(Source: MSSQL_REPL, Error number: MSSQL_REPL12003)

Get help: http://help/MSSQL_REPL12003


I can't see where the error is

(I have configure an other Subscriber (in Push) with port open which work perfectly)

Thanks for you help


Moving published database from SQL 2005 Std. version to SQL 2012 Std.

$
0
0

Hello, 

I have  a published database 'foo' in production on SQL Server 2005 Standard. It serves 2 subscribers which use SQL Express version for subscription.

Now I want to detach that database 'foo' from old server and attach to new SQL Server 2012 Standard.

Can I shift my old database to new server as it is? I know that I won't be able to detach database if its publishing...

but if I drop articles from current publication,

Can I keep my old  replication settings intact while moving to new server?

Will I have to create new publisher and subscribers? 



Dipesh Pachlegaonkar

Does adding a second subscriber to an existing publication require a resyncronization?

$
0
0
The publication has been around with a single subscriber for quite some time. Was curious whether or not adding a second subscriber would require a resync of the already existing subscriber?

John M. Couch

Is it possible to converting Snapshot replication to Transactional replication

$
0
0

Hi All,

Is it possible to convert the existing snapshot replication to transactional replication?

Thanks in advance,

Maximum stored procedure, function, trigger, or view nesting level exceeded (limit 32).

$
0
0

Hi All,

I have transactional replication with up-datable subscriber. When i try to update the data from Publisher side i am getting below error. in the same way when i update from subscriber side, it is updating fine. There is no problem with select statement the problem is happening in updating the data. And i am able to update the tables which are not participating in replication

Msg 217, Level 16, State 1, Procedure uDocument, Line 7
Maximum stored procedure, function, trigger, or view nesting level exceeded (limit 32).

Kindly help.

Thanks in  Advance

Regards

Khushi



How would I know which node was initially setup in peer to peer replication.

$
0
0

How would I know which node was initially setup in peer to peer replication.


Thanks

ignore column value in merger replication 2005

$
0
0

I Have a column in one table which causes conflicts because it is the 'updated' date of the row and all users update this column while they are using the system.

I do not want to exclude the column and would still like it to be synchronised

 I just need the value to be ignored during sync.


jnc

merge Web Synchonization in Windows server 2012 fail with Faulting application w3wp.exe Faulting module name replrec.dll

$
0
0

 Hi Folks.

   I have a product that synchronize data from a SQL server compact database to a SQL server 2012 database, the same application is running in other version of windows server and SQL server  without any problem but is crashing in windows server 2012 with SQL server 2012.

 If there any other patch I need to apply to make it work.

This is the error :Faulting application name w2wp.exe, version 8.0.9200.16384

Faulting module name : replrec.dll, version. 2011.110.3000.0

Exception Code : 0x0000000000059eff

 

 Thanks.


Install SQL Server 2008 R2 SP2

$
0
0

Hi

Actually, we 've plateforme with SQL server entreprise SP1 with merge replication, we must passe to SP2, quicky....

Anyone, can advice me on the method, the test, and problems encountered on this install.

we've 3000 subscribers, you canno't make mistakes !!

Thanks a lot

Migrating SQL Server Published databases with minimal downtime

$
0
0

All,

 I have a requirement in which databases in Server A has to be mirated to Server B. Server A has two databases in Merge replication and one with Transactional replication. Server A act as the distributor itself.

My question is how can I migrate all these production databases which are also publishers to new sever B with minimal downtime, and with out breaking replication.

I read that if the Server B is renamed as Server A then replication will continue with out any errors.Please suggest how to migrate the publisher to Server B with minimal downtime.

Also I would like to know if the replication is Server A->Server C->Server D, then if I can migrate Server A to Server B with out dropping replication, will it affect the replication setup from Server C to Server D. Does it cause any replication errors.

Thanks in advance!

Viewing all 4054 articles
Browse latest View live


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