I didn't either, I just happened to notice that the temp table names matched, more luck than judgement believe me.

Try this...same script, but I have changed the name of #databases to #thedatabases and it seems to work. I wonder if it has something to do with the sp_databases proc...

How are you calling the dts from the job? Could you paste the execution line?

It's not supported in the slightest, as for getting it to work, possibly.

Why would you run 6.5 on 2003?

I wouldn't recommend using a NAS however....

You'd keep sql on the local box and use the san for the database files.

I would run option 2 with all the db's on full recovery...this gives you the advantage of having seperate filegroups for each of the apps (even though you could use...

Other than that, you could look at using an evaluation version of Litespeed from http://www.imceda.com which compresses the backup as it does it.

The latest version of pkzip from http://www.pkware.com/ does files above 4GB, I belive that Winzip 8.1 also does the job.

I would start out with a hard cap on SQL, this will prevent it and other applications fighting for memory space, give the OS and other apps at least 500Mb...

Is there any way that you could put a load on the dev server equivalent of that on production just as a proof of concept?

It looks as though you have everything configured correctly. Just bear in mind that unless SQL is using a lot of memory and having to pull a lot of data...

Presumably you are running SQL2LK EE and Win2k Adv?

Previously were you seeing memory as being an issue? If SQL had plenty of spare memory previously and was not having to...

In BOL look for RESTORE LOG.

Syntax of restore to point in time:

RESTORE LOG <dbname>

   FROM <tranlogfile>

   WITH RECOVERY, STOPAT = ' <date & time> '

Useful link for help troubleshooting MAPI errors: http://support.microsoft.com/default.aspx?scid=kb;en-us;Q238119