MS SQL Server Merge Replication

Hi, I have two databases on MS. SQL Server 200 the first one is the
main DB and the second one is a replica of it, both of them in
different territories .I connect them using merge replication just
when I need to merge the data.

The problem is when I make import data or export data from any
location (MS access ,MS SQL server ) to the second one (subscriber DB)
or the main DB(publisher and distributor ) ,the imported data does
not replicated to the other DB ?

Normal transaction replicated smoothly.

I hope you can help me.

Thanks in advance.

Mahmoud Khebaisa.mahmod79@.hotmail.com (Mahmoud KHEBAISA) wrote in message news:<ce543867.0408190341.2cd2244@.posting.google.com>...
> Hi, I have two databases on MS. SQL Server 200 the first one is the
> main DB and the second one is a replica of it, both of them in
> different territories .I connect them using merge replication just
> when I need to merge the data.
> The problem is when I make import data or export data from any
> location (MS access ,MS SQL server ) to the second one (subscriber DB)
> or the main DB(publisher and distributor ) ,the imported data does
> not replicated to the other DB ?
> Normal transaction replicated smoothly.
> I hope you can help me.
> Thanks in advance.
> Mahmoud Khebaisa.

You might want to post this in microsoft.public.sqlserver.replication
to get a better answer. You should probably also mention exactly how
you are importing the data which are not replicated, eg. DTS, bcp.exe,
a custom tool etc.

Simon

MS SQL Server 2000 replication deployment

Hi
I want to implement transactional replication on 2 MS SQL Servers 2000
(SP3). Is there any good guide available that discusses crucial points in
this endeavour (e.g. possible topologies, what and how needs to be monitored,
potential issues to avoid, what to do in case of failures etc.)? I need a
document that focuses on moving the replication into production environment.
I'm especially interested in alternative means of monitoring the replication
rather than the built-in one.
Many thanks,
Oskar
You can check BOL, do a search on MSDN for transactional replication. You
might want to consider my book
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
"Oskar" <Oskar@.discussions.microsoft.com> wrote in message
news:3F9E5C48-79C8-4D76-87C8-B9C2ABC6C840@.microsoft.com...
> Hi
> I want to implement transactional replication on 2 MS SQL Servers 2000
> (SP3). Is there any good guide available that discusses crucial points in
> this endeavour (e.g. possible topologies, what and how needs to be
monitored,
> potential issues to avoid, what to do in case of failures etc.)? I need a
> document that focuses on moving the replication into production
environment.
> I'm especially interested in alternative means of monitoring the
replication
> rather than the built-in one.
> --
> Many thanks,
> Oskar
>
|||Yeah, but are you completely sure that these sources give answers to the
specific questions I have? So far I was unable to find answers to my
questions in BOL.
"Hilary Cotter" wrote:

> You can check BOL, do a search on MSDN for transactional replication. You
> might want to consider my book
> --
> 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
> "Oskar" <Oskar@.discussions.microsoft.com> wrote in message
> news:3F9E5C48-79C8-4D76-87C8-B9C2ABC6C840@.microsoft.com...
> monitored,
> environment.
> replication
>
>

MS SQL Replication Error -XParentProcessHandle

Recieving the following error when I try to fire off the snapshot agent for transactional replication. I'm new to 2005 replication. Any suggestions? Thanks,

2007-08-14 00:49:08.972 Status: 0, code: 20030, text: 'A syntax error occurred near parameter '-XParentProcessHandle'.'.
2007-08-14 00:49:08.972 A syntax error occurred near parameter '-XParentProcessHandle'.

Can you do select @.@.version and tell me the version of your publisher and distributor? And on what machine are you running the snapshot agent?

MS SQL Replication Error -XParentProcessHandle

Recieving the following error when I try to fire off the snapshot agent for transactional replication. I'm new to 2005 replication. Any suggestions? Thanks,

