is it possible to have many publisher and one subscriber ?

we have 20 branches running same application with 20 sql server databases.
can i have replication of data of all branches into one Central Server.
All branches have different branch code in each table as one of the column
of primary key.
Also is this same phenomenon posiible in ORACLE?
Please check out this article for the Multiple Publishers and Central
Subscriber Setup:
http://www.replicationanswers.com/CentralSubscriberArticle.asp
No idea if Oracle supports this natively. If however you are talking about
Oracle Publications as supported in SQL Server 2005 I'll do some checking.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .

Is it possible to do Replication Manually

I'm not too sure what you mean, but if replication is set
up then the relevant job can be started using
sp_start_job. Is this what you were looking for?
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
hi,
Thanks Paul. But this is not the one i need, I don't wanna do replication
by creating publishers and all (Not un\sing the EM). But i want to know, is
it possible to do replication manually. i.e .taking the differfences of the
tables and inserting it into the curresponding table.
I think u got it.
regards aneesh
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:032501c4e1c8$b3ea92e0$a601280a@.phx.gbl...
> I'm not too sure what you mean, but if replication is set
> up then the relevant job can be started using
> sp_start_job. Is this what you were looking for?
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||It is possible, but not easy. If the data is partitioned,
then it is not too difficult, but if not, you'll have to
consider conflicts and how to deal with them.
First of all, you need to know if a row has changed
(inserted or updated), and triggers are the ideal
mechanism for this - yout edit an extra column, or store
the id of the row in a separate table (a separate table
is especially useful for deletes). This has to be done on
the publisher and subscriber. Then routines created to
parse these tables and do joins to find non-matches
before applying the changes. Do you recognise what is
happening as this is worked through? We are essentially
recreating the procedures used by (merge) replication
itself .
If you have a very simple business requirement, with
partitioned data and no deletes, then it might be worth
looking at the manual solution, otherwise using the
inbuilt tools will save weeks/months of work.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

>--Original Message--
>hi,
>Thanks Paul. But this is not the one i need, I don't
wanna do replication
>by creating publishers and all (Not un\sing the EM). But
i want to know, is
>it possible to do replication manually. i.e .taking the
differfences of the
>tables and inserting it into the curresponding table.
>I think u got it.
>regards aneesh
>"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in
message[vbcol=seagreen]
>news:032501c4e1c8$b3ea92e0$a601280a@.phx.gbl...
set
>
>.
>

Is it possible to do Replication Manually

Hi,
This is a silmple Qn. I know it is possible to Replicate thru Query
Analizer. But i don't know the steps
can anyone help me
An
Have you looked at Log shipping? We use a home grown version for some of our
SQL servers, with out any problems.
"AR" <aneesh.r@.eostek.com> wrote in message
news:OZulCUc4EHA.1192@.tk2msftngp13.phx.gbl...
> Hi,
> This is a silmple Qn. I know it is possible to Replicate thru Query
> Analizer. But i don't know the steps
> can anyone help me
> An
>
sql

Is it possible to alter snapshot agent to not drop tables?

We've got transactional replication set up from 2000 to 05. Is there a
way to not let the snapshot agent to drop and recreate the destination
tables, but rather truncate them?
Thank you,
Igor
*** Sent via Developersdex http://www.codecomments.com ***
Have a look at the article properties (@.pre_creation_cmd ). By default it is
Drop, but it can be converted to delete or truncate (or none).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Right ON!
Thank you.
*** Sent via Developersdex http://www.codecomments.com ***

Is it possible replicate Service Broker Object and messages?

Could anybody suggest to me - is it possible replicate Service Broker Object and messages (in the queue) with usual Replication Process?

Thanks to all very much,

Sveta.

what are service broker object and messages, user tables? views? procs? if not, then no. if yes, and they're not marked as system objects, then you might be able to, just know that some replication topologies will add columns and indexes to tables.|||

Thank you for the explanation!

Sveta

Is it possible for a subscriber to know.......

whether it is sync...ing
is there any sp can find out the replication is working properly?
thank you very much
You could have a look at the distribution agent's job to see if it is in
process - sp_helpjob or this link:
http://www.replicationanswers.com/Do...unningJobs.txt
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Is is necessary for a table which will be part of the Replication process to have a and Primary

Hi there,

We're going to use replication on our database. There are tables without any primary key.

