It can help check for errors in the db such as corruption.

There is little point in restoring a corrupted database unless you are testing the fix for the corruption.

This sounds to me like you have a re-indexing job running at night, this will cause the log to grow. If not is there an overnight process that maybe manipulating...

This is an FTS issue, change the drive and folder that the FTS file for the database is going to. Try and put it on the same drive and folder...

Looks like you are trying to restore the same Full Text Search file, Change the File name in the restore options.

Does your database use Full TEXT SEARCH?

Ah......

Yes on one server, I only set it up a couple weekends ago and someone has gone in and changed it to selected dbs. Thought I had checked that...

Data is pretty much the same,

Stats are up to date on LIVE,

Out of date on Test (this was what confused me).

Seems like the Environments are too different that is...

Sorry 500K execution in Live.

Why would it choose such an awful plan in LIVE

Thanks.;-);-);-);-)

I'll take a look now.

Thanks

Thanks,

Saved me a lot of time googling.

Thanks

What I will be questioning is if the LEft joins in the code are actually valid or simply a lack of understanding of which joins to use.

I can see some...

Are you using a SSIS package to do this.

Who is the owner of the job?

When the job is executed who is it executed by(which account).

How are you managing the T-logs?

If this happens frequently then I would increase the disk drive.

Otherwise maybe instead of sending a Mail.

It could trigger off

1 backup the DB

2 ...