2007-08-14 00:49:08.972 Status: 0, code: 20030, text: 'A syntax error occurred near parameter '-XParentProcessHandle'.'.
2007-08-14 00:49:08.972 A syntax error occurred near parameter '-XParentProcessHandle'.

Can you do select @.@.version and tell me the version of your publisher and distributor? And on what machine are you running the snapshot agent?

MS Sql replication - Primary keys problem

Hi.
I am trying to replicate an MS SQL server but when I do that all my primary keys on the tables on subscriber server are gone and the datebase is unusefull.
Can anyone help me in that situation?

Thanks in advance.

Quote:

Originally Posted by Yordan Yordanov

Hi.
I am trying to replicate an MS SQL server but when I do that all my primary keys on the tables on subscriber server are gone and the datebase is unusefull.
Can anyone help me in that situation?

Thanks in advance.

Set "Copy unique key constraints" property of the articles on the publisher to True if you're on SQL Server 2005.

MS SQL 2000 TCPIP Port Number and SQL Replication

Hi all

I'm struggling to find an answer to this one!

We've configured our SQL boxes to run under a different port number,
e.g. from 1433 to 4533. This works fine under our Citrix enviornmnet
where the dsn is configured to use the new port. The problem comes in
terms of SQL Server management. For example, when you try and
configure SQL Replication, it is not possible to add the subscriber
unless the SQL Servce runs under port 1433, the default port. The
same goes when you try to add the server as a registered server within
the Enterprise Manager MMC.

Does anyone know how you can configure SQL Server to run under a
different port number, without naffecting SQL REPLICATION, etc?

Many thnaks
Nik
nik@.nastek.co.uknik@.nastek.co.uk wrote in message news:<a30v10lk653eu3j878hfj0tpflub252qrl@.4ax.com>...
> Hi all
> I'm struggling to find an answer to this one!
> We've configured our SQL boxes to run under a different port number,
> e.g. from 1433 to 4533. This works fine under our Citrix enviornmnet
> where the dsn is configured to use the new port. The problem comes in
> terms of SQL Server management. For example, when you try and
> configure SQL Replication, it is not possible to add the subscriber
> unless the SQL Servce runs under port 1433, the default port. The
> same goes when you try to add the server as a registered server within
> the Enterprise Manager MMC.
> Does anyone know how you can configure SQL Server to run under a
> different port number, without naffecting SQL REPLICATION, etc?
> Many thnaks
> Nik
> nik@.nastek.co.uk

I haven't tried this myself, but this KB article seems to suggest that
creating a server alias (in Client Network Utility) with the correct
port number should work:

http://support.microsoft.com/defaul...2&Product=sql2k

Simon|||sql@.hayes.ch (Simon Hayes) wrote in message news:<60cd0137.0402030644.62669b66@.posting.google.com>...
> nik@.nastek.co.uk wrote in message news:<a30v10lk653eu3j878hfj0tpflub252qrl@.4ax.com>...
> > Hi all
> > I'm struggling to find an answer to this one!
> > We've configured our SQL boxes to run under a different port number,
> > e.g. from 1433 to 4533. This works fine under our Citrix enviornmnet
> > where the dsn is configured to use the new port. The problem comes in
> > terms of SQL Server management. For example, when you try and
> > configure SQL Replication, it is not possible to add the subscriber
> > unless the SQL Servce runs under port 1433, the default port. The
> > same goes when you try to add the server as a registered server within
> > the Enterprise Manager MMC.
> > Does anyone know how you can configure SQL Server to run under a
> > different port number, without naffecting SQL REPLICATION, etc?
> > Many thnaks
> > Nik
> > nik@.nastek.co.uk
> I haven't tried this myself, but this KB article seems to suggest that
> creating a server alias (in Client Network Utility) with the correct
> port number should work:
> http://support.microsoft.com/defaul...2&Product=sql2k
> Simon

We have some servers with non-standard ports. We access them using the
Client Network Utility with the correct port and have no problems with
MMC, ISQLW or OSQLW or even ODBC.