Who owns the job? Users cannot see/execute jobs that they don't own.

Here's a quick way.

EXEC sp_MSforeachtable 'sp_spaceused @objname =''?'''

Ok, here's a way I would probably end up doing it. This is pretty rough, I did do a bit a fiddling around to get some of the data to line...

As mentioned in my earlier post, the main bottleneck you seem to be encountering is transferring the files to the OLAP server. There is nothing that DTS, or SQL Server...

As mentioned in my earlier post, try using ROBOCOPY from the Windows Resource Kit.

Check the articles over at http://www.sqldts.com about changing the text file connection.

Is this data, log or both? Allocated space or used space?

Could be all you need to do is shrink the log file.

You could alter your stored procedure to accept the Job ID uniqueidentifier as a parameter.

Then in the job that calls the stored procedure, add the SQL Agent token [JOBID]. Then...

Best I've come up with is to put borders on the table in the report design. Make sure you use the thinnest line possible, otherwise you'll end up with huge...

As long as the structure of the tables is the same, you can replace TABLE_1 and TABLE_2 with your new tables names dynamically and everything will work great. If however...

Also, using Data Driven queries in the DTS packages will slow things down a lot. This causes the package to process data from the source in row-by-row method instead of...

Just to make sure I'm understanding what you've posted, the total time from steps 1 to 7 is 6 hours??

If so then I'd look at the main bottleneck in your process...

While Dan's comments are quite legitimate, you can use the WITH TABLERESULTS option on the DBCC SHOWCONTIG command to return the results in a table format. This make it easy...

Do you mean the IDENTITY values??

If so, check DBCC CHECKIDENT in Books Online.

Also, check point 6 of the following article for permissions,

http://www.microsoft.com/sql/techinfo/administration/2000/security/securingsqlserver.mspx