Is a primary key necessary for replication?

I have also antoher question: We want to replicate the whole OLTP database (size 30 GB).

Is snapshot replication a suitable mechanisme for this? I thougt snapshot replication overwrites all of the data, not only changed data. Or should we use another replication method?

Thanks in advance,

Patrick de Jong

A primary key is necessary to replicate an article so that a unique record can always be found. Snapshotting a 30gb everytime might not be such a great idea. Transactional is probably a better way to go, depending on your situation.
Tim|||

Yes you need to have a primary key on each table for replication.

Depending on how often your data changes and how frequently you need to have the subscriber updated is the best way to decide if snapshot replication is the best method.

Typically snapshot is not the best option unless you have a very high data change rate and you only need the subscriber updated once or twice per day (or less frequently).

|||

Thanks for the answer's. The really helped me.

1.) My customer has te deside on which fields the pk must come.

2.) I think we will use transactional replication.

Greetz,

Patrick de Jong

|||

Hi Friends,

1.Yes a table involved in Transactional replication should have a primary key defined.Also if u hav opted for transactional publication with updating subscriber,a unique identifier is required for a table.

2.Since it is a OLTP Database it keeps changing frequently,my suggestion would be to go for Transactional Replication.

Always prefer Snapshot replication for datas which do not change frequently (OLAP environment)

Rgds

Deepak

|||

Thanks Deepak,

Today we've made a list of tables without a PK. It seems to be no problem to add the missing PK's because the tabels had an identity which was used as some sort of PK. Tomorrow we will test transactional replication.

Greetz,

Patrick de Jong

Is IIS always required for replication?

I would like to take advantage of either Merge or RDA replication over HTTP, but would like to avoid setting up IIS.

Is IIS always required to support connectivity for SQL Server Mobile replication back to a desktop SQL Server database?

Thanks, Tim

Yes IIS is very much required for Merge or RDA with SQL Server. However, setting up IIS is not a big thing as we have a "Configure Web Synchronization" wizard that is very helpful for you in this regard.

Thanks,

Laxmi NRO, MSFT, SQL Mobile, Microsoft Corporation

|||Hi

And how setting up a replication bettween a Windows Mobile 5 Pocket PC and a Windows XP Home Edition PC when IIS can't be install on Home Edition ?

?

Thanks for help
Jo?l

|||

1) What is your backend database?

2) Can I know what is the problem in moving to Win XP Professional Edition?

Thanks,

Laxmi Narsimha Rao ORUGANTI, MSFT, SQL Mobile, Microsoft Corporation

|||1) To replace synchronisation between Access/PocketAccess (not more supported with WM5), we use know a MSDE database (on PC) with a SQL Server CE 2.0 database (on PocketPC). The replication work fine on Windows XP Pro, but on Windows XP Home there is no IIS to do the replication.

2) Our customer have Windows XP Home Edition. I'm ok with you that's not very "professional", but we can't tell to our customer : "Hey guys, you must move your forty PC to Windows XP Pro, because our software don't run on XP Home". They will say us "bye bye".

And they have already some old PocketPC (before WM5) with this application installed and it works with XP Home ... that's a big problem for us.

Thanks for helping us

|||I have heard that we can synchronize using ActiveSync is it correct or not, because on Online Book I read we can synchronize using IIS. I need to synchronize my database on Pocket PC to my Desktop PC without using IIS (if we have the cradle why we need access to internet from Pocket PC).

And if synchronized only can work with IIS than use the old way try to send each data by client server application. Its a silly things, but thats the only way if we can only synchronize using IIS.

Is IIS always required for replication?

I would like to take advantage of either Merge or RDA replication over HTTP, but would like to avoid setting up IIS.

Is IIS always required to support connectivity for SQL Server Mobile replication back to a desktop SQL Server database?

Thanks, Tim

Yes IIS is very much required for Merge or RDA with SQL Server. However, setting up IIS is not a big thing as we have a "Configure Web Synchronization" wizard that is very helpful for you in this regard.

Thanks,

Laxmi NRO, MSFT, SQL Mobile, Microsoft Corporation

|||Hi

And how setting up a replication bettween a Windows Mobile 5 Pocket PC and a Windows XP Home Edition PC when IIS can't be install on Home Edition ?

?

Thanks for help
Jo?l|||

