I would look at the DTSRUN command in BOL. You are able to pass global variables into the package at runtime using switches within the DTSRUN.

I would check for blocking processes on the table that you are trying to insert the records into. The blocking condition would cause the insert to timeout.

Just gave it a try, guess you can't create a trigger on there.

You will have to license both Windows nodes, you are correct in the licensing for the SQL Server.

I guess you could put a trigger on the sysobjects table where the inserted xtype = 'U'.

You cannot insert the data from an execute into a table variable, you could use a temp table instead.

Check that you are using the same log shipping monitor server.

Are you running perfmons against the machine? If not add some counters for memory, both OS and SQL related, see if this gives you any ideas.

If you actually want the data to be updateable on the publisher and subscriber you'll need to change to Merge replication rather than Transactional.

Someone may have inadvertantly broken the trust between the two domains...I'd check that out first, here's a link to a MS article on this particular problem... http://support.microsoft.com/?kbid=834124

Never been to one, honestly, I don't even know that one exists in the Jersey area.

The whole networking aspect is an interesting thing that I know Monster.com has been looking...

One note of warning, just be aware that you will have to have the disks that you are moving to managed within the SQL cluster otherwise SQL will not be...

Never had the chance to get training and no help with the purchase of books or mags either unfortunately.

Be lost without this place that's for sure.

Where I have found a lot of interviewees have fallen down is when the don't know the answer to a question that they don't even provide an idea as to where...

You could us a cursor to accomplish that, however it would be slow as it's a row by row process.