Log Shipping: how to avoid connection resets on secondary

Tech-Archive recommends: Fix windows errors by optimizing your registry

Is there a way to avoid resetting connections to the db on the secondary
server, while using log shipping?

I appreciate any pointers in this regard.

Thanks,

Subra


.

Relevant Pages

  • Re: Need Feedback on Trans. Replication w/ Remote Distributor
    ... Built-in log shipping works over SMB protocols. ... BOL describes the built-in stuff for Log Shipping in Enterprise ... The SQL 2000 resource kit has some more information on roll your ... Microsoft SQL Server MVP ...
    (microsoft.public.sqlserver.replication)
  • Re: SQL 2005 servers with multiple instances
    ... log shipping is the current plan. ... given the same number of user databases. ... server, one old server, many new drives) and we spec'ed it for SQL2000's ... has changed since I worked with it, clustering only has one copy of the ...
    (microsoft.public.sqlserver.setup)
  • Transaction Log Shipping silently fails?
    ... I configured SQL2005 transaction log shipping from a primary to a secondary server. ... I created shares on the primary and secondary, and configured log shipping on the primary with the default options, with the dB on the secondary set to "standby" during log restores. ... The database is about 5 gig, so I did a separate restore on the secondary before configuring shipping. ...
    (microsoft.public.sqlserver.tools)
  • Re: Disaster recovery - Use Replication or Log shipping
    ... cons of each ... Pros log shipping ... there is a log shipping wizard that ships with SQL 2000 EE, ... standby server database must go off line as you apply the tlogs ...
    (microsoft.public.sqlserver.replication)
  • Re: newbie help: failover server
    ... I will look into Log Shipping & the SQL Resource ... As far as business decision vs technology decision, ... > Server 2000 Resource Kit includes a simple log shipping example that you ...
    (microsoft.public.sqlserver.clustering)