Showing posts with label implement. Show all posts
Showing posts with label implement. Show all posts

Wednesday, March 28, 2012

merge replication with pull subscriber(compress snapshot)

Hi
I am trying to implement merge publication with compress snapshot, copy it
to the subscriber,
create a pull subscriber with the alternate folder(where the snapshot was
copied to)
and then run the agent for synchronization (first time).
i get error that the table in the publication does not exist in the
subscriber database.
It seems that the agent ignores the snapshot and it tries to just merge the
changes between publisher and subscriber.
when i create the table manually at the subscriber with the rowguid column,
it does not fail but it stills does not aplly the snapshot.
if i update/insert new row and run the agent it does merge the changes.
am i missing a crucial step in the process that causes that problem?
Thanks in advance
Daniel
daniel
Please can you post up the error message in its entirety. I suspect that it
is related to a script missing. Also, please try not using the CAB file
method. If you need to compress the snapshot, zip it up and unzip on the
subscriber (I only say this because I've never tested using an alternative
folder with a CAB file).
Paul Ibison
|||Hi and thank u for the replying.
When i start the agent for the first time i get the following error:
"Table 't3' does not exist in the Subscriber database."
At the log i can see that he does try to get the snapshot from alternate
folder:
" Snapshot will be applied from the alternate folder ..."
thanks in advance
Daniel
daniel
"Paul Ibison" wrote:

> Please can you post up the error message in its entirety. I suspect that it
> is related to a script missing. Also, please try not using the CAB file
> method. If you need to compress the snapshot, zip it up and unzip on the
> subscriber (I only say this because I've never tested using an alternative
> folder with a CAB file).
> Paul Ibison
|||Interesting - if you enable full logging is there more info? Also, are you
using the uncompressed snapshot files (if not please try this way also)? In
the snapshot files do you see the table creation script for t3?
(the alternative to this investigation if you like is to do a nosync
initialization).
Paul Ibison
|||Hi Paul
Yes there is a script for table creation.
I tried to use the uncompressed and i got the same error.
How do i do the no sync initialization?
daniel
"Paul Ibison" wrote:

> Interesting - if you enable full logging is there more info? Also, are you
> using the uncompressed snapshot files (if not please try this way also)? In
> the snapshot files do you see the table creation script for t3?
> (the alternative to this investigation if you like is to do a nosync
> initialization).
> Paul Ibison
|||Please have a look here. It largely applies to transactional, but mostly the
same info applies: http://www.replicationanswers.com/NoSyncInitializations.asp
HTH,
Paul Ibison

Friday, March 23, 2012

Merge replication schema changes

