I would attempt the full UNC path for this and see if that works for you.

i.e.

"\\servername\sharename\cpu_history_max_by_hour.txt"

As long as you do not mind the fragmentation that it can create (and likely is creating) it should not be a problem, it just could make queries against the...

I really just have one thought on the process as a whole and it pertains to shrinking your db. Shrinking the log makes sense, but shrinking your data...

I am not aware of any history being kept on this column.

But if you have some older backups of msdb you could certainly restore them and then check the sysjobs...

The redistributable that you have linked here has the installer within it that you will need for the installation.

I am not aware of this being available to you within SSMS. However, you could certainly write your own SSIS package that could loop through a server list to...

I may not be quite understanding the question but if you loaded this into a table (leaded into EntryDateTime order) and included an identity column, you could do a select...

Depending on what kind of options and setup you have for this table, it really sounds to me like this is a good opportunity to put the sliding window partition...

I think it very much depends on what you are doing. But I have one running that does throw the error into the log. The code...

This is similar to what you are looking for and also uses an input text file with the list of servers you want to get data from but instead of...

You could use an ActiveX Script task, to get the value from your table and then store that into a Global Variable, since the global variables within the package can...

Scheduler blocking is what caused the Agent to...

This seems like the ideal task to use SSIS for (if you are familiar and comfortable with the tool). Obviously you will have some criteria that will tell...

I have had this happen to me before on an old SQL 2000 server as well, and it ended up being due to Schedule Blocking at the database level. ...

Here is a script that will script out all of your indexes for you (you would want to run this prior to dropping them obviously)

http://www.sqlservercentral.com/scripts/Index+Management/31652/

And then here is another script...