I am currently trying to setup Transformation on a Transactional Publication.
When When I finish setting up all the transformation for the package and
click finish to save the DTS package I get the Message "SQL Server Enterprise
manager could not complete this operation." this message comes up when it is
in the "Adding task 1 of 1" phase in the Creating the DTS package for
replication wizard.
Any help would be greatly appriciated.
Thanks in advance.
Jeff Stokes
Hi Jeff:
Right click on Server name and click Properties. In the properties window,
click on Connections tab and check if "Enforce Distributed Transactions"
Checkbox is checked. If so, uncheck it and then recreate your publication.
HTH
"Jeff Stokes" wrote:
> I am currently trying to setup Transformation on a Transactional Publication.
> When When I finish setting up all the transformation for the package and
> click finish to save the DTS package I get the Message "SQL Server Enterprise
> manager could not complete this operation." this message comes up when it is
> in the "Adding task 1 of 1" phase in the Creating the DTS package for
> replication wizard.
> Any help would be greatly appriciated.
> Thanks in advance.
> Jeff Stokes
|||Mark,
Thanks for your response. I checked the server properties and "Enforce
Distributed Transactions" is unchecked. Any otherthoughts?
Jeff
Jeff Stokes
"Mark" wrote:
[vbcol=seagreen]
> Hi Jeff:
> Right click on Server name and click Properties. In the properties window,
> click on Connections tab and check if "Enforce Distributed Transactions"
> Checkbox is checked. If so, uncheck it and then recreate your publication.
> HTH
>
> "Jeff Stokes" wrote:
sql
Showing posts with label transactional. Show all posts
Showing posts with label transactional. Show all posts
Friday, March 30, 2012
Replication transcations
Hi All
I had stopped transactional replication for about 5 hours and now i have
restarted it. The replication is so slow. How can i calculate how many
transactions are left to be replicated? Both the log reader and distribution
agent are running although at times they time out.. I have tried to query the
table MSrepl_transcations but nothing makes sense to me.Thank you in advance.
query select * from distribution.dbo.msdistribution_status or execute
sp_browsereplcmds in the distribution database.
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
"MittyKom" <MittyKom@.discussions.microsoft.com> wrote in message
news:54BB99E9-1F10-4AE4-8747-3B99F27DE83B@.microsoft.com...
> Hi All
> I had stopped transactional replication for about 5 hours and now i have
> restarted it. The replication is so slow. How can i calculate how many
> transactions are left to be replicated? Both the log reader and
distribution
> agent are running although at times they time out.. I have tried to query
the
> table MSrepl_transcations but nothing makes sense to me.Thank you in
advance.
I had stopped transactional replication for about 5 hours and now i have
restarted it. The replication is so slow. How can i calculate how many
transactions are left to be replicated? Both the log reader and distribution
agent are running although at times they time out.. I have tried to query the
table MSrepl_transcations but nothing makes sense to me.Thank you in advance.
query select * from distribution.dbo.msdistribution_status or execute
sp_browsereplcmds in the distribution database.
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
"MittyKom" <MittyKom@.discussions.microsoft.com> wrote in message
news:54BB99E9-1F10-4AE4-8747-3B99F27DE83B@.microsoft.com...
> Hi All
> I had stopped transactional replication for about 5 hours and now i have
> restarted it. The replication is so slow. How can i calculate how many
> transactions are left to be replicated? Both the log reader and
distribution
> agent are running although at times they time out.. I have tried to query
the
> table MSrepl_transcations but nothing makes sense to me.Thank you in
advance.
Replication to establish warm Standby
Using SQL Sever 2k. Anyone seeing a problem with use of transactional replic
ation to establish warm Standby Server. The only problem that I am aware of
would be user defined data types.Aleksandar,
Transactional replication can be used for the purpose you want. I would,
possibly, caution that replication appears to be one of the SQL Server more
"delicate" abilities in that, from my experience, it is "prone" to breaking
under a number of circumstances. However, in a reasonably stable
environment, you should probably be okay. Do keep in mind that transactional
replication will not by itself automatically failover to the replicated
server if your primary server goes down for any reason. If your primary
server does fail, the replicated server will require manual intervention in
order to allow your users to access it as if it were your primary server.
For a rather comprehensive list of options of maintaining database
availability, along with the associated pro's, con's and costs, I recommend
picking up a copy of the book "Microsoft SQL Server 2000 Resource Kit" from
Microsoft Press. Part 4, "Availability" covers the topic, I believe, better
than any other write up than I've encountered to date.
Chief Tenaya
"Aleksandar" <anonymous@.discussions.microsoft.com> wrote in message
news:2867FCF4-6B75-45CD-ABF3-0F338C4FE5B9@.microsoft.com...
> Using SQL Sever 2k. Anyone seeing a problem with use of transactional
replication to establish warm Standby Server. The only problem that I am
aware of would be user defined data types.
>|||Aleksander
Log shipping is much more suitable for maintaining a warm spare for a number
of reasons.
1. Log shipping copies all transactions that occur on the database. Replicat
ion copies all the data in articles you have set up. This means that when th
e database changes you do nothing with log shipping, with replication you ne
ed to remember to update th
e relevent articles.
2. With log shipping, you can place the warm database in loading state, no '
accidental' updating can occur. With replication the database is still avail
able.
3. With log shipping if anything happens with any of your logs so that they
can not be loaded you will get errors in your log shipping alerting you to t
he fact there is a problem. With replication if far any reason any of the da
ta is not updated on the wa
rm database you will not know.
4. With log shipping you have controlled updates to your warm database. You
always know where you are. Replication does the updates behind the scenes, a
lthough fast it is not instant. If you loose the system you can not be sure
how up to date the data is.
Hope this helps
John|||Log Shipping it is. This is exactly what I was looking for. Great help, than
k you for replay.sql
ation to establish warm Standby Server. The only problem that I am aware of
would be user defined data types.Aleksandar,
Transactional replication can be used for the purpose you want. I would,
possibly, caution that replication appears to be one of the SQL Server more
"delicate" abilities in that, from my experience, it is "prone" to breaking
under a number of circumstances. However, in a reasonably stable
environment, you should probably be okay. Do keep in mind that transactional
replication will not by itself automatically failover to the replicated
server if your primary server goes down for any reason. If your primary
server does fail, the replicated server will require manual intervention in
order to allow your users to access it as if it were your primary server.
For a rather comprehensive list of options of maintaining database
availability, along with the associated pro's, con's and costs, I recommend
picking up a copy of the book "Microsoft SQL Server 2000 Resource Kit" from
Microsoft Press. Part 4, "Availability" covers the topic, I believe, better
than any other write up than I've encountered to date.
Chief Tenaya
"Aleksandar" <anonymous@.discussions.microsoft.com> wrote in message
news:2867FCF4-6B75-45CD-ABF3-0F338C4FE5B9@.microsoft.com...
> Using SQL Sever 2k. Anyone seeing a problem with use of transactional
replication to establish warm Standby Server. The only problem that I am
aware of would be user defined data types.
>|||Aleksander
Log shipping is much more suitable for maintaining a warm spare for a number
of reasons.
1. Log shipping copies all transactions that occur on the database. Replicat
ion copies all the data in articles you have set up. This means that when th
e database changes you do nothing with log shipping, with replication you ne
ed to remember to update th
e relevent articles.
2. With log shipping, you can place the warm database in loading state, no '
accidental' updating can occur. With replication the database is still avail
able.
3. With log shipping if anything happens with any of your logs so that they
can not be loaded you will get errors in your log shipping alerting you to t
he fact there is a problem. With replication if far any reason any of the da
ta is not updated on the wa
rm database you will not know.
4. With log shipping you have controlled updates to your warm database. You
always know where you are. Replication does the updates behind the scenes, a
lthough fast it is not instant. If you loose the system you can not be sure
how up to date the data is.
Hope this helps
John|||Log Shipping it is. This is exactly what I was looking for. Great help, than
k you for replay.sql
Replication to establish warm Standby
Using SQL Sever 2k. Anyone seeing a problem with use of transactional replication to establish warm Standby Server. The only problem that I am aware of would be user defined data types.
Aleksandar,
Transactional replication can be used for the purpose you want. I would,
possibly, caution that replication appears to be one of the SQL Server more
"delicate" abilities in that, from my experience, it is "prone" to breaking
under a number of circumstances. However, in a reasonably stable
environment, you should probably be okay. Do keep in mind that transactional
replication will not by itself automatically failover to the replicated
server if your primary server goes down for any reason. If your primary
server does fail, the replicated server will require manual intervention in
order to allow your users to access it as if it were your primary server.
For a rather comprehensive list of options of maintaining database
availability, along with the associated pro's, con's and costs, I recommend
picking up a copy of the book "Microsoft SQL Server 2000 Resource Kit" from
Microsoft Press. Part 4, "Availability" covers the topic, I believe, better
than any other write up than I've encountered to date.
Chief Tenaya
"Aleksandar" <anonymous@.discussions.microsoft.com> wrote in message
news:2867FCF4-6B75-45CD-ABF3-0F338C4FE5B9@.microsoft.com...
> Using SQL Sever 2k. Anyone seeing a problem with use of transactional
replication to establish warm Standby Server. The only problem that I am
aware of would be user defined data types.
>
|||Aleksander
Log shipping is much more suitable for maintaining a warm spare for a number of reasons.
1. Log shipping copies all transactions that occur on the database. Replication copies all the data in articles you have set up. This means that when the database changes you do nothing with log shipping, with replication you need to remember to update th
e relevent articles.
2. With log shipping, you can place the warm database in loading state, no 'accidental' updating can occur. With replication the database is still available.
3. With log shipping if anything happens with any of your logs so that they can not be loaded you will get errors in your log shipping alerting you to the fact there is a problem. With replication if far any reason any of the data is not updated on the wa
rm database you will not know.
4. With log shipping you have controlled updates to your warm database. You always know where you are. Replication does the updates behind the scenes, although fast it is not instant. If you loose the system you can not be sure how up to date the data is.
Hope this helps
John
|||Log Shipping it is. This is exactly what I was looking for. Great help, thank you for replay.
Aleksandar,
Transactional replication can be used for the purpose you want. I would,
possibly, caution that replication appears to be one of the SQL Server more
"delicate" abilities in that, from my experience, it is "prone" to breaking
under a number of circumstances. However, in a reasonably stable
environment, you should probably be okay. Do keep in mind that transactional
replication will not by itself automatically failover to the replicated
server if your primary server goes down for any reason. If your primary
server does fail, the replicated server will require manual intervention in
order to allow your users to access it as if it were your primary server.
For a rather comprehensive list of options of maintaining database
availability, along with the associated pro's, con's and costs, I recommend
picking up a copy of the book "Microsoft SQL Server 2000 Resource Kit" from
Microsoft Press. Part 4, "Availability" covers the topic, I believe, better
than any other write up than I've encountered to date.
Chief Tenaya
"Aleksandar" <anonymous@.discussions.microsoft.com> wrote in message
news:2867FCF4-6B75-45CD-ABF3-0F338C4FE5B9@.microsoft.com...
> Using SQL Sever 2k. Anyone seeing a problem with use of transactional
replication to establish warm Standby Server. The only problem that I am
aware of would be user defined data types.
>
|||Aleksander
Log shipping is much more suitable for maintaining a warm spare for a number of reasons.
1. Log shipping copies all transactions that occur on the database. Replication copies all the data in articles you have set up. This means that when the database changes you do nothing with log shipping, with replication you need to remember to update th
e relevent articles.
2. With log shipping, you can place the warm database in loading state, no 'accidental' updating can occur. With replication the database is still available.
3. With log shipping if anything happens with any of your logs so that they can not be loaded you will get errors in your log shipping alerting you to the fact there is a problem. With replication if far any reason any of the data is not updated on the wa
rm database you will not know.
4. With log shipping you have controlled updates to your warm database. You always know where you are. Replication does the updates behind the scenes, although fast it is not instant. If you loose the system you can not be sure how up to date the data is.
Hope this helps
John
|||Log Shipping it is. This is exactly what I was looking for. Great help, thank you for replay.
Replication to establish warm Standby
Using SQL Sever 2k. Anyone seeing a problem with use of transactional replication to establish warm Standby Server. The only problem that I am aware of would be user defined data types.Aleksandar,
Transactional replication can be used for the purpose you want. I would,
possibly, caution that replication appears to be one of the SQL Server more
"delicate" abilities in that, from my experience, it is "prone" to breaking
under a number of circumstances. However, in a reasonably stable
environment, you should probably be okay. Do keep in mind that transactional
replication will not by itself automatically failover to the replicated
server if your primary server goes down for any reason. If your primary
server does fail, the replicated server will require manual intervention in
order to allow your users to access it as if it were your primary server.
For a rather comprehensive list of options of maintaining database
availability, along with the associated pro's, con's and costs, I recommend
picking up a copy of the book "Microsoft SQL Server 2000 Resource Kit" from
Microsoft Press. Part 4, "Availability" covers the topic, I believe, better
than any other write up than I've encountered to date.
Chief Tenaya
"Aleksandar" <anonymous@.discussions.microsoft.com> wrote in message
news:2867FCF4-6B75-45CD-ABF3-0F338C4FE5B9@.microsoft.com...
> Using SQL Sever 2k. Anyone seeing a problem with use of transactional
replication to establish warm Standby Server. The only problem that I am
aware of would be user defined data types.
>|||Log Shipping it is. This is exactly what I was looking for. Great help, thank you for replay.
Transactional replication can be used for the purpose you want. I would,
possibly, caution that replication appears to be one of the SQL Server more
"delicate" abilities in that, from my experience, it is "prone" to breaking
under a number of circumstances. However, in a reasonably stable
environment, you should probably be okay. Do keep in mind that transactional
replication will not by itself automatically failover to the replicated
server if your primary server goes down for any reason. If your primary
server does fail, the replicated server will require manual intervention in
order to allow your users to access it as if it were your primary server.
For a rather comprehensive list of options of maintaining database
availability, along with the associated pro's, con's and costs, I recommend
picking up a copy of the book "Microsoft SQL Server 2000 Resource Kit" from
Microsoft Press. Part 4, "Availability" covers the topic, I believe, better
than any other write up than I've encountered to date.
Chief Tenaya
"Aleksandar" <anonymous@.discussions.microsoft.com> wrote in message
news:2867FCF4-6B75-45CD-ABF3-0F338C4FE5B9@.microsoft.com...
> Using SQL Sever 2k. Anyone seeing a problem with use of transactional
replication to establish warm Standby Server. The only problem that I am
aware of would be user defined data types.
>|||Log Shipping it is. This is exactly what I was looking for. Great help, thank you for replay.
Replication to different table structure
I had set up some Snapshot and Transactional replication in the past but
would like to see if following is possible.
Is it possible to do either snapshot or transactionl replication between
tables with 2 different table structure? Lets say I have a tableA which i
like to replicate to TableB. But TableB has few additional columns from
tableA. Also, How about datatype difference on some columns between TableA
and TableB?
Version is Sql server 2000 sp4.
I appreciate your reply.
Filtering (vertical) can be used to restrict the columns. Where the
datatypes are different there are a few posibilities, but replicating
indexed views is quite straightforward.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
|||Have a look at this:
http://www.dbazine.com/sql/sql-articles/cotter1
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
"James" <kush@.brandes.com> wrote in message
news:uc8kggmaHHA.808@.TK2MSFTNGP04.phx.gbl...
>I had set up some Snapshot and Transactional replication in the past but
>would like to see if following is possible.
> Is it possible to do either snapshot or transactionl replication between
> tables with 2 different table structure? Lets say I have a tableA which i
> like to replicate to TableB. But TableB has few additional columns from
> tableA. Also, How about datatype difference on some columns between TableA
> and TableB?
> Version is Sql server 2000 sp4.
> I appreciate your reply.
>
|||http://www.dbazine.com/sql/sql-articles/cotter1
I just get a page prompting to renew the domain name... do you have another
link Hilary?
"Hilary Cotter" wrote:
> Have a look at this:
> http://www.dbazine.com/sql/sql-articles/cotter1
> --
> 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
>
> "James" <kush@.brandes.com> wrote in message
> news:uc8kggmaHHA.808@.TK2MSFTNGP04.phx.gbl...
>
>
|||Wow, I just checked this link and it was valid, and now I get the domain
expired as well
Have a look at this:
http://209.85.165.104/search?q=cache:4m4CLStYfWIJ:www.dbazine.com/sql/sql-articles/cotter1+http://www.dbazine.com/sql/sql-articles/cotter1&hl=en&ct=clnk&cd=1&gl=us
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
"Steve Hall" <SteveHall@.discussions.microsoft.com> wrote in message
news:4E6A1EF4-E639-4ED7-B4BA-F6DEE42F016E@.microsoft.com...[vbcol=seagreen]
> http://www.dbazine.com/sql/sql-articles/cotter1
> I just get a page prompting to renew the domain name... do you have
> another
> link Hilary?
>
> "Hilary Cotter" wrote:
|||Thanks Hilary,
I got the same text minus the images from google cache and
waybackmachine.org. Just got finished reading it and a few of your other
articles on dbdirections.com.
Steve
"Hilary Cotter" wrote:
> Wow, I just checked this link and it was valid, and now I get the domain
> expired as well
> Have a look at this:
> http://209.85.165.104/search?q=cache:4m4CLStYfWIJ:www.dbazine.com/sql/sql-articles/cotter1+http://www.dbazine.com/sql/sql-articles/cotter1&hl=en&ct=clnk&cd=1&gl=us
> --
> 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
>
> "Steve Hall" <SteveHall@.discussions.microsoft.com> wrote in message
> news:4E6A1EF4-E639-4ED7-B4BA-F6DEE42F016E@.microsoft.com...
>
>
|||Thanks Hilary! Helpful article.
I am still having some trouble though. I am trying to implement some of the
suggestion from that Article for Case 2 (where subscriber has more columns
than publisher) and I am using Snapshot replication only.
Suggestion1: I precreated the table on the subscriber and provide default
value for the column (which doesn't exist on publisher), but when the
distributer agent runs it gives me following error:
"Unexpected EOF encountered in BCP data-file"
Suggestion 2: "Supply a value for those columns in the replication stored
procedure". Where can I find this SP? It doesn't exist on Subscription
database.
Suggestion 3: "Index View". haven't tried yet. going to try very soon.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:eoznYMuaHHA.4396@.TK2MSFTNGP06.phx.gbl...
> Have a look at this:
> http://www.dbazine.com/sql/sql-articles/cotter1
> --
> 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
>
> "James" <kush@.brandes.com> wrote in message
> news:uc8kggmaHHA.808@.TK2MSFTNGP04.phx.gbl...
>
|||Could you post the table schema on the publisher and what you want it to
look like on the subscriber?
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
"James" <kush@.brandes.com> wrote in message
news:ux0YSQwaHHA.1388@.TK2MSFTNGP05.phx.gbl...
> Thanks Hilary! Helpful article.
> I am still having some trouble though. I am trying to implement some of
> the suggestion from that Article for Case 2 (where subscriber has more
> columns than publisher) and I am using Snapshot replication only.
> Suggestion1: I precreated the table on the subscriber and provide default
> value for the column (which doesn't exist on publisher), but when the
> distributer agent runs it gives me following error:
> "Unexpected EOF encountered in BCP data-file"
> Suggestion 2: "Supply a value for those columns in the replication stored
> procedure". Where can I find this SP? It doesn't exist on Subscription
> database.
> Suggestion 3: "Index View". haven't tried yet. going to try very soon.
>
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:eoznYMuaHHA.4396@.TK2MSFTNGP06.phx.gbl...
>
would like to see if following is possible.
Is it possible to do either snapshot or transactionl replication between
tables with 2 different table structure? Lets say I have a tableA which i
like to replicate to TableB. But TableB has few additional columns from
tableA. Also, How about datatype difference on some columns between TableA
and TableB?
Version is Sql server 2000 sp4.
I appreciate your reply.
Filtering (vertical) can be used to restrict the columns. Where the
datatypes are different there are a few posibilities, but replicating
indexed views is quite straightforward.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
|||Have a look at this:
http://www.dbazine.com/sql/sql-articles/cotter1
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
"James" <kush@.brandes.com> wrote in message
news:uc8kggmaHHA.808@.TK2MSFTNGP04.phx.gbl...
>I had set up some Snapshot and Transactional replication in the past but
>would like to see if following is possible.
> Is it possible to do either snapshot or transactionl replication between
> tables with 2 different table structure? Lets say I have a tableA which i
> like to replicate to TableB. But TableB has few additional columns from
> tableA. Also, How about datatype difference on some columns between TableA
> and TableB?
> Version is Sql server 2000 sp4.
> I appreciate your reply.
>
|||http://www.dbazine.com/sql/sql-articles/cotter1
I just get a page prompting to renew the domain name... do you have another
link Hilary?
"Hilary Cotter" wrote:
> Have a look at this:
> http://www.dbazine.com/sql/sql-articles/cotter1
> --
> 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
>
> "James" <kush@.brandes.com> wrote in message
> news:uc8kggmaHHA.808@.TK2MSFTNGP04.phx.gbl...
>
>
|||Wow, I just checked this link and it was valid, and now I get the domain
expired as well
Have a look at this:
http://209.85.165.104/search?q=cache:4m4CLStYfWIJ:www.dbazine.com/sql/sql-articles/cotter1+http://www.dbazine.com/sql/sql-articles/cotter1&hl=en&ct=clnk&cd=1&gl=us
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
"Steve Hall" <SteveHall@.discussions.microsoft.com> wrote in message
news:4E6A1EF4-E639-4ED7-B4BA-F6DEE42F016E@.microsoft.com...[vbcol=seagreen]
> http://www.dbazine.com/sql/sql-articles/cotter1
> I just get a page prompting to renew the domain name... do you have
> another
> link Hilary?
>
> "Hilary Cotter" wrote:
|||Thanks Hilary,
I got the same text minus the images from google cache and
waybackmachine.org. Just got finished reading it and a few of your other
articles on dbdirections.com.
Steve
"Hilary Cotter" wrote:
> Wow, I just checked this link and it was valid, and now I get the domain
> expired as well
> Have a look at this:
> http://209.85.165.104/search?q=cache:4m4CLStYfWIJ:www.dbazine.com/sql/sql-articles/cotter1+http://www.dbazine.com/sql/sql-articles/cotter1&hl=en&ct=clnk&cd=1&gl=us
> --
> 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
>
> "Steve Hall" <SteveHall@.discussions.microsoft.com> wrote in message
> news:4E6A1EF4-E639-4ED7-B4BA-F6DEE42F016E@.microsoft.com...
>
>
|||Thanks Hilary! Helpful article.
I am still having some trouble though. I am trying to implement some of the
suggestion from that Article for Case 2 (where subscriber has more columns
than publisher) and I am using Snapshot replication only.
Suggestion1: I precreated the table on the subscriber and provide default
value for the column (which doesn't exist on publisher), but when the
distributer agent runs it gives me following error:
"Unexpected EOF encountered in BCP data-file"
Suggestion 2: "Supply a value for those columns in the replication stored
procedure". Where can I find this SP? It doesn't exist on Subscription
database.
Suggestion 3: "Index View". haven't tried yet. going to try very soon.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:eoznYMuaHHA.4396@.TK2MSFTNGP06.phx.gbl...
> Have a look at this:
> http://www.dbazine.com/sql/sql-articles/cotter1
> --
> 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
>
> "James" <kush@.brandes.com> wrote in message
> news:uc8kggmaHHA.808@.TK2MSFTNGP04.phx.gbl...
>
|||Could you post the table schema on the publisher and what you want it to
look like on the subscriber?
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
"James" <kush@.brandes.com> wrote in message
news:ux0YSQwaHHA.1388@.TK2MSFTNGP05.phx.gbl...
> Thanks Hilary! Helpful article.
> I am still having some trouble though. I am trying to implement some of
> the suggestion from that Article for Case 2 (where subscriber has more
> columns than publisher) and I am using Snapshot replication only.
> Suggestion1: I precreated the table on the subscriber and provide default
> value for the column (which doesn't exist on publisher), but when the
> distributer agent runs it gives me following error:
> "Unexpected EOF encountered in BCP data-file"
> Suggestion 2: "Supply a value for those columns in the replication stored
> procedure". Where can I find this SP? It doesn't exist on Subscription
> database.
> Suggestion 3: "Index View". haven't tried yet. going to try very soon.
>
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:eoznYMuaHHA.4396@.TK2MSFTNGP06.phx.gbl...
>
Wednesday, March 28, 2012
Replication subscription validation in Microsoft SQL Server 2000
Hi,
I have set up a pull transactional replication using 2 machines: one
Publisher and the other Distributor-Subscriber.
Both are running Microsoft SQL Server 2000 SP3. They have different OSes
though: the Publisher has Microsoft Windows Server 2003 SP1 but the
Distributor-Subscriber has Microsoft Windows 2000 Advanced Server SP4.
I have one publication of all objects in a database and one subscriber to
all articles in that publication.
Will the successful result of sp_publication_validation be the sufficient
evidence to make an assumption that the Publication and Subscription
databases are identical if we don't use any text or binary data types? Does
it always need to be a check with checksums?
Many thanks,
Oskar
Oskar,
sp_publication_validation is only a basic comparison. Binary checksums are
needed to be certain, or in some cases I use SQL Data Compare. This can be
useful if you want to manually synchronize the data then reinitialize with
nosync ie you can't afford to reinitialize.
If you are using merge replication, there are some circumstances when rows
won't get replicated (basically those cases where triggers don't fire) and
these cases will be caught by your simple rowcount. Using more arcane
settings like -EXCHANGETYPE can result in the same rowcount but different
data, and while the binary checksum would catch this behaviour the rowcount
might miss it.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
I have set up a pull transactional replication using 2 machines: one
Publisher and the other Distributor-Subscriber.
Both are running Microsoft SQL Server 2000 SP3. They have different OSes
though: the Publisher has Microsoft Windows Server 2003 SP1 but the
Distributor-Subscriber has Microsoft Windows 2000 Advanced Server SP4.
I have one publication of all objects in a database and one subscriber to
all articles in that publication.
Will the successful result of sp_publication_validation be the sufficient
evidence to make an assumption that the Publication and Subscription
databases are identical if we don't use any text or binary data types? Does
it always need to be a check with checksums?
Many thanks,
Oskar
Oskar,
sp_publication_validation is only a basic comparison. Binary checksums are
needed to be certain, or in some cases I use SQL Data Compare. This can be
useful if you want to manually synchronize the data then reinitialize with
nosync ie you can't afford to reinitialize.
If you are using merge replication, there are some circumstances when rows
won't get replicated (basically those cases where triggers don't fire) and
these cases will be caught by your simple rowcount. Using more arcane
settings like -EXCHANGETYPE can result in the same rowcount but different
data, and while the binary checksum would catch this behaviour the rowcount
might miss it.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
Replication subscription validation in Microsoft SQL Server 2000
Hi,
I have set up a pull transactional replication using 2 machines: one
Publisher and the other Distributor-Subscriber.
Both are running Microsoft SQL Server 2000 SP3. They have different OSes
though: the Publisher has Microsoft Windows Server 2003 SP1 but the
Distributor-Subscriber has Microsoft Windows 2000 Advanced Server SP4.
I have one publication of all objects in a database and one subscriber to
all articles in that publication.
Will the successful result of sp_publication_validation be the sufficient
evidence to make an assumption that the Publication and Subscription
databases are identical if we don't use any text or binary data types? Does
it always need to be a check with checksums?
Many thanks,
OskarOskar,
sp_publication_validation is only a basic comparison. Binary checksums are
needed to be certain, or in some cases I use SQL Data Compare. This can be
useful if you want to manually synchronize the data then reinitialize with
nosync ie you can't afford to reinitialize.
If you are using merge replication, there are some circumstances when rows
won't get replicated (basically those cases where triggers don't fire) and
these cases will be caught by your simple rowcount. Using more arcane
settings like -EXCHANGETYPE can result in the same rowcount but different
data, and while the binary checksum would catch this behaviour the rowcount
might miss it.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
I have set up a pull transactional replication using 2 machines: one
Publisher and the other Distributor-Subscriber.
Both are running Microsoft SQL Server 2000 SP3. They have different OSes
though: the Publisher has Microsoft Windows Server 2003 SP1 but the
Distributor-Subscriber has Microsoft Windows 2000 Advanced Server SP4.
I have one publication of all objects in a database and one subscriber to
all articles in that publication.
Will the successful result of sp_publication_validation be the sufficient
evidence to make an assumption that the Publication and Subscription
databases are identical if we don't use any text or binary data types? Does
it always need to be a check with checksums?
Many thanks,
OskarOskar,
sp_publication_validation is only a basic comparison. Binary checksums are
needed to be certain, or in some cases I use SQL Data Compare. This can be
useful if you want to manually synchronize the data then reinitialize with
nosync ie you can't afford to reinitialize.
If you are using merge replication, there are some circumstances when rows
won't get replicated (basically those cases where triggers don't fire) and
these cases will be caught by your simple rowcount. Using more arcane
settings like -EXCHANGETYPE can result in the same rowcount but different
data, and while the binary checksum would catch this behaviour the rowcount
might miss it.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
Replication subscription validation in Microsoft SQL Server 2000
Hi,
I have set up a pull transactional replication using 2 machines: one
Publisher and the other Distributor-Subscriber.
Both are running Microsoft SQL Server 2000 SP3. They have different OSes
though: the Publisher has Microsoft Windows Server 2003 SP1 but the
Distributor-Subscriber has Microsoft Windows 2000 Advanced Server SP4.
I have one publication of all objects in a database and one subscriber to
all articles in that publication.
Will the successful result of sp_publication_validation be the sufficient
evidence to make an assumption that the Publication and Subscription
databases are identical if we don't use any text or binary data types? Does
it always need to be a check with checksums?
--
Many thanks,
OskarOskar,
sp_publication_validation is only a basic comparison. Binary checksums are
needed to be certain, or in some cases I use SQL Data Compare. This can be
useful if you want to manually synchronize the data then reinitialize with
nosync ie you can't afford to reinitialize.
If you are using merge replication, there are some circumstances when rows
won't get replicated (basically those cases where triggers don't fire) and
these cases will be caught by your simple rowcount. Using more arcane
settings like -EXCHANGETYPE can result in the same rowcount but different
data, and while the binary checksum would catch this behaviour the rowcount
might miss it.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
I have set up a pull transactional replication using 2 machines: one
Publisher and the other Distributor-Subscriber.
Both are running Microsoft SQL Server 2000 SP3. They have different OSes
though: the Publisher has Microsoft Windows Server 2003 SP1 but the
Distributor-Subscriber has Microsoft Windows 2000 Advanced Server SP4.
I have one publication of all objects in a database and one subscriber to
all articles in that publication.
Will the successful result of sp_publication_validation be the sufficient
evidence to make an assumption that the Publication and Subscription
databases are identical if we don't use any text or binary data types? Does
it always need to be a check with checksums?
--
Many thanks,
OskarOskar,
sp_publication_validation is only a basic comparison. Binary checksums are
needed to be certain, or in some cases I use SQL Data Compare. This can be
useful if you want to manually synchronize the data then reinitialize with
nosync ie you can't afford to reinitialize.
If you are using merge replication, there are some circumstances when rows
won't get replicated (basically those cases where triggers don't fire) and
these cases will be caught by your simple rowcount. Using more arcane
settings like -EXCHANGETYPE can result in the same rowcount but different
data, and while the binary checksum would catch this behaviour the rowcount
might miss it.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
Replication subscriber views, locks and blocks.
Quick question, do views on the subscription server create locking and
blocking issues?
I have 2 servers set-up with transactional replication. We have scheduled
reports running on the subscribing server, most of those reports using views.
The views seem to create performance, locking and blocking issues.
Thank you very much in advance.
Message posted via http://www.droptable.com
Yes they can. You might want to consider using indexed views depending on
your version and edition of SQL Server.
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
"Frank N via droptable.com" <u10790@.uwe> wrote in message
news:5a40019273826@.uwe...
> Quick question, do views on the subscription server create locking and
> blocking issues?
> I have 2 servers set-up with transactional replication. We have scheduled
> reports running on the subscribing server, most of those reports using
> views.
> The views seem to create performance, locking and blocking issues.
> Thank you very much in advance.
> --
> Message posted via http://www.droptable.com
|||A (non-dirty) read of data takes out a shared lock and this is not peculiar
to views. If these views are used for reporting purposes, you might want to
have a replica to be used for reporting eg using transactional replication,
or database mirroring with database snapshots.
Alternatively you could allow dirty reads (NOLOCK) on the tables in
question - depends on the business constraints.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||So if we place (nolock) hints on all the tables in all the views that should
eliminate the locking?
Paul Ibison wrote:
>A (non-dirty) read of data takes out a shared lock and this is not peculiar
>to views. If these views are used for reporting purposes, you might want to
>have a replica to be used for reporting eg using transactional replication,
>or database mirroring with database snapshots.
>Alternatively you could allow dirty reads (NOLOCK) on the tables in
>question - depends on the business constraints.
>Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
Message posted via http://www.droptable.com
|||Yes - or more easily set the transaction isolation-level to read
uncommitted.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
blocking issues?
I have 2 servers set-up with transactional replication. We have scheduled
reports running on the subscribing server, most of those reports using views.
The views seem to create performance, locking and blocking issues.
Thank you very much in advance.
Message posted via http://www.droptable.com
Yes they can. You might want to consider using indexed views depending on
your version and edition of SQL Server.
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
"Frank N via droptable.com" <u10790@.uwe> wrote in message
news:5a40019273826@.uwe...
> Quick question, do views on the subscription server create locking and
> blocking issues?
> I have 2 servers set-up with transactional replication. We have scheduled
> reports running on the subscribing server, most of those reports using
> views.
> The views seem to create performance, locking and blocking issues.
> Thank you very much in advance.
> --
> Message posted via http://www.droptable.com
|||A (non-dirty) read of data takes out a shared lock and this is not peculiar
to views. If these views are used for reporting purposes, you might want to
have a replica to be used for reporting eg using transactional replication,
or database mirroring with database snapshots.
Alternatively you could allow dirty reads (NOLOCK) on the tables in
question - depends on the business constraints.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||So if we place (nolock) hints on all the tables in all the views that should
eliminate the locking?
Paul Ibison wrote:
>A (non-dirty) read of data takes out a shared lock and this is not peculiar
>to views. If these views are used for reporting purposes, you might want to
>have a replica to be used for reporting eg using transactional replication,
>or database mirroring with database snapshots.
>Alternatively you could allow dirty reads (NOLOCK) on the tables in
>question - depends on the business constraints.
>Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
Message posted via http://www.droptable.com
|||Yes - or more easily set the transaction isolation-level to read
uncommitted.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Replication stops after server reboot??
Hi,
I have transactional replication set up between two dedicated servers. Server A is the PDC and Server B is a BDC (they are both Win2000 boxes). Both the servers are brand new, and replaced the two that were running like clock work (replication wise) for the last 12 months. I never had this problem with the old servers...
When the servers are shut down (as the case was a couple of weeks back with a power failure) or just recently when they were move to another room. Both servers boot up at the same time. Server B (which is the server holding the db being replicated) boots quicker and as a result replication fails and is then 'sucessfully stopped'. Unless I am aware of the server being rebooted and can monitor this potential problem, within 2 days the logfile grows to large and everything comes to a crashing halt.
I just remove replication, truncate and shrink the log, reset replication and we're away... BUT I really need to know why it is happening in the first place. I figure there must be a setting that I have forgotten about or something.
Both servers are Win2000 (SP4) and SQL2000(SP3a).
Any help would be appreciated.
Thanks
CasperHave you tried restarting replication agents before removing replication? Make sure sql agent is set up as auto start. I assume the distribution db are sitting on the publisher (server B). When dist server couldn't find subscriber (box A), it will auto stop all distribution agetns, which caused the distribution db to grow.
You can set up a job monitoring log reader and dist agent to see if they are stopped. Then run sp_start_job to automatically restart them.|||When the log is full everything comes to a crashing halt. That's basically the reason why. You need to either backup the log or truncate it more often, at least once a day. Shrink it if need be. You really don't have to uninstall replicate to dump the log and shrink the log file. You can truncate the log and shrink it with replication running.|||Joejcheng - yes I already do that, the transaction log is backed up and truncated every hour. The problem was when replication stops the transaction log grows (because it is retaining all transactions waiting to be replicated).
Richard - thank you! I had not even thought about just restarting the jobs (doh!). However the 2 times this has happened the transaction log has been around 15GB and the database controls a production system and they cannot afford to be offline for long (I usually just get them up and running and then reset replication the following evening). Can I start the jobs and have them continue work whilst it is pushing all the transactions across - or would it just never catch up because of the size of the transaction log?
And also thank you for mentioning sp_start_job - I will most certainly put that in place.
However I would still really like to know why this is happening in the first place, but I think I may have worked it out...
I set up replication from a script created on the previous system. One of the replication owners is XXXSqlAdmin, however in the new system this user is just SQLAdmin. I have noticed the error raised by this in the past (ie XXXSqlAdmin does not exist in this db), but didn't think it would cause any problems. But now I think I was very wrong. I changed the script before I ran it last night, no errors were returned. I will monitor the DB for the next week and then we will do a test where we shut down the servers and boot server B well before we boot server A.
Thanks again for your help, much appreciated!
Casper :)
I have transactional replication set up between two dedicated servers. Server A is the PDC and Server B is a BDC (they are both Win2000 boxes). Both the servers are brand new, and replaced the two that were running like clock work (replication wise) for the last 12 months. I never had this problem with the old servers...
When the servers are shut down (as the case was a couple of weeks back with a power failure) or just recently when they were move to another room. Both servers boot up at the same time. Server B (which is the server holding the db being replicated) boots quicker and as a result replication fails and is then 'sucessfully stopped'. Unless I am aware of the server being rebooted and can monitor this potential problem, within 2 days the logfile grows to large and everything comes to a crashing halt.
I just remove replication, truncate and shrink the log, reset replication and we're away... BUT I really need to know why it is happening in the first place. I figure there must be a setting that I have forgotten about or something.
Both servers are Win2000 (SP4) and SQL2000(SP3a).
Any help would be appreciated.
Thanks
CasperHave you tried restarting replication agents before removing replication? Make sure sql agent is set up as auto start. I assume the distribution db are sitting on the publisher (server B). When dist server couldn't find subscriber (box A), it will auto stop all distribution agetns, which caused the distribution db to grow.
You can set up a job monitoring log reader and dist agent to see if they are stopped. Then run sp_start_job to automatically restart them.|||When the log is full everything comes to a crashing halt. That's basically the reason why. You need to either backup the log or truncate it more often, at least once a day. Shrink it if need be. You really don't have to uninstall replicate to dump the log and shrink the log file. You can truncate the log and shrink it with replication running.|||Joejcheng - yes I already do that, the transaction log is backed up and truncated every hour. The problem was when replication stops the transaction log grows (because it is retaining all transactions waiting to be replicated).
Richard - thank you! I had not even thought about just restarting the jobs (doh!). However the 2 times this has happened the transaction log has been around 15GB and the database controls a production system and they cannot afford to be offline for long (I usually just get them up and running and then reset replication the following evening). Can I start the jobs and have them continue work whilst it is pushing all the transactions across - or would it just never catch up because of the size of the transaction log?
And also thank you for mentioning sp_start_job - I will most certainly put that in place.
However I would still really like to know why this is happening in the first place, but I think I may have worked it out...
I set up replication from a script created on the previous system. One of the replication owners is XXXSqlAdmin, however in the new system this user is just SQLAdmin. I have noticed the error raised by this in the past (ie XXXSqlAdmin does not exist in this db), but didn't think it would cause any problems. But now I think I was very wrong. I changed the script before I ran it last night, no errors were returned. I will monitor the DB for the next week and then we will do a test where we shut down the servers and boot server B well before we boot server A.
Thanks again for your help, much appreciated!
Casper :)
Replication status check
What is the best way to determine if transactional replication is alive and
well? I would like to know if the snapshots are completed, the articles are
being published, and that replicated transactions are being processed by the
subscriber.
Bob b
run sp_MSenum_snapshot
look for a status of 2, which means complete.
to check that replicated commands are being processed issue the below
select * from distribution.dbo.msdistribution_status
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
"bob b" <bobb@.discussions.microsoft.com> wrote in message
news:677477A8-E644-439A-BE90-96B1D94E0B14@.microsoft.com...
> What is the best way to determine if transactional replication is alive
and
> well? I would like to know if the snapshots are completed, the articles
are
> being published, and that replicated transactions are being processed by
the
> subscriber.
> --
> Bob b
well? I would like to know if the snapshots are completed, the articles are
being published, and that replicated transactions are being processed by the
subscriber.
Bob b
run sp_MSenum_snapshot
look for a status of 2, which means complete.
to check that replicated commands are being processed issue the below
select * from distribution.dbo.msdistribution_status
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
"bob b" <bobb@.discussions.microsoft.com> wrote in message
news:677477A8-E644-439A-BE90-96B1D94E0B14@.microsoft.com...
> What is the best way to determine if transactional replication is alive
and
> well? I would like to know if the snapshots are completed, the articles
are
> being published, and that replicated transactions are being processed by
the
> subscriber.
> --
> Bob b
Monday, March 26, 2012
replication setup help
Shailesh,
transactional replication over a VPN would be my choice,
with your home as a pull subscriber. If you haven't got
the VPN set up, then you can still use SQL Server logins
for synchronization and FTP for initialization.
This article should help in the configuration:
http://support.microsoft.com/?id=321822
Rgds,
Paul Ibison
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Paul Ibison wrote:
> Shailesh,
> transactional replication over a VPN would be my choice,
> with your home as a pull subscriber. If you haven't got
> the VPN set up, then you can still use SQL Server logins
> for synchronization and FTP for initialization.
> This article should help in the configuration:
> http://support.microsoft.com/?id=321822
> Rgds,
> Paul Ibison
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
There are so many options and issues. I don't think there's any way
to avoid spending a week just to read through everything and
understand it all...
sql
transactional replication over a VPN would be my choice,
with your home as a pull subscriber. If you haven't got
the VPN set up, then you can still use SQL Server logins
for synchronization and FTP for initialization.
This article should help in the configuration:
http://support.microsoft.com/?id=321822
Rgds,
Paul Ibison
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Paul Ibison wrote:
> Shailesh,
> transactional replication over a VPN would be my choice,
> with your home as a pull subscriber. If you haven't got
> the VPN set up, then you can still use SQL Server logins
> for synchronization and FTP for initialization.
> This article should help in the configuration:
> http://support.microsoft.com/?id=321822
> Rgds,
> Paul Ibison
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
There are so many options and issues. I don't think there's any way
to avoid spending a week just to read through everything and
understand it all...
sql
replication setup
Hi,
I am using SQL 2005 server. If I want to replicate a table from A
server to B server, using transactional publication, do I setup a
publication in A server with article of the table and then setup a
subscription in B server? Am I over-simplifying or there is some thing I
need to set up? Cause now it is not changing the record in B server when I
change the record in A server.
Please help. Thanks.
Michael - have you set this up already? If the table is on Server B then I
assume that the initialization has worked and therefore the snapshot and
distribution agent have worked. Can you see if the distribution agent is on
a schedule and if it is, start the relevant job to send the recent
transactions over. Assuming this is the case, you might want to set the
agent to run continuously to reduce latency.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
I am using SQL 2005 server. If I want to replicate a table from A
server to B server, using transactional publication, do I setup a
publication in A server with article of the table and then setup a
subscription in B server? Am I over-simplifying or there is some thing I
need to set up? Cause now it is not changing the record in B server when I
change the record in A server.
Please help. Thanks.
Michael - have you set this up already? If the table is on Server B then I
assume that the initialization has worked and therefore the snapshot and
distribution agent have worked. Can you see if the distribution agent is on
a schedule and if it is, start the relevant job to send the recent
transactions over. Assuming this is the case, you might want to set the
agent to run continuously to reduce latency.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
Replication schedule
How can I check if the transactional replication is set up in continuous
mode or on a set time such as replicate once every hour ? Thanks
Have a look at the distribution agent's job schedule.
Rgds,
Paul Ibison
mode or on a set time such as replicate once every hour ? Thanks
Have a look at the distribution agent's job schedule.
Rgds,
Paul Ibison
Replication schedule
Here's my problem
I have setup a transactional replication with a push
subscription, I schedule it to run every hour, every think
works good, however when the schedule start synchronizing
it never stops so its not stating at the next hour, I have
to manually click stop synchronizing and then it starts
again.
Please help!!!
Expand Replicaiton Monitor, expand the agents folder, expand the
distribution agents folder, right click on your distribution agent and
select agent properties. then select the steps tab. Click on Run Agent and
then click on the Edit button.
in the command section press the end key, remove the -Continuous statement,
click apply, ok, apply ok, right click on your distribution agent again and
select start agent.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"amw" <amw@.1800wheelchair.com> wrote in message
news:0b7b01c48b80$61dbdc50$a301280a@.phx.gbl...
> Here's my problem
> I have setup a transactional replication with a push
> subscription, I schedule it to run every hour, every think
> works good, however when the schedule start synchronizing
> it never stops so its not stating at the next hour, I have
> to manually click stop synchronizing and then it starts
> again.
> Please help!!!
|||Thanks for your reply
I follow your answer but I don't see the -Continuous
statement on the distribution agent schedule, but I see it
in the log reader agent schedule, should I remove it from
there? I think the log reader should run continuous.
>--Original Message--
>Expand Replicaiton Monitor, expand the agents folder,
expand the
>distribution agents folder, right click on your
distribution agent and
>select agent properties. then select the steps tab. Click
on Run Agent and
>then click on the Edit button.
>in the command section press the end key, remove the -
Continuous statement,
>click apply, ok, apply ok, right click on your
distribution agent again and[vbcol=seagreen]
>select start agent.
>--
>Hilary Cotter
>Looking for a book on SQL Server replication?
>http://www.nwsu.com/0974973602.html
>
>"amw" <amw@.1800wheelchair.com> wrote in message
>news:0b7b01c48b80$61dbdc50$a301280a@.phx.gbl...
think[vbcol=seagreen]
synchronizing[vbcol=seagreen]
have
>
>.
>
|||don't touch the log reader!
If it is not present in your distribution agent, you have a lot of data to
send to your subscriber. In time the job will finish.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"amw" <amw@.1800wheelchair.com> wrote in message
news:0c2801c48b8f$7ad28e20$a501280a@.phx.gbl...[vbcol=seagreen]
> Thanks for your reply
> I follow your answer but I don't see the -Continuous
> statement on the distribution agent schedule, but I see it
> in the log reader agent schedule, should I remove it from
> there? I think the log reader should run continuous.
> expand the
> distribution agent and
> on Run Agent and
> Continuous statement,
> distribution agent again and
> think
> synchronizing
> have
I have setup a transactional replication with a push
subscription, I schedule it to run every hour, every think
works good, however when the schedule start synchronizing
it never stops so its not stating at the next hour, I have
to manually click stop synchronizing and then it starts
again.
Please help!!!
Expand Replicaiton Monitor, expand the agents folder, expand the
distribution agents folder, right click on your distribution agent and
select agent properties. then select the steps tab. Click on Run Agent and
then click on the Edit button.
in the command section press the end key, remove the -Continuous statement,
click apply, ok, apply ok, right click on your distribution agent again and
select start agent.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"amw" <amw@.1800wheelchair.com> wrote in message
news:0b7b01c48b80$61dbdc50$a301280a@.phx.gbl...
> Here's my problem
> I have setup a transactional replication with a push
> subscription, I schedule it to run every hour, every think
> works good, however when the schedule start synchronizing
> it never stops so its not stating at the next hour, I have
> to manually click stop synchronizing and then it starts
> again.
> Please help!!!
|||Thanks for your reply
I follow your answer but I don't see the -Continuous
statement on the distribution agent schedule, but I see it
in the log reader agent schedule, should I remove it from
there? I think the log reader should run continuous.
>--Original Message--
>Expand Replicaiton Monitor, expand the agents folder,
expand the
>distribution agents folder, right click on your
distribution agent and
>select agent properties. then select the steps tab. Click
on Run Agent and
>then click on the Edit button.
>in the command section press the end key, remove the -
Continuous statement,
>click apply, ok, apply ok, right click on your
distribution agent again and[vbcol=seagreen]
>select start agent.
>--
>Hilary Cotter
>Looking for a book on SQL Server replication?
>http://www.nwsu.com/0974973602.html
>
>"amw" <amw@.1800wheelchair.com> wrote in message
>news:0b7b01c48b80$61dbdc50$a301280a@.phx.gbl...
think[vbcol=seagreen]
synchronizing[vbcol=seagreen]
have
>
>.
>
|||don't touch the log reader!
If it is not present in your distribution agent, you have a lot of data to
send to your subscriber. In time the job will finish.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"amw" <amw@.1800wheelchair.com> wrote in message
news:0c2801c48b8f$7ad28e20$a501280a@.phx.gbl...[vbcol=seagreen]
> Thanks for your reply
> I follow your answer but I don't see the -Continuous
> statement on the distribution agent schedule, but I see it
> in the log reader agent schedule, should I remove it from
> there? I think the log reader should run continuous.
> expand the
> distribution agent and
> on Run Agent and
> Continuous statement,
> distribution agent again and
> think
> synchronizing
> have
Replication Scene Consultant
Hi Guys!
I work in Govern Department Bank. We just have many experiences about
Replication, meanly Transactional.
All evolution about Client-Server architecture in the past, make some choice:
?Many Distribution application at many sites located in many cities linked
through Wan (frame relay – 98 kbps to 512 kbps)
?Each site has one Domain controller Server, with SQL 2000 Standard, 2
processor and 1 Gbyte of Memory. Many Databases that belongs each other to
your own application and share some tables.
Now we need put all information together at central Server. Let’s take a look:
?We have many databases : Ddes950, Ddes033, etc
?Many tables that become at each other Database needs to plus at one table,
I mean, if one table at site Ag002,Ag003, Ag004,…, call T999xxx01, we need to
add to one central. The distributed table has different PK row at each other!
Transactional replication can do this administration?
How can I do that without truncate central table after every snapshot
initialize schema?
How can I control synchronisms and snapshots ?
How can I control schema changes?
Could Microsoft replication support many publication to one subscriber?
What about Oracle solutions? Can we plus together with Microsoft SQL Server?
Please, if anyone has any information or Scene like that situation, please
send me and share these with us!!!
Thanks
Krisnamourt
Message posted via http://www.droptable.com
It sounds like a multiple publishers and central subscriber topology is what
you need. Here is an article on setting it up etc :
http://www.replicationanswers.com/CentralSubscriberArticle.asp
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Paul,
It's more complicated!
I follow that article example, and make some experiences like that, but here
I have more to worry:
The total table is something like 100.
The table at publisher just have many rows, I mean, some table have 3
millions rows or more, so the Initial SnapShot will required at firts charge,
so How can I coordinate this ? That's the point!!!
I do another experience with snapshot files manipulations, so the syncronism
isn't the problem, but Initial snapshot schema is...
Sds!
Paul Ibison wrote:
>It sounds like a multiple publishers and central subscriber topology is what
>you need. Here is an article on setting it up etc :
>http://www.replicationanswers.com/CentralSubscriberArticle.asp
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
Message posted via http://www.droptable.com
|||Paul,
It's more complicated!
I follow that article example, and make some experiences like that, but here
I have more to worry:
The total table is something like 100.
The table at publisher just have many rows, I mean, some table have 3
millions rows or more, so the Initial SnapShot will required at firts charge,
so How can I coordinate this ? That's the point!!!
I do another experience with snapshot files manipulations, so the syncronism
isn't the problem, but Initial snapshot schema is...
Sds!
Paul Ibison wrote:
>It sounds like a multiple publishers and central subscriber topology is what
>you need. Here is an article on setting it up etc :
>http://www.replicationanswers.com/CentralSubscriberArticle.asp
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
Message posted via http://www.droptable.com
|||Paul,
It's more complicated!
I follow that article example, and make some experiences like that, but here
I have more to worry:
The total table is something like 100.
The table at publisher just have many rows, I mean, some table have 3
millions rows or more, so the Initial SnapShot will required at firts charge,
so How can I coordinate this ? That's the point!!!
I do another experience with snapshot files manipulations, so the syncronism
isn't the problem, but Initial snapshot schema is...
Sds!
Paul Ibison wrote:
>It sounds like a multiple publishers and central subscriber topology is what
>you need. Here is an article on setting it up etc :
>http://www.replicationanswers.com/CentralSubscriberArticle.asp
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums.aspx/sql-server-replication/200612/1
|||I'm not too sure which part of your setup is more complicated than that in
the article.
You have a lot of tables and a lot of records but the methodology should be
exactly the same, assuming the data is all partitioned. Are you saying that
the data isn't partitioned ie there is some overlap of data across the
various publishers?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Let me explain more:
When I create Publisher and subscriber with “keep the existing table
unchanged”, we need initial load too.
When I maked for one publisher ok, but when another publisher make the same,
It don′t plus row one by one, It truncate the table and plus its own snapshot.
THAT’S THE POINT!
Every time , the process make the same!
What's the magic? Please , tell me
I would need to do the load process in separated way?, I mean:
1.I’ll create the publish and subscriber , without any load.
2.Stop the distribution agent and let log reader agent run
3.Start and finish the load by DTS or BCP.
4.Start distribution agent again. Pretty !!!
If I’ll do in this way, work fine, but It’s more hard to do and to manage.
Sds!
Kris
Paul Ibison wrote:
>I'm not too sure which part of your setup is more complicated than that in
>the article.
>You have a lot of tables and a lot of records but the methodology should be
>exactly the same, assuming the data is all partitioned. Are you saying that
>the data isn't partitioned ie there is some overlap of data across the
>various publishers?
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
Message posted via http://www.droptable.com
|||Let me explain more:
When I create Publisher and subscriber with “keep the existing table
unchanged”, we need initial load too.
When I maked for one publisher ok, but when another publisher make the same,
It don′t plus row one by one, It truncate the table and plus its own snapshot.
THAT’S THE POINT!
Every time , the process make the same!
What's the magic? Please , tell me
I would need to do the load process in separated way?, I mean:
1.I’ll create the publish and subscriber , without any load.
2.Stop the distribution agent and let log reader agent run
3.Start and finish the load by DTS or BCP.
4.Start distribution agent again. Pretty !!!
If I’ll do in this way, work fine, but It’s more hard to do and to manage.
Sds!
Kris
Paul Ibison wrote:
>I'm not too sure which part of your setup is more complicated than that in
>the article.
>You have a lot of tables and a lot of records but the methodology should be
>exactly the same, assuming the data is all partitioned. Are you saying that
>the data isn't partitioned ie there is some overlap of data across the
>various publishers?
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums.aspx/sql-server-replication/200612/1
|||Let me explain more:
When I create Publisher and subscriber with “keep the existing table
unchanged”, we need initial load too.
When I maked for one publisher ok, but when another publisher make the same,
It don′t plus row one by one, It truncate the table and plus its own snapshot.
THAT’S THE POINT!
Every time , the process make the same!
What's the magic? Please , tell me
I would need to do the load process in separated way?, I mean:
1.I’ll create the publish and subscriber , without any load.
2.Stop the distribution agent and let log reader agent run
3.Start and finish the load by DTS or BCP.
4.Start distribution agent again. Pretty !!!
If I’ll do in this way, work fine, but It’s more hard to do and to manage.
Sds!
Kris
Paul Ibison wrote:
>I'm not too sure which part of your setup is more complicated than that in
>the article.
>You have a lot of tables and a lot of records but the methodology should be
>exactly the same, assuming the data is all partitioned. Are you saying that
>the data isn't partitioned ie there is some overlap of data across the
>various publishers?
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums.aspx/sql-server-replication/200612/1
|||I still think something is set up incorrectly as this can work fine. The
initial publication has article properties which are the default ie it uses
a 'drop table' as the initial script. The subsequent publications use the
option to "keep the existing table unchanged". Run the snapshots for these
subsequent publications without subscribing to test - there should be no
drop statement or truncate or delete statements in the snapshot folder and
the data should still be in BCP data files like usual. If you have something
different to this (ie a drop etc) then please double-check the article
properties as something is seriously awry. If you have an article set up
with "keep the existing table unchanged" and yet there is a
drop/truncate/delete, please script up your publication and table and I'd
like to reproduce it.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
I work in Govern Department Bank. We just have many experiences about
Replication, meanly Transactional.
All evolution about Client-Server architecture in the past, make some choice:
?Many Distribution application at many sites located in many cities linked
through Wan (frame relay – 98 kbps to 512 kbps)
?Each site has one Domain controller Server, with SQL 2000 Standard, 2
processor and 1 Gbyte of Memory. Many Databases that belongs each other to
your own application and share some tables.
Now we need put all information together at central Server. Let’s take a look:
?We have many databases : Ddes950, Ddes033, etc
?Many tables that become at each other Database needs to plus at one table,
I mean, if one table at site Ag002,Ag003, Ag004,…, call T999xxx01, we need to
add to one central. The distributed table has different PK row at each other!
Transactional replication can do this administration?
How can I do that without truncate central table after every snapshot
initialize schema?
How can I control synchronisms and snapshots ?
How can I control schema changes?
Could Microsoft replication support many publication to one subscriber?
What about Oracle solutions? Can we plus together with Microsoft SQL Server?
Please, if anyone has any information or Scene like that situation, please
send me and share these with us!!!
Thanks
Krisnamourt
Message posted via http://www.droptable.com
It sounds like a multiple publishers and central subscriber topology is what
you need. Here is an article on setting it up etc :
http://www.replicationanswers.com/CentralSubscriberArticle.asp
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Paul,
It's more complicated!
I follow that article example, and make some experiences like that, but here
I have more to worry:
The total table is something like 100.
The table at publisher just have many rows, I mean, some table have 3
millions rows or more, so the Initial SnapShot will required at firts charge,
so How can I coordinate this ? That's the point!!!
I do another experience with snapshot files manipulations, so the syncronism
isn't the problem, but Initial snapshot schema is...
Sds!
Paul Ibison wrote:
>It sounds like a multiple publishers and central subscriber topology is what
>you need. Here is an article on setting it up etc :
>http://www.replicationanswers.com/CentralSubscriberArticle.asp
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
Message posted via http://www.droptable.com
|||Paul,
It's more complicated!
I follow that article example, and make some experiences like that, but here
I have more to worry:
The total table is something like 100.
The table at publisher just have many rows, I mean, some table have 3
millions rows or more, so the Initial SnapShot will required at firts charge,
so How can I coordinate this ? That's the point!!!
I do another experience with snapshot files manipulations, so the syncronism
isn't the problem, but Initial snapshot schema is...
Sds!
Paul Ibison wrote:
>It sounds like a multiple publishers and central subscriber topology is what
>you need. Here is an article on setting it up etc :
>http://www.replicationanswers.com/CentralSubscriberArticle.asp
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
Message posted via http://www.droptable.com
|||Paul,
It's more complicated!
I follow that article example, and make some experiences like that, but here
I have more to worry:
The total table is something like 100.
The table at publisher just have many rows, I mean, some table have 3
millions rows or more, so the Initial SnapShot will required at firts charge,
so How can I coordinate this ? That's the point!!!
I do another experience with snapshot files manipulations, so the syncronism
isn't the problem, but Initial snapshot schema is...
Sds!
Paul Ibison wrote:
>It sounds like a multiple publishers and central subscriber topology is what
>you need. Here is an article on setting it up etc :
>http://www.replicationanswers.com/CentralSubscriberArticle.asp
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums.aspx/sql-server-replication/200612/1
|||I'm not too sure which part of your setup is more complicated than that in
the article.
You have a lot of tables and a lot of records but the methodology should be
exactly the same, assuming the data is all partitioned. Are you saying that
the data isn't partitioned ie there is some overlap of data across the
various publishers?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Let me explain more:
When I create Publisher and subscriber with “keep the existing table
unchanged”, we need initial load too.
When I maked for one publisher ok, but when another publisher make the same,
It don′t plus row one by one, It truncate the table and plus its own snapshot.
THAT’S THE POINT!
Every time , the process make the same!
What's the magic? Please , tell me
I would need to do the load process in separated way?, I mean:
1.I’ll create the publish and subscriber , without any load.
2.Stop the distribution agent and let log reader agent run
3.Start and finish the load by DTS or BCP.
4.Start distribution agent again. Pretty !!!
If I’ll do in this way, work fine, but It’s more hard to do and to manage.
Sds!
Kris
Paul Ibison wrote:
>I'm not too sure which part of your setup is more complicated than that in
>the article.
>You have a lot of tables and a lot of records but the methodology should be
>exactly the same, assuming the data is all partitioned. Are you saying that
>the data isn't partitioned ie there is some overlap of data across the
>various publishers?
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
Message posted via http://www.droptable.com
|||Let me explain more:
When I create Publisher and subscriber with “keep the existing table
unchanged”, we need initial load too.
When I maked for one publisher ok, but when another publisher make the same,
It don′t plus row one by one, It truncate the table and plus its own snapshot.
THAT’S THE POINT!
Every time , the process make the same!
What's the magic? Please , tell me
I would need to do the load process in separated way?, I mean:
1.I’ll create the publish and subscriber , without any load.
2.Stop the distribution agent and let log reader agent run
3.Start and finish the load by DTS or BCP.
4.Start distribution agent again. Pretty !!!
If I’ll do in this way, work fine, but It’s more hard to do and to manage.
Sds!
Kris
Paul Ibison wrote:
>I'm not too sure which part of your setup is more complicated than that in
>the article.
>You have a lot of tables and a lot of records but the methodology should be
>exactly the same, assuming the data is all partitioned. Are you saying that
>the data isn't partitioned ie there is some overlap of data across the
>various publishers?
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums.aspx/sql-server-replication/200612/1
|||Let me explain more:
When I create Publisher and subscriber with “keep the existing table
unchanged”, we need initial load too.
When I maked for one publisher ok, but when another publisher make the same,
It don′t plus row one by one, It truncate the table and plus its own snapshot.
THAT’S THE POINT!
Every time , the process make the same!
What's the magic? Please , tell me
I would need to do the load process in separated way?, I mean:
1.I’ll create the publish and subscriber , without any load.
2.Stop the distribution agent and let log reader agent run
3.Start and finish the load by DTS or BCP.
4.Start distribution agent again. Pretty !!!
If I’ll do in this way, work fine, but It’s more hard to do and to manage.
Sds!
Kris
Paul Ibison wrote:
>I'm not too sure which part of your setup is more complicated than that in
>the article.
>You have a lot of tables and a lot of records but the methodology should be
>exactly the same, assuming the data is all partitioned. Are you saying that
>the data isn't partitioned ie there is some overlap of data across the
>various publishers?
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums.aspx/sql-server-replication/200612/1
|||I still think something is set up incorrectly as this can work fine. The
initial publication has article properties which are the default ie it uses
a 'drop table' as the initial script. The subsequent publications use the
option to "keep the existing table unchanged". Run the snapshots for these
subsequent publications without subscribing to test - there should be no
drop statement or truncate or delete statements in the snapshot folder and
the data should still be in BCP data files like usual. If you have something
different to this (ie a drop etc) then please double-check the article
properties as something is seriously awry. If you have an article set up
with "keep the existing table unchanged" and yet there is a
drop/truncate/delete, please script up your publication and table and I'd
like to reproduce it.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
Replication scenario question...Merge or Transactional?
The situation I am faced with is we have a web application supported by a SQL
2000(sp4) database that resides on a limited bandwidth network. Our
distributed users are constantly complaining of "slow" response times. Our
local users have no such complaints. Some of our leadership has suggested
sending a SQL server/IIS server to the remote location and using some type of
replication to synchronize the data between these boxes. The requirements
are for minimal latency and concurrent updating of data. The leadership also
want this solution to be completely automated (little or no supervision of
the replication process) and as with everything we do they want it right away
(we're talking days, not weeks). I am very new to replication and have read
through the BOL section and am in the process of reading Hillary Cotter's
book. I am leaning toward an implementation of Merge Replication but I am
unsure if this is the right solution. Any advice or informed opinions would
be greatly appreciated.
There is no concurrent replication option ie each solution will have a degree
of latency. If you use merge then you can select from a variety of conflict
resolvers and easily work offline. This might be your best option. There are
alternatives - queued updating subscribers, immediate updating subscribers
and bidirectional transactional replication. Do you have BLOBS in the table?
Are the subscribers always connected? Should they be able to continue if not
connected? These questions will clarify and narrow down the options a bit.
Whichever option you select, don't rush - you'll need time to configure it in
a test environment to establish a set of protocols (change management, error
handling...) and to simply verify that it all works for your situation.
HTH,
Paul Ibison
"Dave Stokes" wrote:
> The situation I am faced with is we have a web application supported by a SQL
> 2000(sp4) database that resides on a limited bandwidth network. Our
> distributed users are constantly complaining of "slow" response times. Our
> local users have no such complaints. Some of our leadership has suggested
> sending a SQL server/IIS server to the remote location and using some type of
> replication to synchronize the data between these boxes. The requirements
> are for minimal latency and concurrent updating of data. The leadership also
> want this solution to be completely automated (little or no supervision of
> the replication process) and as with everything we do they want it right away
> (we're talking days, not weeks). I am very new to replication and have read
> through the BOL section and am in the process of reading Hillary Cotter's
> book. I am leaning toward an implementation of Merge Replication but I am
> unsure if this is the right solution. Any advice or informed opinions would
> be greatly appreciated.
2000(sp4) database that resides on a limited bandwidth network. Our
distributed users are constantly complaining of "slow" response times. Our
local users have no such complaints. Some of our leadership has suggested
sending a SQL server/IIS server to the remote location and using some type of
replication to synchronize the data between these boxes. The requirements
are for minimal latency and concurrent updating of data. The leadership also
want this solution to be completely automated (little or no supervision of
the replication process) and as with everything we do they want it right away
(we're talking days, not weeks). I am very new to replication and have read
through the BOL section and am in the process of reading Hillary Cotter's
book. I am leaning toward an implementation of Merge Replication but I am
unsure if this is the right solution. Any advice or informed opinions would
be greatly appreciated.
There is no concurrent replication option ie each solution will have a degree
of latency. If you use merge then you can select from a variety of conflict
resolvers and easily work offline. This might be your best option. There are
alternatives - queued updating subscribers, immediate updating subscribers
and bidirectional transactional replication. Do you have BLOBS in the table?
Are the subscribers always connected? Should they be able to continue if not
connected? These questions will clarify and narrow down the options a bit.
Whichever option you select, don't rush - you'll need time to configure it in
a test environment to establish a set of protocols (change management, error
handling...) and to simply verify that it all works for your situation.
HTH,
Paul Ibison
"Dave Stokes" wrote:
> The situation I am faced with is we have a web application supported by a SQL
> 2000(sp4) database that resides on a limited bandwidth network. Our
> distributed users are constantly complaining of "slow" response times. Our
> local users have no such complaints. Some of our leadership has suggested
> sending a SQL server/IIS server to the remote location and using some type of
> replication to synchronize the data between these boxes. The requirements
> are for minimal latency and concurrent updating of data. The leadership also
> want this solution to be completely automated (little or no supervision of
> the replication process) and as with everything we do they want it right away
> (we're talking days, not weeks). I am very new to replication and have read
> through the BOL section and am in the process of reading Hillary Cotter's
> book. I am leaning toward an implementation of Merge Replication but I am
> unsure if this is the right solution. Any advice or informed opinions would
> be greatly appreciated.
Friday, March 23, 2012
replication question!
Hi,
How do i truncate transaction log when the transactional replication is in place?
Thanks in advance.You don't, you back it up.
How do i truncate transaction log when the transactional replication is in place?
Thanks in advance.You don't, you back it up.
Replication Question
Hello everyone,
We are desperately wanting to perform transactional replication from a Sybase 12.5 Databse to an SQL server 2000 database. Unfortuneately we cannot migrate the entire Sybase system to SQL server!! Bascially we want to replicate a small subset of the tables from the Sybase database to a SQL server where we can manipulate this isolated data...
Any suggestuions on wether this is possible, and what new software products we may need, will be greatly appreciated.
Thank you
Chris
Moving this thread to the Replication Forum. Hopefully they can answer your question.
-Jeffrey
|||SQL Server 2000 doesn't support hetero as publisher yet. SQL Server 2005 support Hetero DB server as publisher and/or subscriber, but so far it only supports Oracle and DB2.
Thanks
Yunjing
|||Hi,
I have SQL Server 2005 Evaluation Edition for a POC for a client. ISQL2K5 Eval.Ed. doesn't support replication with Sybase. Do you have any idea how to set this up? I am recommneding SQL Server 2005 as a choice for their database for go live. They might not consider it if It will not support Sybase replication as their other functional systems are using Sybase as backend.
Any thoughts?
Thanks,
Mahesh.
|||there is a code sample which shows you how to write your own distributor interface for any provider. It is the samppub one in the code samples directory. You can find it in c:\Program Files\microsoft SqL Server\80\Tools\DevTools\Samples\SQLRepl\Samppub.
If you don't want to write your own interface you can use a product like Data Mirror.
You may also be able to use DTS to pull data locally into a staging table and then load it to your production tables.
|||You will have to write something yourself or use SSIS for this.
Subscribe to:
Posts (Atom)