Re: Modifying the structure of a database that is under log shipping

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

From: Christopher Campbell (ccampbell_at_ancorinfo.com)
Date: 03/04/04 

Date: Thu, 4 Mar 2004 14:00:01 -0500

Thanks for the additional information.

Just to close this thread out...

My table change did copy over with no issues. My log shipping seems to have
caught itself up and is working fine again.

I do use a delay in my log shipping but the delay I experienced earlier was
much longer than the normal delay I allow for. I checked the size of the
logs during the extended delay and found that they were quite a bit larger
than normal due to some bulk data loads that were being done. I think that
this more than anything contributed to the delays.

Log shipping now seems to be working great.

Thanks to everyone for the advice.

"Baisong Wei[MSFT]" <v-baiwei@online.microsoft.com> wrote in message
news:rEl28BbAEHA.604@cpmsftngxa06.phx.gbl...
> Hi Chirstopher,
>
> Thank you for using the newsgroup.
>
> From you information, there seems to be a delay in your log shipping. The
> UDF is copied to the secondary server now. How about your change on the
> table, is it copied to your secondary server according to you schedule?
>
> There is some information you could check for the log shipping.
> 1) There are some options to set when you set up your log shipping:In the
> Log Shipping: The Log Shipping ScheduleSchedules; The Copy/Load Frequency,
> with which you want the destination servers to backup and restore the
> transaction logs from the source server; The Load Delay, with which the
> destination database will wait before it restores the transaction log from
> the source server. The default for this box is 0 minutes, which indicates
> that the destination database should immediately restore any transaction
> log backups.
> 2) When establish the log shipping, you could write the history to the
> local server or a remote server's database
> 'msdb.dbo.sysdbmaintplan_history', you could look for information in that.
> Also, you could write a report to an .TXT file. You could check the
report
> for more information.
>
> As in you case, the log shipping do work ( the UDF finally created on the
> secondary server), so you need check the above information and check why
> there is a delay not according to the schedule and related settings.
>
> Hope this helps.
>
> Best regards
>
> Baisong Wei
> Microsoft Online Support
> ----------------------------------------------------
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only. Thanks.
>
>

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: 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)
  • 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)