Showing posts with label configure. Show all posts
Showing posts with label configure. Show all posts

Wednesday, March 28, 2012

merge replication without rowguid

hi,
I have a database that has Primary Key constraints on every table. Yet
when I run the replication wizard and try to configure merge
replication the wizard notifies me that it will create a rowguid on
the tables even though they already have a primary key.
anybody know how to avoid the rowguid column from being created?
regards,
Doron
what is the big deal with having rowguid column?
I am running the replication for 3 years with that column without any
prolem!
"DoronA" <doronal@.msn.com> wrote in message
news:OMPe$RgwEHA.824@.TK2MSFTNGP11.phx.gbl...
> hi,
> I have a database that has Primary Key constraints on every table. Yet
> when I run the replication wizard and try to configure merge
> replication the wizard notifies me that it will create a rowguid on
> the tables even though they already have a primary key.
> anybody know how to avoid the rowguid column from being created?
> regards,
> Doron
>
|||If your primary key is a unqueidentifier, then you can mark it as the
RowGuid column using ALTER TABLE, e.g.
ALTER TABLE dbo.MyTable
ALTER COLUMN MyPK ADD ROWGUIDCOL
Otherwise, you have to have a separate RowGuid column, as it's how
replication tracks the global identity of rows.
Paul
"DoronA" <doronal@.msn.com> wrote in message
news:OMPe$RgwEHA.824@.TK2MSFTNGP11t .phx.gbl...
> hi,
> I have a database that has Primary Key constraints on every table. Yet
> when I run the replication wizard and try to configure merge
> replication the wizard notifies me that it will create a rowguid on
> the tables even though they already have a primary key.
> anybody know how to avoid the rowguid column from being created?
> regards,
> Doron
>

merge replication without rowguid

hi,
I have a database that has Primary Key constraints on every table. Yet
when I run the replication wizard and try to configure merge
replication the wizard notifies me that it will create a rowguid on
the tables even though they already have a primary key.
anybody know how to avoid the rowguid column from being created?

regards,
Dorondoron_almog@.msn.com (Doron) wrote in message news:<995517bc.0411031605.30cf6318@.posting.google.com>...
> hi,
> I have a database that has Primary Key constraints on every table. Yet
> when I run the replication wizard and try to configure merge
> replication the wizard notifies me that it will create a rowguid on
> the tables even though they already have a primary key.
> anybody know how to avoid the rowguid column from being created?
> regards,
> Doron

Unless all of the replicas are read-only, how would you prevent the
same PK being allocated to two different rows in two different
replicas?

The solution you are being offered is to have rowguid be the primary
key - what's your proposed solution to the problem?

Friday, March 23, 2012

Merge Replication Replicate Master and related tables

hi all,

Could we configure a merge replication such as replicate the master table and its all related tables (relation deep could be 1.)

We dont want to manually find master table relations and configure replication for the related tables.

please help for that configuration

kinds

No but why would you want to?|||No, replication wizard will not find and define all the FK dependencies for you, you have to do this yourself.|||Thanks StatisticsIO.com and Greg Y for your valuable help. |||In repl UI, there is capability to create a dynamic filter on the parent table and then automatically generate the join filters based on PK-FK, do try it out in the publication wizard.sql

Monday, March 19, 2012

Merge replication odd question

Hello,
I need to configure a merge replication between 3 machines, one of these is never connected with the other two machines. I've tried to work with the off-line machine with backup and restore to the offline machine and the others in this way: I backup up a
subscripted DB and restored to the offline machine, update some data and then backup and restore again on the subscripted DB. It breaks the synchronization.
Do you think there is a way to "freeze" a subscribed DB, move it to another off-line machine (moving backups or data and log files, or something else), work on this machine and then restore the updated DB to the freezed one?
And do you think it will work also between a SQL server 2000 publisher and an MSDE subscriber?
Thank you for your help!
Michele
This certainly is an odd request.
I think it might work if you use the keep_replication switch of the restore command while you are restoring your database.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
|||But Hilary, if we RESTORE over the top of one of the two connected databases
the database that was disconnected then we will lose at the very least all
transactions that happened between the two connected databases won't we?
It is almost as though we want to RESTORE to a 3rd DB with KEEP_REPLICATION
and then fire up the Agents.
Not even sure if that will do it.
Allan
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:F1BFFB4C-C330-4BDD-9753-A7787783F03D@.microsoft.com...
> This certainly is an odd request.
> I think it might work if you use the keep_replication switch of the
restore command while you are restoring your database.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
|||OK so here was my testing
Create 3 databases
M1,M2,M3
M1 = Publisher
M2,M3 = Subs
Create a table (I used a very simple table with IDENTITY())
Create an article of the table (Handle Identity ranges)
Add to a publication
Start cooking
--Now remove M3 from the topology so we can put it on the laptop for however
long we want and continue to work on it (watch identity ranges if a long
time)
--stop the merge agent and drop the database
--Restore somewhere else with KEEP_REPLICATION
Must be restored as M3 otherwise you get the following when inputting data
ERROR!!
INITCOLVS: The Parameter 'nickname' is invalid
--Input data
Backup from this box now and restore to the original (WITH KEEP_REPLICATION)
Start up the Merge agent
In it goes.
Allan
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:F1BFFB4C-C330-4BDD-9753-A7787783F03D@.microsoft.com...
> This certainly is an odd request.
> I think it might work if you use the keep_replication switch of the
restore command while you are restoring your database.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
|||I'll try to repro this later.
If you have a subscriber, and you backup that database, and restore it to the 3rd machine using the keep replication switch, make your changes, backup the database and restore it to the second machine, again using keep replication, this should work.
You must have replication installed on the third machine however.
This is a variation of the way you can deploy susbcribers using a backup and restore.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
|||It works!
Thank you very much Hilary and Allan for your precious help!
Michele
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!

