I'm presuming you have an ActiveXScript task like

Function Main()

  DestinationColum("Col001") = Source("Col001")

etc...

If you put the On Error Resume Next statement before the line you want to capture error information for,...

Ok, this is a huge step forward to solving your problem.

"Error:  -2147467259 (80004005); Provider Error:  5 (5)" is basically Access Denied. So the credentials being used to access the INGRES...

The format for the replaceable parameters in the templates is,

< parameter name , datatype , example data or default value >

The 'sysname' that is referred to in the templates is...

You also don't have the overhead of maintaining the cursor data in memory.

These are statistics that are generated/used by the query optimiser when it's generating an execution plan. For what should be apparent reasons now, it is not a good idea to...

Just because you can successfully execute the DTS package manually, don't rule out any security problems. DTS executes with the security credentials of the process that started it. So if...

Lets try and get past why you would store the package in SQL Server, but not execute it in SQL Server. I mean that way you'd be able to take...

Cool, thanks Chris always love ways to avoid triggers and such

Only one record in the whole table can be set to 1, all other records must be 0.

At present the field could be edited/updated via Query Analyzer, possibly in the...

Sorry, I can't reproduce your results, I don't have any databases where the MS_Description property is used.

Honestly, I can't recall using it in any of the databases I've worked on over the...

I'd be inclined to say you'll have to pre-process the file and insert the row terminators. Something like running a short VBScript to insert CR+LF into the appropriate places. Once...

In this case, the debugging won't work as you explain it. The statements in the procedure are not being executed, only the CREATE PROCEDURE statement is being executed.

The uppercase N at the start of a string signifies that the string is in unicode format.

Most of the SQL Server object names, functions and stored procedures use unicode string...

This sort of what you're looking for?

Create table #tblDataDictionary (
    table_id [sql_variant]
    , table_name [sql_variant]
    , column_order [sql_variant]
    , column_name [sql_variant]
    , column_description [sql_variant]
)

INSERT INTO #tblDataDictionary
SELECT
    o.[id] as...

Yes you can have SQL Server running under a plain user account, but to get proper functionality (SQL Agent, SQL Mail, registry access, etc...) you need to assign a few...