I am trying to identify the advantage of using this utility versus an "Actual Execution Plan". It seems to give all the same information about which indexes where used, scans/seeks...

I find the pr_RunAgentJob procedure a little curious. It checks if the job exists and if it is currently running. Well, it won't run if it doesn't exist and...

I suppose it's only fair since I have used this site for so many years now. Thanks for the encouragement.

I see the ability to schedule jobs that run on all the servers an advantage to your method because mine is essentially a dumb terminal that sends commands and displays...

I think the article is great and the methodology is well documented. However, I don't like linked servers, openrowset, opendatasource. I feel they are a security risk, bugy to manage...

Part of the reason to separate the reporting environment from the production environment is to separate resources so that reporting doesn't bog down production. If you have the objects on...

I agree with your conclusions. The nature of a global temp table is that it is highly transient, so security shouldn't become a factor. To your point - I have...

If you are running this interactively you should be able to see how many records leave the source and how many records flow to the destination. It does sound strange...

Are you a local admin on your machine? If not then they probably need to add you to the sysadmin role on the SQL Server instance. Can you see if...

Ralph Kimball has written some good general books on the subject. However, if you are dealing specifically with SQL Server 2005 I prefer the indepth book

Microsoft SQL Server 2005 Analysis...

Transactional replication would likely be your best bet.

There are a few bugs in SSIS, and a few other frustrating issues with it like how it handles meta-data. However, I don't know of any bugs related to your...

Is [dbo].[ptPayments] ([PaymentBatchID]) a primary key or does it have a unique constraint/index?

You cannot assign permissions to global temp tables - everyone has every permission on them including ddl.

They are visible for the entire SQL Sever instance.

You don't deal with permissions.

There are...

You cannot setuser to a login account, you must instead setuser to a database account. SA is not a database account, instead setuser to dbo.

Regards