Monday, March 12, 2012

Merge replication issue - The subscription to publication is invalid

I am trying to configure a merge replication of publication with 151 table-articles over 128 kbps line via proxy (Win XP, WinProxy), which is used for connection to internet as well.
The whole snapshot runs well, all the data are pumped to the subscriber and all dri, trg etc. scripts are executed without problem, but instead of the message "No data needed to be merged" comes out this error message:

Last Command: {call sp_MSgetreplicainfo(?,?,?,?,?,?,?)}

The subscription to publication 'Katalog' is invalid.
(Source: Merge Replication Provider (Agent); Error number: -2147201019)
--------------------------
General network error. Check your network documentation.
(Source: FANTOM (Data source); Error number: 11)
--------------------------

When I try to replicate the small Northwind database, everything works fine, no errors. When I try to replicate only a few tables from my big database, everything works fine.

Thank you very much for any ideas.The problem is probably in WinProxy. When comunicating without Proxy everything goes OK.|||Hi,

I had seen your psting and asking your help.

How do I use the FTP option in Merge Replication

I am using Merge Replication on SqlServer 2000 with SP2 and MDAC2.7 loaded on my system.
My database version is 8.00.534 on Windows2000 Advancedserver.

Both Publisher and Subscriber are running with same versions.

I created a publication and I created a pull subscription using internet.
I want the subscriber machine to access the Publisher
machine via ftp and get the Snapshot and do
Synchronization.

I had setup the following parameters at the Publisher side
for the publication.

1.Generate snapshots in the following location as

\\myservername\D$\Microsoft SQL Server\MSSQL\REPLDATA\ftp which is UNC shared with full access.

2.Checked - Subscribers can access this folder using FTP

ftpservername -myservername
port-21

Login-Anonymous, no password

3.At subscriber side I had setup SnapshotLocation property as
Download the folder using File Transfer Protocol - checked

I get the following errors at Synchronization time
After configuring subscriber for merge replication i am getting staus as succeeded at the subscriber.

when performing data modifications I am getting following errors during synchronisation time.

Errors

Category:NULL
Source: Merge Replication Provider
Number: -2147201001
Message: The schema script '' could not be propagated to the subscriber.

Category:AGENT
Source: SRVH
Number: 0
Message: The process could not connect to FTP site 'HERITAGEAMERICA' using port 21.

Category:OS
Source:
Number: 12007
Message: The server name or address could not be resolved

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

Microsoft conformed this is a bug and that details are
Question number is Q318592.
BUG #: 356652 (SHILOH_BUGS) BUG #: 356652 (SHILOH_BUGS)

Microsoft confirmed that this is a bug when we use different versions check with the Question in microsoft site in fixes.

I am getting same error for same versions also.

Can anyone help me on how to use FTP for accessing
Snapshots?

Thanks|||Hello,

I have not any experience with using FTP for merge replication over internet, we are using VPN connection to the server on port 1433.
But as far as I understood, you do not get the error message when transferring a snapshot but at the moment, when the distributor needs to propagate data changes between publisher and subscriber.
I suppose it is important when do you get the error message: whether on the very beginning of applying the snapshot or at the end.
Also would be useful to check, whether the FTP connection is reliable (proxies, switches etc.).

Caruso|||Hi

May be you can help me wit a minor problem in Merge replication. I am trying to perform merge replication on two SQL Server 2000 databases on Windows Nt 4.0 platform using TCP/IP and FTp. Have set everything in Publication and Subscriber for FTp and the subscriber can connect to publisher.

