i think i agree with you, when i give the option to stopat and tried to see what the script code is, its no whevere mentioning the restore with stopat.

Need...

you can try installing one of the tool like performance analysis or spotlight from Quest, and you can browse history to see what type of locks were there at any...

you can add one more step to verify the backup when its being copleted, and it will confirm you either backup is valid set or not.

here is my finding...

I did the full backup.

then modified a table value

take log backup

then modified the value back to original

take log backup.

Restored on existing database and it showed me all...

ok, let me try. Will come back to you soon

ashish.kuriyal (9/7/2010)

---

when you do the restore after full backup, you database must in norecovery mode.

Now, start restoring your logbackup.

For pointintime recovery you need to mention the timestamp which in t-sql...

when you do the restore after full backup, you database must in norecovery mode.

Now, start restoring your logbackup.

For pointintime recovery you need to mention the timestamp which in t-sql referred...

in that case, then every time in your query you need to define itin your matching condition. Something like :-

select.....

from tabl1 a inner join table2 b

ON a.columnname= b.columnname...

seems like your replication is out of sync?

Are you getting any more detail/error in replication monitor or in distribution database using below query:-

select * from MSrepl_errors order by time...

you need to write t-sql code on that folder which will delete the file older than the number of days you want.

You need to use the cursor which will go...

on a light note, i think its problem with name(Priya) which is female name and ladies are always main reason of any problem.......hahahahahahaha 😀 😀 😀 😀 😀

try to change maintenance plan to delete last 2 days file its 1 day as of now or just add one more day. And then once it run successfully on...

and are you able to delete/rename it manually? If not then file is in use? Have you looked into your task manager?

are you copying your old day backup file to some other location?

Try in task manager and if you can find any process which could be using your old day...

ok, and this is the only code you have behind that perticular functionality or some other set of code as well?

Not able to find any specific problem with this set...