1) What is your backend database?

2) Can I know what is the problem in moving to Win XP Professional Edition?

Thanks,

Laxmi Narsimha Rao ORUGANTI, MSFT, SQL Mobile, Microsoft Corporation

|||1) To replace synchronisation between Access/PocketAccess (not more supported with WM5), we use know a MSDE database (on PC) with a SQL Server CE 2.0 database (on PocketPC). The replication work fine on Windows XP Pro, but on Windows XP Home there is no IIS to do the replication.

2) Our customer have Windows XP Home Edition. I'm ok with you that's not very "professional", but we can't tell to our customer : "Hey guys, you must move your forty PC to Windows XP Pro, because our software don't run on XP Home". They will say us "bye bye".

And they have already some old PocketPC (before WM5) with this application installed and it works with XP Home ... that's a big problem for us.

Thanks for helping us|||I have heard that we can synchronize using ActiveSync is it correct or not, because on Online Book I read we can synchronize using IIS. I need to synchronize my database on Pocket PC to my Desktop PC without using IIS (if we have the cradle why we need access to internet from Pocket PC).

And if synchronized only can work with IIS than use the old way try to send each data by client server application. Its a silly things, but thats the only way if we can only synchronize using IIS.

is DB publication/subscription?

Because of problems trying to alter databases used
for replication my software would need to find out
if a database is a publisher or was repliated (using
T-SQL). Is this possible?Look in BOL for sp_dboption

This should be able to tell you if the database is Published etc

Cheers

Is complete control over subscriber-to-publisher inserts/updates possible?