I am getting the followiing error message afetr running replmerg.exe withh all required parameters for FTP.

Microsoft SQL Server Merge Agent 8.00.194
Copyright (c) 2000 Microsoft Corporation

Connecting to Subscriber 'RAJ'
Connecting to Distributor 'VTPL'
Initializing
Connecting to Publisher 'VTPL'
Retrieving publication information
Retrieving subscription information
Snapshot files will be downloaded via ftp
Connecting to ftp site 'VTPL'
The subscription has been marked for reinitialization. Reinitialization will occur the next time you synchronize this subscription.
The schema script '\\VTPL\C$\Program Files\Microsoft SQL Server\MSSQL\ReplData\ftp\VTPL_Caryaire_F2\2003010 7120306\RightMain_1.sch' could not be propagated to the subscriber.
Category:NULL
Source: Merge Replication Provider
Number: -2147201001
Message: The schema script '\\VTPL\C$\Program Files\Microsoft SQL Server\MSSQL\ReplData\ftp\VTPL_Caryaire_F2\2003010 7120306\RightMain_1.sch' could not be propagated to the subscriber.
Category:AGENT
Source: VTPL
Number: 0
Message: The process could not retrieve file 'VTPL_Caryaire_F2\20030107120306\RightMain_1.sch' from the FTP site 'VTPL'.
Category:OS
Source:
Number: 12003
Message: 200 Type set to I.
200 PORT command successful.
550 VTPL_Caryaire_F2\20030107120306\RightMain_1.sch: The system cannot find the path specified.
550 VTPL_Caryaire_F2\20030107120306\RightMain_1.sch: The system cannot find the path specified.

The process finished. Use CTRL+C to close this window.

I am desparately in need of a solution. Can anyone help me out?

Thanks and regards,
Anamika|||Hi,

Anamika, first thing I would like you to do is check the verison of SQL server 2000. Merge Replication module has some problems. It have been fixed in the SQL server SP3. It is essential to apply this pack on SQL server.

Secondly you need to check ftp settings. your ftp service or root directory of ftp is not configured properly. Due to this you are getting "The process could not retrieve file 'VTPL_Caryaire_F2\20030107120306\RightMain_1.sch' from the FTP site 'VTPL'. "VTPL_Caryaire_F2" parent folder should be root of ftp site.
Details are available in windows or in IIS about ftp configuration.

Saturday, February 25, 2012

merge replication and snapshots

I am having the huge db of 80 GB and trying to configure merge replication. The intial snapshot application is failing due to some schema issues. I have made some necessary changes to avoid the schema issues. If I try start the merge agent it is going to re-initialize the snapshot and reapplying the whole snapshot will take atleast 10-15 hrs.

Is there any way to resume the snapshot from the point of failure.. avoiding the reapplying all the data which has already got transfered to subscriber.You cannot restart from the point of failure. You can do it w/o applying the snapshot. Look here:

http://technet.microsoft.com/en-us/library/ms152488.aspx

Monday, February 20, 2012

merge replication and domains

Does SQL2K needs the publisher and subscriber to be in same domain?
Can we configure merge replication between two stand-alone servers?
it does not, you can replicate from two stand alone server. What you should
do is create a local administrator account with the same name and password
on both servers and use this account for the SQL Server and SQL Server Agent
accounts.
--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"ravi lobo" <ravi lobo@.discussions.microsoft.com> wrote in message
news:1E7324F8-3F93-45C3-876A-56A7FE81D907@.microsoft.com...
> Does SQL2K needs the publisher and subscriber to be in same domain?
> Can we configure merge replication between two stand-alone servers?
|||You might want to have a look at these articles:
http://www.replicationanswers.com/InternetArticle.asp
http://support.microsoft.com/?id=321822
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com/default.asp
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||I have done that..but when i create the subscriber i get the message..process
could not deliver the snapshot to the subscriber..
"Hilary Cotter" wrote:

> it does not, you can replicate from two stand alone server. What you should
> do is create a local administrator account with the same name and password
> on both servers and use this account for the SQL Server and SQL Server Agent
> accounts.
> --
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "ravi lobo" <ravi lobo@.discussions.microsoft.com> wrote in message
> news:1E7324F8-3F93-45C3-876A-56A7FE81D907@.microsoft.com...
>
>
|||i did that but it was not working. Only after giving the $ share access to
the snapshot folder it started working.
"Hilary Cotter" wrote:

> it does not, you can replicate from two stand alone server. What you should
> do is create a local administrator account with the same name and password
> on both servers and use this account for the SQL Server and SQL Server Agent
> accounts.
> --
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "ravi lobo" <ravi lobo@.discussions.microsoft.com> wrote in message
> news:1E7324F8-3F93-45C3-876A-56A7FE81D907@.microsoft.com...
>
>

