Big replication

You might find this optimization article helpful:
http://www.microsoft.com/technet/pro.../sql/2000/main
tain/mergperf.mspx
As you are using continuous merge, are you using merge
because of its versatile conflict management? If you
don't have conflicts and have no need for autonomy, I'd
consider transactional with updating subscribers if speed
is an issue.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Thanks for link
Well I nead a conflict menager - clients can connect to any server as they
wish.
By the way some info:
to replicate 750 records 650 Bytes each to 6 SQL Server i nead (
approximately) :
- 23 seconds with 1024kbps,
- 143 seconds with 256kbps,
- 330 seconds with 128kbps
Best Regards
Wojciech Znaniecki
Uzytkownik "Paul Ibison" <Paul.Ibison@.Pygmalion.Com> napisal w wiadomosci
news:15c401c515df$a311f300$a401280a@.phx.gbl...
> You might find this optimization article helpful:
> http://www.microsoft.com/technet/pro.../sql/2000/main
> tain/mergperf.mspx
> As you are using continuous merge, are you using merge
> because of its versatile conflict management? If you
> don't have conflicts and have no need for autonomy, I'd
> consider transactional with updating subscribers if speed
> is an issue.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>

Best way to maintain up to date SQL Jobs and SSIS on failover Serv

Hi,
on SQL 2005 we use log shipping to maintain our production server to an
alternate server. Now I would like to do something similar with our SQL
Agent jobs and SSIS. While those jobs are enabled on the production server,
I would like them to become disable on the alternate server, this process
would be scheduled once per day.
I'm sure there are many ways to achieve this, but I am wondering what would
be the most efficient.
any ideas ?
Thanks
Fred
ok, I just figured out how to transfer/disable jobs using the Transfer Job
task in SSIS, it's quite nice actually.
But, I am still in the dark on how to transfer SSIS from one server to
another.
BTW, a backup and restore of MSDB is out of the question.
Thanks
"FredDBA" wrote:

> Hi,
> on SQL 2005 we use log shipping to maintain our production server to an
> alternate server. Now I would like to do something similar with our SQL
> Agent jobs and SSIS. While those jobs are enabled on the production server,
> I would like them to become disable on the alternate server, this process
> would be scheduled once per day.
> I'm sure there are many ways to achieve this, but I am wondering what would
> be the most efficient.
> any ideas ?
> Thanks
> Fred

Best way to maintain up to date SQL Jobs and SSIS on failover Serv

Hi,
on SQL 2005 we use log shipping to maintain our production server to an
alternate server. Now I would like to do something similar with our SQL
Agent jobs and SSIS. While those jobs are enabled on the production server,
I would like them to become disable on the alternate server, this process
would be scheduled once per day.
I'm sure there are many ways to achieve this, but I am wondering what would
be the most efficient.
any ideas ?
Thanks
Fredok, I just figured out how to transfer/disable jobs using the Transfer Job
task in SSIS, it's quite nice actually.
But, I am still in the dark on how to transfer SSIS from one server to
another.
BTW, a backup and restore of MSDB is out of the question.
Thanks
"FredDBA" wrote:

> Hi,
> on SQL 2005 we use log shipping to maintain our production server to an
> alternate server. Now I would like to do something similar with our SQL
> Agent jobs and SSIS. While those jobs are enabled on the production serve
r,
> I would like them to become disable on the alternate server, this process
> would be scheduled once per day.
> I'm sure there are many ways to achieve this, but I am wondering what woul
d
> be the most efficient.
> any ideas ?
> Thanks
> Fred|||If its not too late, consider storing your SSIS packages in the
filesystem and just keep copies on your DR machines
Terry|||Anotther thing we do here (mostly for legacy dts packages) is to
restore the MSDB as another name. During DR, rename that database to
MSDB and all the objects will be there.
Terry

Best way to maintain up to date SQL Jobs and SSIS on failover Serv

Hi,
on SQL 2005 we use log shipping to maintain our production server to an
alternate server. Now I would like to do something similar with our SQL
Agent jobs and SSIS. While those jobs are enabled on the production server,
I would like them to become disable on the alternate server, this process
would be scheduled once per day.
I'm sure there are many ways to achieve this, but I am wondering what would
be the most efficient.
any ideas ?
Thanks
Fredok, I just figured out how to transfer/disable jobs using the Transfer Job
task in SSIS, it's quite nice actually.
But, I am still in the dark on how to transfer SSIS from one server to
another.
BTW, a backup and restore of MSDB is out of the question.
Thanks
"FredDBA" wrote:
> Hi,
> on SQL 2005 we use log shipping to maintain our production server to an
> alternate server. Now I would like to do something similar with our SQL
> Agent jobs and SSIS. While those jobs are enabled on the production server,
> I would like them to become disable on the alternate server, this process
> would be scheduled once per day.
> I'm sure there are many ways to achieve this, but I am wondering what would
> be the most efficient.
> any ideas ?
> Thanks
> Fred|||If its not too late, consider storing your SSIS packages in the
filesystem and just keep copies on your DR machines
Terry|||Anotther thing we do here (mostly for legacy dts packages) is to
restore the MSDB as another name. During DR, rename that database to
MSDB and all the objects will be there.
Terry