Hi, we are using merge replication from our server (SQL Server 2005) to what
will soon be hundreds of subscribers. The subscribers are actually from a
Windows app that uses a SQLCE database. The client app is able to insert and
update records that are then merged up to the server. Everything I have
mentioned up to this point is already functional, but we recently realized
that more "control" over the replication process is needed. Here's what we
want to do: When a record that was inserted at the subscriber is replicated
up to the server, it must be caught and redirected to a stored procedure
which will perform the insert instead. This should be completely transparent
to the subscriber (meaning we can't return them an error code).
Unless I am mistaken the only way to get this kind of functionality is by
using a business logic handler. I have a sample which demonstrates some very
basic uses for the business logic handler but unfortunately it barely
scratches the surface of what is possible. This doc page from the BO explains
a scenario very similar to what we need (Custom Change Handling -> Apply
custom data), but I do not know how I would go about implementing it.
Can anyone who has done something like this before point me in the right
direction?
Using the BusinessLogic resolver is the correct way of doing it.
If the logic is such that it is only in one direction or only one table is
affected you can either use transactional replication from the subscribers
to the publisher (you will need to upgrade your subscribers to SQL Server
2005 standard for this), or have a trigger hanging of the publisher table so
when the insert arrives this trigger will process it and fire the stored
procedure.
You can use the session_property function to detect if the process doing the
dml is a replication process.
if convert(bit, sessionproperty('replication_agent'))=1
do work.
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
"Chris" <no@.spam.com> wrote in message
news:%2367uVkx0HHA.4932@.TK2MSFTNGP03.phx.gbl...
> Hi, we are using merge replication from our server (SQL Server 2005) to
> what
> will soon be hundreds of subscribers. The subscribers are actually from a
> Windows app that uses a SQLCE database. The client app is able to insert
> and
> update records that are then merged up to the server. Everything I have
> mentioned up to this point is already functional, but we recently realized
> that more "control" over the replication process is needed. Here's what we
> want to do: When a record that was inserted at the subscriber is
> replicated
> up to the server, it must be caught and redirected to a stored procedure
> which will perform the insert instead. This should be completely
> transparent
> to the subscriber (meaning we can't return them an error code).
> Unless I am mistaken the only way to get this kind of functionality is by
> using a business logic handler. I have a sample which demonstrates some
> very
> basic uses for the business logic handler but unfortunately it barely
> scratches the surface of what is possible. This doc page from the BO
> explains
> a scenario very similar to what we need (Custom Change Handling -> Apply
> custom data), but I do not know how I would go about implementing it.
> Can anyone who has done something like this before point me in the right
> direction?
|||Thank you Hilary. I would prefer to use the business logic resolver though if
possible, but the more I dig into this it seems like it won't work the way I
need it to. I believe all I can do with it is modify the record sent from the
subscriber. Please correct me if I'm wrong, but it will not allow me to
*stop* the insert unless I outright reject it. Meaning I can't "redirect" the
insert to a SP and still tell the subscriber that everything went fine.
Using a trigger on the publisher table seems interresting. I will have to
look into that further. Thanks for your insight.
Chris
On 7/31/2007 6:39:27 AM, "Hilary Cotter" wrote:
> Using the BusinessLogic resolver is the correct way of doing it.
> If the logic is such that it is only in one direction or only one table is
> affected you can either use transactional replication from the subscribers
> to the publisher (you will need to upgrade your subscribers to SQL Server
> 2005 standard for this), or have a trigger hanging of the publisher table so
> when the insert arrives this trigger will process it and fire the stored
> procedure.
> You can use the session_property function to detect if the process doing the
> dml is a replication process.
> if convert(bit, sessionproperty('replication_agent'))=1
> do work.
>

Is bug described in article 872843 really fixed?

I'm running SQL Server 2000 SP4 with the AWE hotfix (build 2040?) on Windows
Server 2003 with replication.
This morning, my log reader agents failed. In the server log, I saw the
following messages:
SQL Server Assertion: File: <logscan.cpp>, line=1985
Failed Assertion = 'startLSN >= m_curLSN'.
...
SQL Server Assertion: File: <logscan.cpp>, line=2223
Failed Assertion = 'm_noOfScAlloc == 0'.
KB article 872843 says that this is supposed to be fixed in SP4... is it?
Or did it come back in the AWE hotfix?
Regards,
Jonathan
Hello,
KB872843 is included in SQL server 2000 SP4. It appears a new issue and is
not related to the AWE hotfix. Please reInitializing the replication and
then check if the issue still exists.
To find out the cause of this issue we may need to analyze memory dumps,
this work has to be done by contacting Microsoft Customer Service and
Support (CSS). Therefore, if the issue still exists, please contact CSS for
more immediate assistance. For more information on available CSS services,
please click here:
http://support.microsoft.com/default...roPhone#faq607

Is bug described in article 872843 really fixed?

I'm running SQL Server 2000 SP4 with the AWE hotfix (build 2040?) on Windows
Server 2003 with replication.
This morning, my log reader agents failed. In the server log, I saw the
following messages:
SQL Server Assertion: File: <logscan.cpp>, line=1985
Failed Assertion = 'startLSN >= m_curLSN'.
...
SQL Server Assertion: File: <logscan.cpp>, line=2223
Failed Assertion = 'm_noOfScAlloc == 0'.
KB article 872843 says that this is supposed to be fixed in SP4... is it?
Or did it come back in the AWE hotfix?
Regards,
JonathanHello,
KB872843 is included in SQL server 2000 SP4. It appears a new issue and is
not related to the AWE hotfix. Please reInitializing the replication and
then check if the issue still exists.
To find out the cause of this issue we may need to analyze memory dumps,
this work has to be done by contacting Microsoft Customer Service and
Support (CSS). Therefore, if the issue still exists, please contact CSS for
more immediate assistance. For more information on available CSS services,
please click here:
http://support.microsoft.com/defaul...ProPhone#faq607

Is bug described in article 872843 really fixed?

I'm running SQL Server 2000 SP4 with the AWE hotfix (build 2040?) on Windows
Server 2003 with replication.
This morning, my log reader agents failed. In the server log, I saw the
following messages:
SQL Server Assertion: File: <logscan.cpp>, line=1985
Failed Assertion = 'startLSN >= m_curLSN'.
...
SQL Server Assertion: File: <logscan.cpp>, line=2223
Failed Assertion = 'm_noOfScAlloc == 0'.
KB article 872843 says that this is supposed to be fixed in SP4... is it?
Or did it come back in the AWE hotfix?
Regards,
JonathanHello,
KB872843 is included in SQL server 2000 SP4. It appears a new issue and is
not related to the AWE hotfix. Please reInitializing the replication and
then check if the issue still exists.
To find out the cause of this issue we may need to analyze memory dumps,
this work has to be done by contacting Microsoft Customer Service and
Support (CSS). Therefore, if the issue still exists, please contact CSS for
more immediate assistance. For more information on available CSS services,
please click here:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607