>the reason why the cahnges in primary DB are not reflected on secondary
>maybe that you didnt setup the log shipping properly.
>You can cross check if if have any out of sync errors...
>
>and abt deleting the log shipping the best way will be ... from the
>maintenance plan remove log shipping and then delete the plan.

> Hi,
>
> I have set up log shipping in the following :
>
> load/copy frequency - 1 mins
> backup frequency - 5 mins
> secondary db - standby mode
>
> issue :
> when i made some changes to a record of the primary db's tbl , it was not
> reflected in the secondary db's table.
>
> Is it due to the fact that the secondary db is a Read-Only ?
>
> and if i do want to delete log shipping  , what shld be the correct way in
> doing this
>
> appreciate ur advise
>
> tks & rdgs
>
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200601/1

> Hi,
>
>  I have managed to set up the log shipping correctly as i could see the
> changes on my destination DB . However, i have specified that copy is 0
> minutes , and load is 1 minutes but it took something like around 5
> minutes
> to see the updated data in  my destination DB.
>
>  how can i acutally make the updates "almost immediate" ? or this is
> normal
> as copying the txn log takes time and need to wait till user "give up" the
> exclusive lock , then copy the txn log over and then load from the txn log
> ?
>
> appreciate ur advice
> tks & rdgs
>
>
> Michael Hotek wrote:
>>Did you wait long enough for the changs to be sent?  You can verify the
>>tran
>>log backups by looking in the directories on each machine.  You can also
>>verify the backup and restore by looking in the errorlog.  The log
>>shipping
>>monitor will display the status of everything.  If it isn't getting there,
>>you will be seeing errors.
>>
>>> Hi,
>>>
>>[quoted text clipped - 16 lines]
>>>
>>> tks & rdgs
>
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200602/1

>You can't.  The entire thing runs as a set of jobs.  The most frequently a
>job can run is every minute and that is NOT recommended for log shipping
>unless you want to watch the monitor throw a LOT of errors.  You usually set
>up the backup job at 2 minutes or more.  (2 minutes is the lowest you want
>to go).  That means a new backup will be generated every 2 minutes.  It then
>takes time to copy over and time to restore.  Most of that time is simply
>the job shutting down and waiting for the SQL Server Agent to kick it off
>again.  5 minutes start to finish is about the best you are going to get
>with log shipping.  If you need lower latency than that, you have to go to
>either Database Mirroring (2005 only) or the replication engine.
>
>> Hi,
>>
>[quoted text clipped - 26 lines]
>>>>
>>>> tks & rdgs