I want to implement merge replication between SQL Server 2005 and SQL Server
2005 express. My problem is, when we make table schema changes like adding
and removing columns, we drop and re-create the table. Is there any way that
this methodology can work with merge replication. I know the replication
trigger only track ATLER TABLE statements.
Thanks
Mark,
I'm not too sure what is happeng here. Are you saying that the ALTER TABLE
statement causes reinitialization? Or is a new snapshot being created? Or do
you manually drop the table, change the columns and then add the table
again? Just trying to get the gist of the issue
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Hi Paul,
We manually drop the table, change the columns and then add the table again.
The documentation I've read says that merge replication only tracks ATLER
TABLE statements. (Which we don't use).
Thanks for the quick response.
"Paul Ibison" wrote:

> Mark,
> I'm not too sure what is happeng here. Are you saying that the ALTER TABLE
> statement causes reinitialization? Or is a new snapshot being created? Or do
> you manually drop the table, change the columns and then add the table
> again? Just trying to get the gist of the issue
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
>
|||Mark - not sure I follow - how do you make the changes to the table's
schema?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Hi Paul,
When we need to change a tables schema, we copy all the data out into a new
table with the new table structure. Then we delete the old table and rename
the new table to be the old table. If we want to add a new column to a table
we do not issue and ALTER TABLE add <column_name>... statement. We create a
new table with the new column in it and then copy the data over from the old
table. Update the new column with appropriate values. DROP the old table and
RENAME the new table. How can we get these schema changes propegated to the
subscribers.
Can we remove the table first from the publication. Drop and CREATE the
table and then add it into the publication again? What about pending
subscriber changes. Would they be lost in that case?
Thanks again.
"Paul Ibison" wrote:

> Mark - not sure I follow - how do you make the changes to the table's
> schema?
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
>
>
|||I would advise to use the inbuilt merge replication's support to ALTER
TABLES and propagate schema changes.
However I can also understand that it may be difficult to change the app. In
that case, yes you could drop the article and readd it after you change the
schema. The subscriber's unsent data will cause a problem in this case.
You may think that setting a pre_creation_cmd of 'none' to save the
subscriber's unsent changes. But remember that the schema is now different
between publisher and subscriber.
One thing you can do is to save off subscriber's unsent changes into a temp
table and then reinsert these rows after re-synchronizing the (new schema)
table.
Hope that helps
--Mahesh
[ This posting is provided "as is" with no warranties and confers no
rights. ]
"Mark (WHSCC)" <MarkWHSCC@.discussions.microsoft.com> wrote in message
news:63DB1088-15DE-4A3C-8FEE-A91C79D4AC9E@.microsoft.com...[vbcol=seagreen]
> Hi Paul,
> When we need to change a tables schema, we copy all the data out into a
> new
> table with the new table structure. Then we delete the old table and
> rename
> the new table to be the old table. If we want to add a new column to a
> table
> we do not issue and ALTER TABLE add <column_name>... statement. We create
> a
> new table with the new column in it and then copy the data over from the
> old
> table. Update the new column with appropriate values. DROP the old table
> and
> RENAME the new table. How can we get these schema changes propegated to
> the
> subscribers.
> Can we remove the table first from the publication. Drop and CREATE the
> table and then add it into the publication again? What about pending
> subscriber changes. Would they be lost in that case?
> Thanks again.
> "Paul Ibison" wrote:

Wednesday, March 21, 2012

Merge Replication programming with SQL Snapshot and SQL Distribution Control

Hello all, I am try to implement Merge replication just
like this
article shows for transaction type replicaion
http://support.microsoft.com/default.aspx?scid=kb;EN-
US;319649
using SQL Snapshot and SQL Distribution Control with
Visual C# .NET
First ..I dont see
Use a Distribution Agent that is independent of other
publications from this database and Snapshot files are
always available to initialize new subscriptions
immediately check boxes under subscription options.
second..
I get an error on SQL Snapshot object initialization
Erro # 24006 and message : The publication does not exist.
Sri,
you're using the wrong article - the one you have applies to transactional
and snapshot. For merge, have a look at this one:
http://support.microsoft.com/default...b;EN-US;319647
HTH,
Paul Ibison
|||Paul, Thank you very much.It worked like a charm.
Once again Thanks a million.
Srinu
>--Original Message--
>Sri,
>you're using the wrong article - the one you have applies
to transactional
>and snapshot. For merge, have a look at this one:
>http://support.microsoft.com/default.aspx?scid=kb;EN-
US;319647
>HTH,
>Paul Ibison
>
>.
>

Monday, March 12, 2012

Merge Replication in POS

Hello folks!
I have to implement the merge replication for the retail POS software. Right now I am doing the research and study work of Merge Replication in the scenario of POS ( url ). What i want to ask is, how much time complexity is typically involved to implement it completely (for consumer POS). Can someone give me a rough idea. Any precautions and nice reading materials (step-by-step implementation process) would be great.

cheers

Its difficult to predict complexity without more information on the complexity of the data model and the number of subscribers. However replication requires a lot of maintenance and monitoring and when something goes wrong (which it quite often does) it can consume weeks of time.

Suggest you get a book on SQL Server Replication i can recommend "Pro SQL Server 2005 Replication" by "Sujoy P. Paul

Martin

|||thanks martin!
can anyone tell me the link to find the sample merge replication implementations w/ sql server05 standard ed.. I have got its sample for mobile devices but thats not what i required.

Merge Replication in POS

Hello folks!
I have to implement the merge replication for the retail POS software. Right now I am doing the research and study work of Merge Replication in the scenario of POS ( url ). What i want to ask is, how much time complexity is typically involved to implement it completely (for consumer POS). Can someone give me a rough idea. Any precautions and nice reading materials (step-by-step implementation process) would be great.

cheers

Its difficult to predict complexity without more information on the complexity of the data model and the number of subscribers. However replication requires a lot of maintenance and monitoring and when something goes wrong (which it quite often does) it can consume weeks of time.

Suggest you get a book on SQL Server Replication i can recommend "Pro SQL Server 2005 Replication" by "Sujoy P. Paul

Martin

|||thanks martin!
can anyone tell me the link to find the sample merge replication implementations w/ sql server05 standard ed.. I have got its sample for mobile devices but thats not what i required.

Saturday, February 25, 2012

Merge Replication Architecture Planning Guidance

Hi,
My organization is considering use of merge replication (SQL Server 2K with MSDE clients) to implement a classic data-centric "occasionally connected" application pattern. The target user base extends to 4,500 users distributed across time zones and lang
uages. Depending on their location users will connect over telecom links varying from 28.8Kbps to broadband.
Our preference is to retain a single, centralized SQL Server cluster as a publisher and to deploy multiple remote distributor nodes to optimize performance. However, I've been unable to find a comprehensive capacity planning guide that can help us to det
ermine a) whether our proposed architecture is viable and b) how and where we should deploy distributor notes to optimize use of available processing capacity and bandwidth.
If anyone is aware of such a guide, or has first-hand operational experience of a deployment commensurate with that described above then I'd love to hear about it.
Cheers,
Lee.
Lee,
this article details scaling upto 2000 subscribers. I don't know of any
other articles that suit your needs, although Hilary once mentioned a
presentation at SQLPASS or TECHNET conference that sounds as though it'd be
useful to you. He posted the name of the presenter but unfortunately Idon't
recall it. No doubt he'll post a reply here.
Rgds,
Paul Ibison, SQL Server MVP, WWW.Replicationanswers.Com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||I don't recall such a presentation. However the presentations done by Bren
Newman, Philip Vaughn, Matt Hollingsworth, and Kevin Collins (for SQL CE
replication) are excellent.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23DSrOufuEHA.1292@.TK2MSFTNGP10.phx.gbl...
> Lee,
> this article details scaling upto 2000 subscribers. I don't know of any
> other articles that suit your needs, although Hilary once mentioned a
> presentation at SQLPASS or TECHNET conference that sounds as though it'd
be
> useful to you. He posted the name of the presenter but unfortunately
Idon't
> recall it. No doubt he'll post a reply here.
> Rgds,
> Paul Ibison, SQL Server MVP, WWW.Replicationanswers.Com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Yes this is the conference proceedings I was thinking of
but apologies as I was thinking the presentations were
about MSDE rather than CE.
Rgds,
Paul Ibison, SQL Server MVP, WWW.Replicationanswers.Com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Actually, I believe I have heard of an installation with 4500 subscribers
where they used republishing; I think its Barnes and Noble or Ticketmaster,
and IIRC it was with SQL 7.
I urge you to contact PSS for more information on this, and how to deploy
such a topology.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:016301c4ba68$ebf53fa0$a401280a@.phx.gbl...
> Yes this is the conference proceedings I was thinking of
> but apologies as I was thinking the presentations were
> about MSDE rather than CE.
> Rgds,
> Paul Ibison, SQL Server MVP, WWW.Replicationanswers.Com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Thanks folks,
I do foresee that we'll be working with PSS (and most likely with MS
Consulting Svs also). This posting was intended to help me start to
understand whether we'd be pushing the envelope into areas in which other
have feared to tread (or have been badly burnt). Hopefully MS will be able
to help us understand how B&N and/or Tickermaster had planned their
topologies etc.
Many thanks for your help - and looking forward to your Merge Replication
book becoming available.
Lee.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23%23AhvfouEHA.3972@.TK2MSFTNGP15.phx.gbl...
> Actually, I believe I have heard of an installation with 4500 subscribers
> where they used republishing; I think its Barnes and Noble or
> Ticketmaster,
> and IIRC it was with SQL 7.
> I urge you to contact PSS for more information on this, and how to deploy
> such a topology.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
> news:016301c4ba68$ebf53fa0$a401280a@.phx.gbl...
>
|||Lee,
once you've got it all set up, if you can find the time
please post up a bit of general info on the topology
choices etc.
Rgds,
Paul Ibison, SQL Server MVP, WWW.Replicationanswers.Com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Monday, February 20, 2012

