logshipping question

Hi Guys,
i am planning to implement logshipping in sql 2000 which
is already a pulisher for transactional replication.
i am planning to take transaction log backup in the
interval of 1(one) minute.
if network connection broken will it affect restoring at
desination server?
can i make the share for transaction log backup folder on
network instead of production server?
overall will it have any negative impacton source server.
Pls advice
Thanks
Biju
Biju,
although the graphical interface doesn't implement the option to backup to a different computer (in terms of browsing), you can use a network share by typing it in. I haven't done this in anger before but I guess the usual constraints of bandwidth, networ
k useage etc would obviously apply.
Regards,
Paul Ibison

logshipping question

Hi Guys,
i am planning to implement logshipping in sql 2000 which
is already a pulisher for transactional replication.
i am planning to take transaction log backup in the
interval of 1(one) minute.
if network connection broken will it affect restoring at
desination server?
can i make the share for transaction log backup folder on
network instead of production server?
overall will it have any negative impacton source server.
Pls advice
Thanks
Biju
1. Don't try to do log shipping at an interval less than 2 minutes. It can
be done, but you are going to have an extremely difficult time handling all
of the error messages that will pop up due to latency and congestion.
2. You can use a network share if you choose to. The only impact is that
there will be a slightly longer delay as your backups transit across your
network card instead of to the local disk. The negative impact is that your
backups are streaming down your network card which impacts network
throughput. But, that impact is similar to what happens if you back up to
local disk and then copy the backup over, so that consideration is
essentially a wash.
3. Watch you full backups carefully. They will block the transaction log
backups which can cause all of your alarms to go off.
Mike
Principal Mentor
Solid Quality Learning
"More than just Training"
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com
|||A one minute transaction log backup is VERY ambitious. Most people go for between 5 and 15 minutes. If you test lab this with production-like equipment you will understand why 1-min intervals is so difficult to achieve on SQL2K.
If the network connection is broken, the transaction log copy job will retry the copy the next time it is scheduled to run. No data will be lost. It will keep retrying until the logs are successfully copied or the out-of-synch time is reached.
With an interval of 1-min performance could be a real concern.

Login Problem

I just tried to create a Transactional Replication and it failed because the
Login for sa failed...
I assume that the destination server (for Push Subscription) doesn't
recognize the sa of the Distributor
What can be done to solve that (when running the wizard I wasn't given any
chance to solve that)
Thank you,
Samuel
if this is a pull subscription you must make sure that the sa account, the
SQL Server agent account on the subscriber, or the account that you are
using to pull the subscription has dbo rights on the distribution database,
and is in the PAL of the publication 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
"Samuel Shulman" <samuel.shulman@.ntlworld.com> wrote in message
news:eeCvEFN5GHA.4868@.TK2MSFTNGP03.phx.gbl...
> I just tried to create a Transactional Replication and it failed because
> the Login for sa failed...
> I assume that the destination server (for Push Subscription) doesn't
> recognize the sa of the Distributor
> What can be done to solve that (when running the wizard I wasn't given any
> chance to solve that)
> Thank you,
> Samuel
>
|||It is a push subscription
Samuel
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:OG4si8N5GHA.4256@.TK2MSFTNGP03.phx.gbl...
> if this is a pull subscription you must make sure that the sa account, the
> SQL Server agent account on the subscriber, or the account that you are
> using to pull the subscription has dbo rights on the distribution
> database, and is in the PAL of the publication 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
> "Samuel Shulman" <samuel.shulman@.ntlworld.com> wrote in message
> news:eeCvEFN5GHA.4868@.TK2MSFTNGP03.phx.gbl...
>
|||Samuel,
please see if this applies to your issue:
http://support.microsoft.com/default...b;en-us;320773
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Your publisherlogin property must be the sa account (or an account in the
dbo role in the distribution database and the dbo role in the publication
database). can you ensure that this is the case?
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Samuel Shulman" <samuel.shulman@.ntlworld.com> wrote in message
news:O$JJeDO5GHA.2596@.TK2MSFTNGP06.phx.gbl...
> It is a push subscription
> Samuel
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:OG4si8N5GHA.4256@.TK2MSFTNGP03.phx.gbl...
>