Merge replication 2005 - 2005 Express

Hi.
I want to replicate SQL 2005 - SQL 2005 Express. MS SQL 2005 (DevEdition
beta 2) is configured as Publisher/Distributor. I want ti configure SQL 2005
Express (beta 2)as Subscriber (pull-subscription).
For this purposes used T-SQL command (at Subscriber)
sp_addmergepullsubscription (after it runs in subscriber database appears
some system tables for "replication managment") Next step is to run (at
Subscriber)sp_addmergepullsubscription_agent procedure. I use it in this way:
use [DB_FOR_REPLICATION]
EXEC sp_addmergepullsubscription_agent
@.name = ...,
@.publisher = ...,
@.publisher_db = ...,
@.publication = ...,
@.publisher_security_mode=0,
@.publisher_login = ...,
@.publisher_password = ...,
@.distributor_security_mode=0,
@.distributor = ...,
@.distributor_login = ...,
@.distributor_password = ...,
@.job_login = ...,
@.job_password = ...,
@.use_interactive_resolver='false',
@.enabled_for_syncmgr='true',
@.frequency_type=4,
@.frequency_subday=4,
@.frequency_subday_interval=1,
@.active_start_date= 20050101;
GO
As I understand its meant that: SQL server authentication used for both
Publisher/Distributor(login/pswrd i supplied), replication is sheduled to run
every minute since 2005 jan 01 and _subscription can be synchronized through
Windows Synchronization Manager_.
Questions:
1. Does Windows Synchronization Manager keep password i provided in SP
above? (every time i'm trying to run it asks me to enter 'em again).
2. Where i can find schedule mentioned in SP (every minute since...)?
3. What happens when @.enabled_for_syncmgr='false'? I cant syncronize DBs at
all. No agent tables in SubscriptionDB and no schedule in MSBD.
Thnx for answers
Best Regards Maxim Morzhov
Does anyone know?
Best regards
Morzhov M.
|||Since SQL Server 2005 Express Edition doesn't include SQL Agent, the
scheduling parameters will be ingored. After you create the subscription, you
must setup a schedule in Windows Synchronization Manager to run the agent on
a schedule.
If you don't enable Windows Syncronization Manager, you can still
synchronize the subscription by running the Merge Agent directly (C:\Program
Files\Microsoft SQL Server\90\COM\replmerge.exe) as shown in the SQL Server
2005 BOL topic "
How to: Synchronize a Pull Subscription (Replication Programming)." Or you
can write an application that uses RMO to synchronize the subscription.
Hope that helps,
Glenn Gailey [MS]
This posting is provided "AS IS" with no warranties, and confers no rights.
"MaxX_RUS" wrote:

> Hi.
> I want to replicate SQL 2005 - SQL 2005 Express. MS SQL 2005 (DevEdition
> beta 2) is configured as Publisher/Distributor. I want ti configure SQL 2005
> Express (beta 2)as Subscriber (pull-subscription).
> For this purposes used T-SQL command (at Subscriber)
> sp_addmergepullsubscription (after it runs in subscriber database appears
> some system tables for "replication managment") Next step is to run (at
> Subscriber)sp_addmergepullsubscription_agent procedure. I use it in this way:
> use [DB_FOR_REPLICATION]
> EXEC sp_addmergepullsubscription_agent
> @.name = ...,
> @.publisher = ...,
> @.publisher_db = ...,
> @.publication = ...,
> @.publisher_security_mode=0,
> @.publisher_login = ...,
> @.publisher_password = ...,
> @.distributor_security_mode=0,
> @.distributor = ...,
> @.distributor_login = ...,
> @.distributor_password = ...,
> @.job_login = ...,
> @.job_password = ...,
> @.use_interactive_resolver='false',
> @.enabled_for_syncmgr='true',
> @.frequency_type=4,
> @.frequency_subday=4,
> @.frequency_subday_interval=1,
> @.active_start_date= 20050101;
> GO
> As I understand its meant that: SQL server authentication used for both
> Publisher/Distributor(login/pswrd i supplied), replication is sheduled to run
> every minute since 2005 jan 01 and _subscription can be synchronized through
> Windows Synchronization Manager_.
> Questions:
> 1. Does Windows Synchronization Manager keep password i provided in SP
> above? (every time i'm trying to run it asks me to enter 'em again).
> 2. Where i can find schedule mentioned in SP (every minute since...)?
> 3. What happens when @.enabled_for_syncmgr='false'? I cant syncronize DBs at
> all. No agent tables in SubscriptionDB and no schedule in MSBD.
> Thnx for answers
> Best Regards Maxim Morzhov