Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
tonyshukal
Starting Member
7 Posts |
 Posted - 2004-05-06 : 04:58:32
|
| HiI am using SQL 2k En edition and am Log Shipping to 2 other servers.I have used Database Maint Plan to create these Log Shipping. It working fine for most of the databases but every morning I find a few databases are not Shipping properly. Upon further investigation I have noticed that Log backup task of that database is still running on sourceServer, therefore Transaction was never backed up. I stop SQL Server Agent to stop that JOB, all other means just does not work.Does anyone has this problem with SQL Server Agent that any job is running for forever?Any Ideas?Tony |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2004-05-06 : 05:02:02
|
| I always implement log shipping by scheduling log backups into a directory, copying the files to the other server (and archiving) and restoring (and archiving) them there.I know if anything is wrong by the date on the latest file restored.I'm not a fan of using maintenance plans for anything.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
tonyshukal
Starting Member
7 Posts |
Posted - 2004-05-06 : 05:26:02
|
| Thanks nrI followed Microsoft recommendations and it sounded pretty much straight forward.What could be wrong with dates? I have checked dates are in-sync on 3 db servers.Do we have some place to specify something like timeout for Job?I am not sure why its status never changes. (I am aware the refresh thingy)All this Job is doing is taking transaction log back up every 15th minute.TRN file copying and Restoring is destination server's Job.Thanks |
|
|
|
|
|
|
Log Shipping [25 databases]