Hi all,
does someone know any third party tool to manage MSSQLServer replication?
TIA
bruno reiter
Some of the monitoring tools out there (Quest, Idera, BMC, etc) have some
features which allow you to monitor replication, and replication jobs. They
don't allow you to create them.
You might want to look at these.
Exactly what features were you looking for? Easy Publication/Subscription
creating, Monitoring, Health monitoring, troubleshooting, etc.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"bruno reiter" <remove.this.br33@.bol.com.br> wrote in message
news:OJLUR2V$EHA.2600@.TK2MSFTNGP09.phx.gbl...
> Hi all,
> does someone know any third party tool to manage MSSQLServer replication?
> TIA
> bruno reiter
>
|||sorry a little late ;-)
looking for monitoring, visualization (topology), manage (start/stop
some/any at one time), visual stats simple/consolidate
one big problem is refresh for large repl and SEM freeze!
br
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:#O2eSqW$EHA.612@.TK2MSFTNGP09.phx.gbl...
> Some of the monitoring tools out there (Quest, Idera, BMC, etc) have some
> features which allow you to monitor replication, and replication jobs.
They[vbcol=seagreen]
> don't allow you to create them.
> You might want to look at these.
> Exactly what features were you looking for? Easy Publication/Subscription
> creating, Monitoring, Health monitoring, troubleshooting, etc.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> "bruno reiter" <remove.this.br33@.bol.com.br> wrote in message
> news:OJLUR2V$EHA.2600@.TK2MSFTNGP09.phx.gbl...
replication?
>
Showing posts with label party. Show all posts
Showing posts with label party. Show all posts
Friday, March 30, 2012
Replication to Mainframe Db2 OSZ
What would I need in order to setup replication between SQL2000 SP3 and MVS Subsystem running Db2 database . I mean, does it need any 3rd party tool or regular replication setup between SQL and Db2 is enoughAsk IBM for the DB2 Federated Server. If you have DB2 license, they should let you use that software free. It comes with a Replicator which allows you to replicate data from a different platform.
Friday, March 23, 2012
replication question
My situation:
I have a DB hosted by a 3rd party ISP. I want to replicate that DB locally
with in my office on our local server, mainly for backup purposes. I then
want to replicate that backup DB to a development DB for testing purposes.
Basically I'll have a LIVE DB hosted at the ISP. A backup version of the
LIVE
DB on our local server (peace of mind really) Then a development DB for
testing
purposes.
The Publisher will be the DB at the ISP.
Question 1. Is this a doable or a reasonable solution. I figured
transaction replication
from LIVE to BACKUP. Then Snapshot from BACKUP to
DEVELOPMENT.
It isn't absolutely necessary to have the most recent
data on the development db
since I will only be using it for testing purposes. But
would be nice to draw from
real data, almost live situations.
Question 2. Can a DB or server be both a Publisher and a Subscriber in this
case the BACKUP DB
would be both?
Thanks,
George
George,
this is possible - it is known as republishing. In your case my preference
would be to use merge between the live system and the Backup system, as it
is ideal for this sort of high latency situation. This would allow you to
have the Backup system as the publisher (with merge, the
publisher/subscriber metaphor doesn't especially hold), as you can then
control the configuration settings locally, and I'd have the live system as
a push subscriber. The other system is used as a testing system and the data
could become incompatible with replication from the Backup system, so I
wouldn't use replication to transfer to this box. Instead, I'd use a backup
and restore of the whole database - Backup to Test.
HTH,
Paul Ibison
|||I'd use transactional as
1) it offers better performance
2) it doesn't add a GUID key to every table.
The con of transactional replication is that you need a PK on every table you wish to replicate, and with republishing transactional is more sensitive to schema changes. By more sensitive I mean you have to drop your publications and subscriptions, make c
hanges and re-build again.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
sql
I have a DB hosted by a 3rd party ISP. I want to replicate that DB locally
with in my office on our local server, mainly for backup purposes. I then
want to replicate that backup DB to a development DB for testing purposes.
Basically I'll have a LIVE DB hosted at the ISP. A backup version of the
LIVE
DB on our local server (peace of mind really) Then a development DB for
testing
purposes.
The Publisher will be the DB at the ISP.
Question 1. Is this a doable or a reasonable solution. I figured
transaction replication
from LIVE to BACKUP. Then Snapshot from BACKUP to
DEVELOPMENT.
It isn't absolutely necessary to have the most recent
data on the development db
since I will only be using it for testing purposes. But
would be nice to draw from
real data, almost live situations.
Question 2. Can a DB or server be both a Publisher and a Subscriber in this
case the BACKUP DB
would be both?
Thanks,
George
George,
this is possible - it is known as republishing. In your case my preference
would be to use merge between the live system and the Backup system, as it
is ideal for this sort of high latency situation. This would allow you to
have the Backup system as the publisher (with merge, the
publisher/subscriber metaphor doesn't especially hold), as you can then
control the configuration settings locally, and I'd have the live system as
a push subscriber. The other system is used as a testing system and the data
could become incompatible with replication from the Backup system, so I
wouldn't use replication to transfer to this box. Instead, I'd use a backup
and restore of the whole database - Backup to Test.
HTH,
Paul Ibison
|||I'd use transactional as
1) it offers better performance
2) it doesn't add a GUID key to every table.
The con of transactional replication is that you need a PK on every table you wish to replicate, and with republishing transactional is more sensitive to schema changes. By more sensitive I mean you have to drop your publications and subscriptions, make c
hanges and re-build again.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
sql
Wednesday, March 21, 2012
Replication Problems
We are thinking to replicate a 'READ ONLY' database to an
off-site location by using a third party utility (We will
try to replicate from the warm backup server where we
restore transaction logs every hour from the original prod
server). Here are the two facts:
1- We don't want any performance decrease from the
original production server to replicate directly from the
prod server.
2- The third party utility is a file replication utility
which can replicate the whole database, differences only
e.t.c.
The problem seems to be, when the transaction log restore
starts, it kicks out all other users (SINGLE_USER,
RESTRICTED_USER).
Is there a way to restore the Transaction log without
cutting all the connections (Especially replication) to
the read-only database '
Thanks for any feedback....> Is there a way to restore the Transaction log without
> cutting all the connections (Especially replication) to
> the read-only database '
I'm afraid not.
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=...ublic.sqlserver
"John" <anonymous@.discussions.microsoft.com> wrote in message
news:b48d01c3ecfc$63946850$a101280a@.phx.gbl...
> We are thinking to replicate a 'READ ONLY' database to an
> off-site location by using a third party utility (We will
> try to replicate from the warm backup server where we
> restore transaction logs every hour from the original prod
> server). Here are the two facts:
> 1- We don't want any performance decrease from the
> original production server to replicate directly from the
> prod server.
> 2- The third party utility is a file replication utility
> which can replicate the whole database, differences only
> e.t.c.
> The problem seems to be, when the transaction log restore
> starts, it kicks out all other users (SINGLE_USER,
> RESTRICTED_USER).
> Is there a way to restore the Transaction log without
> cutting all the connections (Especially replication) to
> the read-only database '
> Thanks for any feedback....|||Change the schedule for the restore portion of transaction logshipping so th
at it doesn't conflict with the replication. Why are you using a third-part
y replication tool?sql
off-site location by using a third party utility (We will
try to replicate from the warm backup server where we
restore transaction logs every hour from the original prod
server). Here are the two facts:
1- We don't want any performance decrease from the
original production server to replicate directly from the
prod server.
2- The third party utility is a file replication utility
which can replicate the whole database, differences only
e.t.c.
The problem seems to be, when the transaction log restore
starts, it kicks out all other users (SINGLE_USER,
RESTRICTED_USER).
Is there a way to restore the Transaction log without
cutting all the connections (Especially replication) to
the read-only database '
Thanks for any feedback....> Is there a way to restore the Transaction log without
> cutting all the connections (Especially replication) to
> the read-only database '
I'm afraid not.
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=...ublic.sqlserver
"John" <anonymous@.discussions.microsoft.com> wrote in message
news:b48d01c3ecfc$63946850$a101280a@.phx.gbl...
> We are thinking to replicate a 'READ ONLY' database to an
> off-site location by using a third party utility (We will
> try to replicate from the warm backup server where we
> restore transaction logs every hour from the original prod
> server). Here are the two facts:
> 1- We don't want any performance decrease from the
> original production server to replicate directly from the
> prod server.
> 2- The third party utility is a file replication utility
> which can replicate the whole database, differences only
> e.t.c.
> The problem seems to be, when the transaction log restore
> starts, it kicks out all other users (SINGLE_USER,
> RESTRICTED_USER).
> Is there a way to restore the Transaction log without
> cutting all the connections (Especially replication) to
> the read-only database '
> Thanks for any feedback....|||Change the schedule for the restore portion of transaction logshipping so th
at it doesn't conflict with the replication. Why are you using a third-part
y replication tool?sql
Replication Problems
We are thinking to replicate a 'READ ONLY' database to an
off-site location by using a third party utility (We will
try to replicate from the warm backup server where we
restore transaction logs every hour from the original prod
server). Here are the two facts:
1- We don't want any performance decrease from the
original production server to replicate directly from the
prod server.
2- The third party utility is a file replication utility
which can replicate the whole database, differences only
e.t.c.
The problem seems to be, when the transaction log restore
starts, it kicks out all other users (SINGLE_USER,
RESTRICTED_USER).
Is there a way to restore the Transaction log without
cutting all the connections (Especially replication) to
the read-only database '
Thanks for any feedback....> Is there a way to restore the Transaction log without
> cutting all the connections (Especially replication) to
> the read-only database '
I'm afraid not.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"John" <anonymous@.discussions.microsoft.com> wrote in message
news:b48d01c3ecfc$63946850$a101280a@.phx.gbl...
> We are thinking to replicate a 'READ ONLY' database to an
> off-site location by using a third party utility (We will
> try to replicate from the warm backup server where we
> restore transaction logs every hour from the original prod
> server). Here are the two facts:
> 1- We don't want any performance decrease from the
> original production server to replicate directly from the
> prod server.
> 2- The third party utility is a file replication utility
> which can replicate the whole database, differences only
> e.t.c.
> The problem seems to be, when the transaction log restore
> starts, it kicks out all other users (SINGLE_USER,
> RESTRICTED_USER).
> Is there a way to restore the Transaction log without
> cutting all the connections (Especially replication) to
> the read-only database '
> Thanks for any feedback....|||Change the schedule for the restore portion of transaction logshipping so that it doesn't conflict with the replication. Why are you using a third-party replication tool?
off-site location by using a third party utility (We will
try to replicate from the warm backup server where we
restore transaction logs every hour from the original prod
server). Here are the two facts:
1- We don't want any performance decrease from the
original production server to replicate directly from the
prod server.
2- The third party utility is a file replication utility
which can replicate the whole database, differences only
e.t.c.
The problem seems to be, when the transaction log restore
starts, it kicks out all other users (SINGLE_USER,
RESTRICTED_USER).
Is there a way to restore the Transaction log without
cutting all the connections (Especially replication) to
the read-only database '
Thanks for any feedback....> Is there a way to restore the Transaction log without
> cutting all the connections (Especially replication) to
> the read-only database '
I'm afraid not.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"John" <anonymous@.discussions.microsoft.com> wrote in message
news:b48d01c3ecfc$63946850$a101280a@.phx.gbl...
> We are thinking to replicate a 'READ ONLY' database to an
> off-site location by using a third party utility (We will
> try to replicate from the warm backup server where we
> restore transaction logs every hour from the original prod
> server). Here are the two facts:
> 1- We don't want any performance decrease from the
> original production server to replicate directly from the
> prod server.
> 2- The third party utility is a file replication utility
> which can replicate the whole database, differences only
> e.t.c.
> The problem seems to be, when the transaction log restore
> starts, it kicks out all other users (SINGLE_USER,
> RESTRICTED_USER).
> Is there a way to restore the Transaction log without
> cutting all the connections (Especially replication) to
> the read-only database '
> Thanks for any feedback....|||Change the schedule for the restore portion of transaction logshipping so that it doesn't conflict with the replication. Why are you using a third-party replication tool?
Friday, March 9, 2012
Replication of SPs/Views/UDFs - Third party tool?
Hi,
I am using merge replication with anonymous pull subscriber. My problem is
getting a way to consistenly replicate database objects (SPs/Views/UDFs).
Replication kind of support it, but then you are not able to modify
(drop/alter) the objects and it doesn't work anyways because it depends on
the sysdependencies information (which is totally messed up).
So, I cannot use replication for that. I have tested DTS and it fails
because sysdependencies doesn't hold dependencies accurately enough.
I am starting to think on getting a third party tool or program my own...
I know I can include before snapshot scripts to create my objects; the
problem is that my database is highly dynamic, ie: objects are
created/modified/dropped too frequently.
Any advice?
Thanks, Jos Araujo.
use sp_addscriptexec to deploy your changes in your procs, views, and other
objects. This will only work for non ftp deployed subscriptions.
Getting dependencies correct is a problem no matter what RDBMS you use.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Jos Araujo" <josea@.mcrinc.com> wrote in message
news:OUZ44UAqEHA.3424@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I am using merge replication with anonymous pull subscriber. My problem is
> getting a way to consistenly replicate database objects (SPs/Views/UDFs).
> Replication kind of support it, but then you are not able to modify
> (drop/alter) the objects and it doesn't work anyways because it depends on
> the sysdependencies information (which is totally messed up).
> So, I cannot use replication for that. I have tested DTS and it fails
> because sysdependencies doesn't hold dependencies accurately enough.
> I am starting to think on getting a third party tool or program my own...
> I know I can include before snapshot scripts to create my objects; the
> problem is that my database is highly dynamic, ie: objects are
> created/modified/dropped too frequently.
> Any advice?
> Thanks, Jos Araujo.
>
|||I would do that (use sp_addscriptexec); however there is SQL code being
autocreated by my application.
For instance, there are "rules" that the user defines, that are supposed to
affect the records, those rules are "translated" to stored procedures that
the application creates.
Of course, i could change a lot of things to get it working with
sp_addscriptexec, however, it would really easier to just have an
application to "synchronize" these objects.
Thanks, Jos.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uHPDFJCqEHA.3540@.TK2MSFTNGP11.phx.gbl...
> use sp_addscriptexec to deploy your changes in your procs, views, and
other[vbcol=seagreen]
> objects. This will only work for non ftp deployed subscriptions.
> Getting dependencies correct is a problem no matter what RDBMS you use.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Jos Araujo" <josea@.mcrinc.com> wrote in message
> news:OUZ44UAqEHA.3424@.TK2MSFTNGP12.phx.gbl...
is[vbcol=seagreen]
(SPs/Views/UDFs).[vbcol=seagreen]
on[vbcol=seagreen]
own...
>
|||This is not an automated approach, but you can put your objects in a
different publication, manually create the snapshot when needed and then
reinit the subscribers to push your changes.
Scott
"Jos Araujo" <josea@.mcrinc.com> wrote in message
news:%23rGZvrjqEHA.2636@.TK2MSFTNGP09.phx.gbl...
>I would do that (use sp_addscriptexec); however there is SQL code being
> autocreated by my application.
> For instance, there are "rules" that the user defines, that are supposed
> to
> affect the records, those rules are "translated" to stored procedures that
> the application creates.
> Of course, i could change a lot of things to get it working with
> sp_addscriptexec, however, it would really easier to just have an
> application to "synchronize" these objects.
> Thanks, Jos.
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:uHPDFJCqEHA.3540@.TK2MSFTNGP11.phx.gbl...
> other
> is
> (SPs/Views/UDFs).
> on
> own...
>
|||Thanks...
"Scott Wallace" <scott.wallace@.astyles.com> wrote in message
news:eb6eajlqEHA.596@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> This is not an automated approach, but you can put your objects in a
> different publication, manually create the snapshot when needed and then
> reinit the subscribers to push your changes.
> Scott
> "Jos Araujo" <josea@.mcrinc.com> wrote in message
> news:%23rGZvrjqEHA.2636@.TK2MSFTNGP09.phx.gbl...
that[vbcol=seagreen]
problem[vbcol=seagreen]
depends[vbcol=seagreen]
the
>
I am using merge replication with anonymous pull subscriber. My problem is
getting a way to consistenly replicate database objects (SPs/Views/UDFs).
Replication kind of support it, but then you are not able to modify
(drop/alter) the objects and it doesn't work anyways because it depends on
the sysdependencies information (which is totally messed up).
So, I cannot use replication for that. I have tested DTS and it fails
because sysdependencies doesn't hold dependencies accurately enough.
I am starting to think on getting a third party tool or program my own...
I know I can include before snapshot scripts to create my objects; the
problem is that my database is highly dynamic, ie: objects are
created/modified/dropped too frequently.
Any advice?
Thanks, Jos Araujo.
use sp_addscriptexec to deploy your changes in your procs, views, and other
objects. This will only work for non ftp deployed subscriptions.
Getting dependencies correct is a problem no matter what RDBMS you use.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Jos Araujo" <josea@.mcrinc.com> wrote in message
news:OUZ44UAqEHA.3424@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I am using merge replication with anonymous pull subscriber. My problem is
> getting a way to consistenly replicate database objects (SPs/Views/UDFs).
> Replication kind of support it, but then you are not able to modify
> (drop/alter) the objects and it doesn't work anyways because it depends on
> the sysdependencies information (which is totally messed up).
> So, I cannot use replication for that. I have tested DTS and it fails
> because sysdependencies doesn't hold dependencies accurately enough.
> I am starting to think on getting a third party tool or program my own...
> I know I can include before snapshot scripts to create my objects; the
> problem is that my database is highly dynamic, ie: objects are
> created/modified/dropped too frequently.
> Any advice?
> Thanks, Jos Araujo.
>
|||I would do that (use sp_addscriptexec); however there is SQL code being
autocreated by my application.
For instance, there are "rules" that the user defines, that are supposed to
affect the records, those rules are "translated" to stored procedures that
the application creates.
Of course, i could change a lot of things to get it working with
sp_addscriptexec, however, it would really easier to just have an
application to "synchronize" these objects.
Thanks, Jos.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uHPDFJCqEHA.3540@.TK2MSFTNGP11.phx.gbl...
> use sp_addscriptexec to deploy your changes in your procs, views, and
other[vbcol=seagreen]
> objects. This will only work for non ftp deployed subscriptions.
> Getting dependencies correct is a problem no matter what RDBMS you use.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Jos Araujo" <josea@.mcrinc.com> wrote in message
> news:OUZ44UAqEHA.3424@.TK2MSFTNGP12.phx.gbl...
is[vbcol=seagreen]
(SPs/Views/UDFs).[vbcol=seagreen]
on[vbcol=seagreen]
own...
>
|||This is not an automated approach, but you can put your objects in a
different publication, manually create the snapshot when needed and then
reinit the subscribers to push your changes.
Scott
"Jos Araujo" <josea@.mcrinc.com> wrote in message
news:%23rGZvrjqEHA.2636@.TK2MSFTNGP09.phx.gbl...
>I would do that (use sp_addscriptexec); however there is SQL code being
> autocreated by my application.
> For instance, there are "rules" that the user defines, that are supposed
> to
> affect the records, those rules are "translated" to stored procedures that
> the application creates.
> Of course, i could change a lot of things to get it working with
> sp_addscriptexec, however, it would really easier to just have an
> application to "synchronize" these objects.
> Thanks, Jos.
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:uHPDFJCqEHA.3540@.TK2MSFTNGP11.phx.gbl...
> other
> is
> (SPs/Views/UDFs).
> on
> own...
>
|||Thanks...
"Scott Wallace" <scott.wallace@.astyles.com> wrote in message
news:eb6eajlqEHA.596@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> This is not an automated approach, but you can put your objects in a
> different publication, manually create the snapshot when needed and then
> reinit the subscribers to push your changes.
> Scott
> "Jos Araujo" <josea@.mcrinc.com> wrote in message
> news:%23rGZvrjqEHA.2636@.TK2MSFTNGP09.phx.gbl...
that[vbcol=seagreen]
problem[vbcol=seagreen]
depends[vbcol=seagreen]
the
>
Subscribe to:
Posts (Atom)