If it runs when you run manually, but not as a job, then it is highly probably that it is due to privilege problems. There have been similar questions...

What project?

Are you planning to create a new database in the existing SQL Server instance or do you need to install a new instance of SQL Server ... to be...

I'm not totally clear about your problem. But could you explain why you are using snapshot, rather than transactional replication? What was the rationale behind it?

I had a similar issue ... Never got to solve it though ... I think it is related to IO problems ...

In our company, we have developed an in-house software, which monitors and displays the status of many of the items you mentioned:

- Jobs good/failed

- Backup problems

- Disk space/problems

and sends emails...

Check out the 7th item here:

http://www.sqlservercentral.com/columnists/jsack/sevenmonitoringscripts.asp

See if this is what you were looking for.

Good luck!

I don't think what I am about to suggest is the best way to go, but it satisfies your non-manual constraint:

1. Script out all views, together with exec privileges as...

What if a new stored procedure is added to the publisher, will it be propagated to all the subscribers as well or should it be added in some special way...

One way to find out (I think) is to run Profiler [capturing certain information] during the time this maintenance plan runs ...

We run UPDATE STATISTICS daily (sometimes multiple times a day). Would it be important to run it right before I execute the query to get the space usage results?

Thank...

Andras,

Thank you for the suggestion.  Once I ran the DBCC UPDATEUSAGE('DbName'), the situation seems to have improved, but not completely fixed.  That is, the difference in space used by indexes...

Does it only take that long over weekend or it got longer from now on?

As Ratheesh suggested, check if any other jobs conflict.  I once had backup job run longer...

Check to see if any jobs are hanging and/or if transaction log backup is really working (i.e. not failing).

We once had a backup job hang for 2 days - transaction...

From my experiment it looks like having a stored procedure will work just as the script.

Thanks a lot!

Steve,

But wasn't it the case with the INDEX_DEFRAG script anyway (i.e. if it fails, what is not defragged is not defragged).  In that case we just rerun the job...