I did exactly that, there were no interim backups listed in SQL server, and the only ones restored by me were in logical order, but the problem still kept reoccurring.

I...

Okay, basically what you're actually doing is in 2 separate parts.

1. You need a database host running on your PC.

2. You need the Primavera v6 application installed on your PC...

I'm assuming you've already downloaded a Primavera installer and encounter the error message when you're in the process of installing it?

It's likely that either;

You want a standalone version on your...

Thanks all,

I have kind of picked parts of everyone's suggestions, and thrown them together to come up with the solution for this and it has now grown to include event...

PS, I run in a multiple-version environment (SQL 2000-2008), so any cross-platform solutions would be ideal, but any suggestions still very welcome 🙂

Great article, thankyou.

I've been looking for one which has SQL benchmarks included for a while...

I'll give you an overview of my jobs. I can;t really see a problem with them at all, and they were working fine until a few weeks ago...

BACKUPS

1. Full Database...

Just a bit of extra info.

It is the very final LSN in the database backup which is causing a problem....

When I restore headeronly the last lsn is "2830931000000492700001" which is...

The explanation for the above missing lines is that a truncate was carried out as part of a bigger process, by another DBA.

It was a one-off so doesn't affect any...

If it is the case that there are only a handful of Stored Procedures the analysts are going to need to run, then it is worth considering giving them basic...

It sounds as if either the process which was introduced is badly designed, meaning it is using an unnecessary amount of temporary tables/temporary data, or the diskspace available to the...

I have found that quite often it is reports causing the problem, and regularly where the criteria hasn't been properly specified.

If you captured the query and source while they were...

This query should help you for what you're after;

It will give you the past weeks backup history for all databases on a server, including the device which was backed up...

Infact the specific lsn in the error appears to be in the full database backup file so is the issue that it not being restored to the standby correctly?

OK thanks for the query 🙂

Here is the log for the latest 3 backups in the history;

#1 Log Backup:

First LSN: 2827651000000421700001

Last LSN: 2827675000000263400001

#2 DB Backup:

First LSN: 2827890000000463800001

Last LSN: 2828010000000320100001

#3...