I don't know how to interpret what you have, I use the blocker checker provided MS http://support.microsoft.com/kb/271509 and then analyze using sherlock as described in http://blogs.msdn.com/debuggingtoolbox/archive/2007/07/09/sherlock-tool-for-graphical-blocker-script-analysis-sql-server-2000-and-7-0.aspx

I...

Other than learning a particular DB I would say learn SQL, a good book is SQL Queries for Mere Mortals(R): A Hands-On Guide to Data Manipulation in SQL

Got this from this site I believe way back, this checks to see if it is a named instance and routes the registry accordingly

declare @reg_srv varchar(256),

...

There was an article in SQL Server Magazine last month detailing cmd line scripting utility you can find the article here, you have to be a subscriber http://www.sqlmag.com/Article/ArticleID/100140/sql_server_100140.html...

Does the MsDtsSrvr.ini.xml file contain the same info on both nodes, this is what management studio read when trying to open integration services?

Andrew

You should be able to do this via sql ssis package, search this site, some one posted how to set up the odbc connection to do this, use google and...

I am assuming you are trying to find out if you have a cluster failover, if this is the case you can poll the box and find out the physical...

There is a bug in the main code, an update is available on some forums, find below the code:

-- Script must not be run in a transaction

SET IMPLICIT_TRANSACTIONS OFF

IF @@TRANCOUNT...

One way to do this would be to collect the job failure by trapping it in a on failure step, use that step to insert into a table, and have...

Intergaration services is not instance or cluster aware, but what you can do is edit the MsDtsSrvr.ini.xml file on both nodes and set up a folder each for the msdb...

Grant,

There sure is a number of ways to skin the old cat, just takes time, effort and feel to hopefully get there in the end:)

Andrew

If you can determine that it is a finite number of procs\sql calls that causes the waits, you could also set the maxdop option in the code, maybe the rest...

Is this 8 proc cores or 8 logical procs hyperthreading, if they are logical procs you can turn this off in the bios. I have seen SQL handle logical procs...

Looks like data is being updated at the subscriber and when the transactions are being passed over the record is not there.

Andrew

I have doctored this script to collect the windows event logs from my SQL boxes it uses log parser and is pretty intuitive:

http://www.sqlservercentral.com/scripts/31350/