Monday, March 26, 2012
Replication Disrupting Other Access
is also used for our web applications. We need the replication for
disconnected computing using an MSDE database. The replication works
exceptionally well, however, we had to publish ID ranges on the tables
so that data could be merged with the server correctly. This has
caused a problem with our web based applications. Once the end of the
ID range is reached, our other applications cannot insert data into
the tables without resetting the ranges or removing replication.
Has anyone else seen this problem? If so, is there a good work-around
to allow both entities to co-exist using the same database? We would
like to avoid adding a significant amount of code/scripts to manage
this automatically. Would we be better off to use a snapshot method
of replication and insert data directly from that?
Thanks for any suggestions you may have.
Dan Broomall
Dan,
there are 2 ways I can think of:
you can use large ranges - so large in fact that no new ranges are required,
or you can select to manually manage the ranges and select a simple
algorithm that ensures there is never any overlap between publisher and
subscriber(s). EG if you have a publisher and a single subscriber, the
publisher could have a seed of 1 and increment of 2 while the subscriber has
a seed of 2 and increment of 2 - the publisher has odd identity values and
the subscriber evens.
HTH,
Paul Ibison
Friday, March 23, 2012
Replication Configuration?
Our website and sql database are hosted away from our offices and is updated via the web by customers and by us in our offices. However due to our slow internet connection we would like to bring a replication server into our office and have the two databases talk to each other when a change occurs.(Customers updating the public database and us update a local one).
I have seen sites mention circular replication is troublesome and may not work, is this the case or is it just a matter of correct configuration?
Any advice, tips etc would be appreciated.
Thanks
John
I guess u need a Transactional replication configured between the two server.
Two scenario u can have
1. Central publishers and many(as many as u wish) read only subscriber
2. Other case in which subscribers also get updated Immediate updating subscribers.
I guess u have a scenario where in both the server will get updated. u can go for transactional replication with immediate updating subscribers.
I see no issues in this and ofcourse correct configuration is must for anything u do with SQL Server.
|||
Also i have one more quick question..how frequent is update on the both the server?
if both server are frequently updated u should consider using merge replication instead of transactional replication with immediate updating subscription as immediate updating subscription is useful for only occasional changes on the subscribers.
|||
I posted this on a different thread, but I think it applys to you as well.
Here is a direct quote from BOL http://msdn2.microsoft.com/en-us/library/ms152570.aspx
The following types of replication and replication options allow you to make changes at a Subscriber and have those changes flow to the Publisher:
Merge replication
There are a large number of Subscribers.
Data is replicated to mobile users.
Replicated data is frequently updated at the Subscriber.
Data filtering is needed so that Subscribers receive different partitions of data.
Monday, March 12, 2012
replication / dmz
if have a firewall with 3 nic cards
- 1 for incoming
- 1 for intranet
- 1 for web app
so that intranet is isolated from the web server
its still possible "replication"
from the intra-net SQLServer to
web server ?
atte,
Hernn Castelo
UTN Buenos Aires
. . . . . . . . . . . . . . . . . . . . . . . . .
.Yes. As long as you can use TCP and Standard SQL Security.
287932 INF: TCP Ports Needed for Communication to SQL Server Through a
Firewall
http://support.microsoft.com/?id=287932
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
replication / dmz
if have a firewall with 3 nic cards
- 1 for incoming
- 1 for intranet
- 1 for web app
so that intranet is isolated from the web server
its still possible "replication"
from the intra-net SQLServer to
web server ?
atte,
Hernn Castelo
UTN Buenos Aires
.. . . . . . . . . . . . . . . . . . . . . . . . . .
Yes. As long as you can use TCP and Standard SQL Security.
287932 INF: TCP Ports Needed for Communication to SQL Server Through a
Firewall
http://support.microsoft.com/?id=287932
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
Saturday, February 25, 2012
Replicating twice
2005 and am replicating (merge via the web) from an intermediate box
which is also running 05. The intermediate box is replicating in some
fashion (unsure since it isn't under my control) from a SQL 2K box.
My issue is that when the job executes it says "Merge completed with no
data changes processed." even though the intermediate box has updated
data on it. Is this common? Is the answer so obvious that everyone is
laughing at me now?
Thanks
Jeremiah
It should work. How is your global priority configured? You might want to
check the conflict viewer to see if these conflicts are logged.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
"JC" <jbzcooper@.gmail.com> wrote in message
news:1141343267.632060.296050@.u72g2000cwu.googlegr oups.com...
>I have a question that google seems eerily quite on. I'm running SQL
> 2005 and am replicating (merge via the web) from an intermediate box
> which is also running 05. The intermediate box is replicating in some
> fashion (unsure since it isn't under my control) from a SQL 2K box.
> My issue is that when the job executes it says "Merge completed with no
> data changes processed." even though the intermediate box has updated
> data on it. Is this common? Is the answer so obvious that everyone is
> laughing at me now?
> Thanks
> Jeremiah
>
|||Jeremiah,
If I understand correctly, your SQL 2005 is subscribing from an intermediate
box, which subscribes from a SQL 2K server? Please note that for merge
replication, the publisher database version has be to newer than the
subscriber version, so basically SQL Server 2005 cannot be a subscriber of a
SQL 2000 publisher.
Yi Chen
"JC" <jbzcooper@.gmail.com> wrote in message
news:1141343267.632060.296050@.u72g2000cwu.googlegr oups.com...
>I have a question that google seems eerily quite on. I'm running SQL
> 2005 and am replicating (merge via the web) from an intermediate box
> which is also running 05. The intermediate box is replicating in some
> fashion (unsure since it isn't under my control) from a SQL 2K box.
> My issue is that when the job executes it says "Merge completed with no
> data changes processed." even though the intermediate box has updated
> data on it. Is this common? Is the answer so obvious that everyone is
> laughing at me now?
> Thanks
> Jeremiah
>
|||Are there any filters on the publisher that make the data not qualify for
the subscriber?
Hope that helps
--Mahesh
[ This posting is provided "as is" with no warranties and confers no
rights. ]
"JC" <jbzcooper@.gmail.com> wrote in message
news:1141343267.632060.296050@.u72g2000cwu.googlegr oups.com...
> I have a question that google seems eerily quite on. I'm running SQL
> 2005 and am replicating (merge via the web) from an intermediate box
> which is also running 05. The intermediate box is replicating in some
> fashion (unsure since it isn't under my control) from a SQL 2K box.
> My issue is that when the job executes it says "Merge completed with no
> data changes processed." even though the intermediate box has updated
> data on it. Is this common? Is the answer so obvious that everyone is
> laughing at me now?
> Thanks
> Jeremiah
>
Blog Archive
-
▼
2012
(501)
-
▼
March
(409)
- replication failed after restart
- replication failed after restart
- replication failed after restart
- replication failed after restart
- Replication failed
- Replication fail(register fail)
- replication fail
- Replication Expired subscription clean up job failed
- Replication errors - vicious circle
- Replication Errors
- Replication Errors
- Replication Errors
- Replication Errors
- Replication errors
- Replication Errors
- replication error? (somewhat urgent)
- Replication Error: 4138
- Replication error....
- Replication Error...
- Replication error with sqlserver mobile:A request ...
- replication error with oracle
- replication error while copy data
- Replication Error while Configuring Distributor
- Replication Error using Ras Connection win2003srv
- Replication error thrown during normal T-SQL proce...
- Replication Error process could not read file HEL...
- Replication error on tables with different owners
- replication error on script
- Replication error on a non-replicated DB?
- Replication error on a non-replicated DB?
- Replication error on a non-replicated DB?
- Replication Error of MS SQL server2k
- replication error message in SQL Server 2005 (June...
- replication error message in SQL Server 2005 (June...
- replication error message in SQL Server 2005 (June...
- Replication Error Message
- Replication Error in Visual Basic
- Replication Error in Store Procedure that is not i...
- Replication error in Snapshot publication
- Replication Error after Upgrade (7.0-2000)
- Replication error after installing SP3a
- replication error after database update
- Replication Error 28559
- Replication Error 28559
- Replication Error 28559
- Replication Error 28559
- Replication Error 28559
- Replication Error 28559
- Replication Error 28559
- Replication Error 28559
- Replication Error 28559
- Replication error 28037
- replication error 21258
- Replication ERROR 208: invalid object name 'syspub...
- Replication error 18482
- Replication Error 14113
- Replication error (old Snapshotfiles)
- Replication error --> General Network Error with 1...
- Replication Error - SharePoint 2007 DB
- Replication error - schema
- REPLICATION ERROR - retention-based meta data
- Replication error - can not retrieve column inform...
- replication error - agent is suspect
- replication error - agent is suspect
- replication error - agent is suspect
- Replication Error
- replication error
- Replication error
- Replication Error
- REPLICATION ERROR
- Replication Error
- replication error
- Replication Error
- Replication Error
- Replication Error
- Replication Error
- Replication error
- Replication error
- Replication Error
- replication error
- Replication Error
- Replication Error
- Replication error
- REPLICATION ERROR
- Replication Error
- Replication Error
- Replication Error
- Replication Error
- Replication enhancement in Yukon
- Replication enhancement in Yukon
- Replication enhancement in Yukon
- Replication encryption
- Replication Dynamic Filter SQL SERVER 2005 June CT...
- Replication down Log Shrinking
- Replication doesnt replicate
- Replication does not work properly
- Replication does not work after deleting the LDF f...
- Replication does not start
- Replication does not seem to work for rows inserte...
- Replication does detect Mirrored Source Fail Over
- Replication Distributor Version
- Replication Distributor Version
- Replication Distributor Job History is shocking!
- Replication Distributor
- replication distribution server agents keep time out
- Replication distribution cleanup error
- Replication Distribution Agent Does Not Start
- Replication Distribution Agent Does Not Start
- Replication Distribution Agent cpu continues to grow
- Replication Distribution Agent cpu continues to grow
- Replication Distribution Agent cpu continues to grow
- Replication Disrupting Other Access
- Replication Disaster - Help
- Replication Dilemma - Need a Solution/Ideas
- Replication Details
- Replication Design, Comments?
- Replication design issue.
- Replication design
- Replication design
- Replication deployment model - SQL Server 2005
- Replication deployment model
- Replication Deadlocks
- Replication Deadlocks
- Replication Deadlocks
- Replication Deadlock...I think
- Replication Deadlock
- Replication Datawarehousing
- Replication creates new triggers?
-
▼
March
(409)