Merge Replication and MSDE 2000

Hello..I am going to implement Merge Replication with MSDE 2000.
please let me know how many users MSDE 2000 can burden the workload. It
will degrade the preformance if more than 5 concurrent user will start
work on it concurrently.
What is the procedure in order to implement merge Replication on MSDE
2000.
Pls help me as soon as possible
Thanks in Advance,
Jayesh Patel
(jayesh@.infoworldpune.com)
its 8 simultaneous workloads. So if you are using connection pooling this
could mean many more users the 8, but it depends on what sort of work they
are doing. Work which takes a long time might mean you get throttling with 8
simultaneous connections. Work which completes in ms and work which takes
advantages of connection pooling could mean many more than 8 simultaneous
users.
To implement replication use any of the tutorials on the web, and run
profiler to capture the commands. Then apply these commands using osql.
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
"Jayesh" <dba.jayeshpatel@.gmail.com> wrote in message
news:1125318990.896170.122400@.g47g2000cwa.googlegr oups.com...
> Hello..I am going to implement Merge Replication with MSDE 2000.
> please let me know how many users MSDE 2000 can burden the workload. It
> will degrade the preformance if more than 5 concurrent user will start
> work on it concurrently.
> What is the procedure in order to implement merge Replication on MSDE
> 2000.
> Pls help me as soon as possible
> Thanks in Advance,
> Jayesh Patel
> (jayesh@.infoworldpune.com)
>
|||Thanks a lot for reply.
Can you guide me how to implement replication between SQL server and
MSDE ?
We have to setup Merge Replication between three continents.
1) asia
2)america
3) Europe
These 3 continents will be act as publisher and suscriber.
(by merging them)
But within one continent , there might be many more countries.
Country contains variuos city. City level database would be running on
MSDE.
Is it possible to replicate data this city level data with country as
well continent level.
Thanks in Advance,
Jayesh Patel