You could use an Event Handler to catch the error. You can set an "On Error" event handler on any component in your pacakge.

You should be able to perform a SQL Server installation and only install the Integration Services and BIDS components.

See this thread on msdn: http://social.technet.microsoft.com/Forums/en-US/sqlintegrationservices/thread/64621f3d-1f25-4cd2-856a-5cfcd67a19cb/[/url]

Under Custom Properties on the Script panel of the Script Transformation Editor, did you enter your variable name in the "ReadOnlyVariables" property? You must do this for your variable...

As I stated earlier, your trigger needs to do something that your VB program can read. If you said INSERT INTO sometable before where you have SELECT * from...

Well, to create the triggers and/or set up service broker, you'd need to enlist a DBA's help. To build the CLR trigger, you would use Visual Studio to write...

To create a basic insert trigger you do something like this:

CREATE TRIGGER trig1

ON yourtable

AFTER INSERT

AS

INSERT INTO monitortable

SELECT somecolumns

FROM inserted

GO

Where "yourtable" is the...

You could use an insert trigger to fire off a process that would notify your VB application that a row was added. The trigger will execute a SQL statement...

I have fought this battle in a production environment before. For DBA's SQL Agent is easy because they have access to it and control over it but the Production...

I would definitely do this with a trigger on the table you want to monitor. You may not even need an application...just a report. If you want to...

What I usually do is remove the constraints, truncate the tables, then add the constraints back on before I load the data (to ensure referential integrity for the new load).

I...

You're correct that if you store the connection strings in a SQL configuration table they won't be encrypted. If using Windows authentication is an option for your connections, you...

For distributed transactions to work, you have to get DTC configured properly on ALL machines participating in the transaction. This includes your development workstations.

There is a free tool from...

I've never tried this but I believe you can pass the table name to the OLEDB Destination task from a package variable. Set the variable in your For Each...

Take a look in BOL for the DTUtil command line utility. It will let you move packages between MSDB and the file system and back.

You're going to spend a lot less time implementing configurations than you will trying to decipher what's stored in msdb. Configurations are very easy to set up. Once...