How to Manage Errors with one file

Hi,

I am pretty new in SSIS 2005, and I have some problems... I want to add logging and error management in my package. I found how to made logging. But for errors managing i have some difficulties.

In my package I have only a flat file source and an ole db destination. I want add errors management for both of them. So I create a connection manager for errors on a file. For both element i add redirect row for all available error type and then i add 2 flat file destination. I branch red arrows of flat file source and ole db destination to the flat file destination.

When i run packge i have an error which indicate me that file error is already take by another process... I don't understand why. And i don't want to create on file for each element on package. Have you any idea on why i have this error? Or how can i made what i want do?

Krest

Before going too far - could you checj if your redirect destination do not point to the same file as primary error file? What happens if you turn off package logging?

|||

Hi,

Thanks for you help.

So, i use the same file for the two flat file destination, because i want all my error in the same file. I i turn off logging (SSISmenu->logging and all checkboxes are not checked.

I have the same error as before. here is the exact error message [Flat File Destination 1 [806]] Warning: The process cannot access the file because it is being used by another process.

krest

How to make SSIS 2005 work like DTS 2000?

Hi!
Is it possible to make data flow in SQL Server 2005 Integration Services
looks like in SQL Server 2000 DTS?
I need to acive 2 goals:
1. If bcp fails on INSERT statement, for example, on primary key validation,
it must go on to the next row, but not to break SQL threat and stop.
2. I need log for failed errors. Not the log about which process failed, but
just the error source line.
And the final question: in SQL Server 2000 it was no probem to do it, so why
it has been removed from SQL Server 2005?
Thank you
Igor A. ChechetHi,
Igor A. Chechet wrote:
> Is it possible to make data flow in SQL Server 2005 Integration Services
> looks like in SQL Server 2000 DTS?
> I need to acive 2 goals:
> 1. If bcp fails on INSERT statement, for example, on primary key validatio
n,
> it must go on to the next row, but not to break SQL threat and stop.
> 2. I need log for failed errors. Not the log about which process failed, b
ut
> just the error source line.
>
your goals are easy to achieve with SIIS, too:
You have to open the editor of the task producing the error and
hit the "configure error output" button. There you have three
options:
- fail component
default, causes the package to stop
- ignore error
errors are ignored (see goal 1)
- redirect row
data is redirected to the error output (red arrow)
you can attach another Data Flow Destination component here
to write the failed rows to another table (see goal 2)
In the books online there's a tutorial for SIIS which shows the
most important features like logging, variables and configuration
files.
HTH,
Gerald|||Gerald, thank you for your advise!
I think that your suported method will help, but the problem is that the
error occured on the SQL Server Destination Task, and that's not possible to
create error output for it. BCP fails always on this task. Any ideas how to
handle it?
Thank you
Igor A. Chechet
"Gerald Aichholzer" <gerald.aichholzer@.gmx.net> '?/'' ? ''
'?: news:eYFYlFRpGHA.504@.TK2MSFTNGP05.phx.gbl...
> Hi,
> Igor A. Chechet wrote:
> your goals are easy to achieve with SIIS, too:
> You have to open the editor of the task producing the error and
> hit the "configure error output" button. There you have three
> options:
> - fail component
> default, causes the package to stop
> - ignore error
> errors are ignored (see goal 1)
> - redirect row
> data is redirected to the error output (red arrow)
> you can attach another Data Flow Destination component here
> to write the failed rows to another table (see goal 2)
> In the books online there's a tutorial for SIIS which shows the
> most important features like logging, variables and configuration
> files.
>
> HTH,
> Gerald|||Hi Igor,
Igor A. Chechet wrote:
> Gerald, thank you for your advise!
> I think that your suported method will help, but the problem is that the
> error occured on the SQL Server Destination Task, and that's not possible
to
> create error output for it. BCP fails always on this task. Any ideas how t
o
> handle it?
>
I'm not quite sure about this (I started with SIIS only two weeks ago),
but AFAIR you have to disable bulk insert to be able to create error
output. I think you have to select "table or view" (without "fast load")
in "data access mode".
HTH,
Gerald|||to log the rows in error, you have to disable the fast load option (like in
SQL 2000)
but this greatly slowdown the loading process.
regarding the size of the file you have to load, it could be bettter to load
the file into a temporary table (with no PK constraint)
then execute some SQL statement to identify duplicated rows and remove these
duplicated (or moving these rows into another table)
another option is to try to play with the sort task in the dataflow (there
is an option to remove duplicated rows)
or the aggregate flow to count the rows in double, then split the stream
into 2 streams (1 with unique rows (count=1), 1 with duplicated rows
(count>1))
finally the stream 1 with the unique rows will be inserted into the
destination using the fast load option and duplicated rows moved to the
error log table.
and another option...
simply insert the rows using the fast load option and use only 1 transaction
(no batch size)
if the insertion failed, then load again the rows but with a destination
where the fastload option is disabled and where the error output can be
used.
(solution not tested)
"Igor A. Chechet" <ichechet@.mail.ru> wrote in message
news:eMksqaPpGHA.4424@.TK2MSFTNGP05.phx.gbl...
> Hi!
> Is it possible to make data flow in SQL Server 2005 Integration Services
> looks like in SQL Server 2000 DTS?
> I need to acive 2 goals:
> 1. If bcp fails on INSERT statement, for example, on primary key
> validation, it must go on to the next row, but not to break SQL threat and
> stop.
> 2. I need log for failed errors. Not the log about which process failed,
> but just the error source line.
> And the final question: in SQL Server 2000 it was no probem to do it, so
> why it has been removed from SQL Server 2005?
> Thank you
> Igor A. Chechet
>

How to make SSIS 2005 work like DTS 2000?

Hi!
Is it possible to make data flow in SQL Server 2005 Integration Services
looks like in SQL Server 2000 DTS?
I need to acive 2 goals:
1. If bcp fails on INSERT statement, for example, on primary key validation,
it must go on to the next row, but not to break SQL threat and stop.
2. I need log for failed errors. Not the log about which process failed, but
just the error source line.
And the final question: in SQL Server 2000 it was no probem to do it, so why
it has been removed from SQL Server 2005?
Thank you
Igor A. ChechetHi,
Igor A. Chechet wrote:
> Is it possible to make data flow in SQL Server 2005 Integration Services
> looks like in SQL Server 2000 DTS?
> I need to acive 2 goals:
> 1. If bcp fails on INSERT statement, for example, on primary key validation,
> it must go on to the next row, but not to break SQL threat and stop.
> 2. I need log for failed errors. Not the log about which process failed, but
> just the error source line.
>
your goals are easy to achieve with SIIS, too:
You have to open the editor of the task producing the error and
hit the "configure error output" button. There you have three
options:
- fail component
default, causes the package to stop
- ignore error
errors are ignored (see goal 1)
- redirect row
data is redirected to the error output (red arrow)
you can attach another Data Flow Destination component here
to write the failed rows to another table (see goal 2)
In the books online there's a tutorial for SIIS which shows the
most important features like logging, variables and configuration
files.
HTH,
Gerald|||Gerald, thank you for your advise!
I think that your suported method will help, but the problem is that the
error occured on the SQL Server Destination Task, and that's not possible to
create error output for it. BCP fails always on this task. Any ideas how to
handle it?
Thank you
Igor A. Chechet
"Gerald Aichholzer" <gerald.aichholzer@.gmx.net> '?/'' ? ''
'?: news:eYFYlFRpGHA.504@.TK2MSFTNGP05.phx.gbl...
> Hi,
> Igor A. Chechet wrote:
>> Is it possible to make data flow in SQL Server 2005 Integration Services
>> looks like in SQL Server 2000 DTS?
>> I need to acive 2 goals:
>> 1. If bcp fails on INSERT statement, for example, on primary key
>> validation, it must go on to the next row, but not to break SQL threat
>> and stop.
>> 2. I need log for failed errors. Not the log about which process failed,
>> but just the error source line.
> your goals are easy to achieve with SIIS, too:
> You have to open the editor of the task producing the error and
> hit the "configure error output" button. There you have three
> options:
> - fail component
> default, causes the package to stop
> - ignore error
> errors are ignored (see goal 1)
> - redirect row
> data is redirected to the error output (red arrow)
> you can attach another Data Flow Destination component here
> to write the failed rows to another table (see goal 2)
> In the books online there's a tutorial for SIIS which shows the
> most important features like logging, variables and configuration
> files.
>
> HTH,
> Gerald|||Hi Igor,
Igor A. Chechet wrote:
> Gerald, thank you for your advise!
> I think that your suported method will help, but the problem is that the
> error occured on the SQL Server Destination Task, and that's not possible to
> create error output for it. BCP fails always on this task. Any ideas how to
> handle it?
>
I'm not quite sure about this (I started with SIIS only two weeks ago),
but AFAIR you have to disable bulk insert to be able to create error
output. I think you have to select "table or view" (without "fast load")
in "data access mode".
HTH,
Gerald|||to log the rows in error, you have to disable the fast load option (like in
SQL 2000)
but this greatly slowdown the loading process.
regarding the size of the file you have to load, it could be bettter to load
the file into a temporary table (with no PK constraint)
then execute some SQL statement to identify duplicated rows and remove these
duplicated (or moving these rows into another table)
another option is to try to play with the sort task in the dataflow (there
is an option to remove duplicated rows)
or the aggregate flow to count the rows in double, then split the stream
into 2 streams (1 with unique rows (count=1), 1 with duplicated rows
(count>1))
finally the stream 1 with the unique rows will be inserted into the
destination using the fast load option and duplicated rows moved to the
error log table.
and another option...
simply insert the rows using the fast load option and use only 1 transaction
(no batch size)
if the insertion failed, then load again the rows but with a destination
where the fastload option is disabled and where the error output can be
used.
(solution not tested)
"Igor A. Chechet" <ichechet@.mail.ru> wrote in message
news:eMksqaPpGHA.4424@.TK2MSFTNGP05.phx.gbl...
> Hi!
> Is it possible to make data flow in SQL Server 2005 Integration Services
> looks like in SQL Server 2000 DTS?
> I need to acive 2 goals:
> 1. If bcp fails on INSERT statement, for example, on primary key
> validation, it must go on to the next row, but not to break SQL threat and
> stop.
> 2. I need log for failed errors. Not the log about which process failed,
> but just the error source line.
> And the final question: in SQL Server 2000 it was no probem to do it, so
> why it has been removed from SQL Server 2005?
> Thank you
> Igor A. Chechet
>sql

How to make input columns unavailable for downstream components?

Hi,

In a SSIS Data flow task, whatever you are doing with the input columns that come from a Data source like a Flat File Source, these columns are always visible and available as input columns for all Transformation and Destination components in the Data flow.

Our Custom Component is a column mapping component that transforms many input columns into many oputput columns and we would like that the used input columns are not available anymore to the downstream components...

Is that possible?

I saw that with the Unpivot component it is possible to make some input columns unavailable to downstream components...So I think there is a way to do the same in a custom component...

Thanks for any help,

David

David-Paris wrote:

Hi,

In a SSIS Data flow task, whatever you are doing with the input columns that come from a Data source like a Flat File Source, these columns are always visible and available as input columns for all Transformation and Destination components in the Data flow.

Our Custom Component is a column mapping component that transforms many input columns into many oputput columns and we would like that the used input columns are not available anymore to the downstream components...

Is that possible?

I saw that with the Unpivot component it is possible to make some input columns unavailable to downstream components...So I think there is a way to do the same in a custom component...

Thanks for any help,

David

If the component you are building is a synchronous component then the rows will be available downstream. That is simply inherent in the nature of the data-flow.

Unpivot is an asynchronous component (just like Merge Join, Union All, Sort etc...). You can think of asynchronous as meaning that the "shape" of the data changes when it goes through the component (that's not really what it means but for simplicity - it works).

You can make your custom component asynchronous if you want but there isn't much point - it will degrade performance.

-Jamie

How to make Application.LoadPackage() and Package.Execute() to run asynchroniously?

Hi,

I am trying to execute a SSIS package programmatically. When a user drops a file in a shared folder, we execute the package based on that file. I am using SqlServer.DTs.Runtime.Application.LoadPackage() and SqlServer.DTs.Runtime.Package.Execute() functions each time to do this.

The problem is, when, say two people drop a file, the second one will not execute untill the first one is completed. I also tried only calling LoadPackage() a single time, and then storing the instance and calling Execute() in a different thread on each file drop; although the blocking still occurs. I assume the Package object is the one doing the blocking then behind the scenes.

Is there any built in functionality to make these functions (Application.LoadPackage() and Package.Execute()) run async? If not, has anyone had much success sticking these calls into a thread? I tried sticking these calls into a thread using System.Threading.ThreadPool.QueueUserWorkItem(), and this appears to work, however it randomly crashes the program when I drop multiple files one after the other. The exception also isn't too helpfull (pasted below):

"The package failed to load due to error 0xC0011008 "Error loading from XML. No further detailed error information can be specified for this problem because no Events object was passed where detailed error information can be stored.". This occurs when CPackage::LoadFromXML fails."

So, is what I am trying to do possible? I know it must be, because when I was using .NET 1.X, I was just calling dtexec via the command line, and dtexec was able to execute many packages simultaneously....

Thanks for any help,

DrewThe calls are synchronous, but each package object is independent - so if you create a thread per incoming file, create a new package object and do LoadPackage/Execute you should get the behavior you need.

The random errors you see are probably caused by your code trying to load the DTSX file before it was fully copied. So SSIS tries to read partial file and throws the error reporting it is not a valid XML file. You need some way to ensure you only load a file when it is ready, e.g. try opening it exclusively until you succeed (it will fail if someone is still writing to the file).

How To Load Periodic SnapShot Fact Table With SSIS

I need help from you data warehouse / SSIS experts out there! I have a Transaction Fact Table with dollar amounts as the measurements. The grain is one row per transaction. I want to roll this up into a Monthly Periodic Snapshot based on 5 keys. I am having no problem where there is transaction data for each month.

However, the problem I am having is - how do I gracefully insert the Monthly rows for the five keys where there was no activity in the transaction fact table - I am sure there is a slick way to do this with SSIS but I am definitely having a mental block on how to accomplish this. Any help would be appreciated!

Hopefully you have a method of deriving all possibly combinations of the 5 key columns. Personally I would do this by extracting all possible values from the dimension tabes, unioning them together but where each column creates a new column in the output from the UNION ALL and then use the Aggregate component to produce all of the combinations.

Once you have done that you can use a MERGE JOIN component to join to your dataset and produce nulls/zeros for teh fact values for all of the missing rows.

-Jamie

|||

Thanks Jamie. I will give that a shot.

-Steve

How to load Fact table and dimension using SSIS?

Hi All,

I am just curious to know how I can load data from a data warehouse to an Analysis Service Cube (both to the fact tables and dimensions).

Does any body have some way to achieve this?

I appreciate if any body provide me a good material which describe this scenario.

Sincerely,

--Amde

Amde wrote:

Hi All,

I am just curious to know how I can load data from a data warehouse to an Analysis Service Cube (both to the fact tables and dimensions).

Does any body have some way to achieve this?

I appreciate if any body provide me a good material which describe this scenario.

Sincerely,

--Amde

this link should help: http://www.microsoft.com/technet/prodtechnol/sql/2005/rtbissas.mspx

How to launch programatically a SSIS package?

Dear all,

I wrote this post others times but the answer did not satisfied so that I'd like to know if really anyone has ever used or experienced with this possibility. No by .Net language rather than Vb 6.0 or ASP or even instanciacing DMO library.

According this link http://support.microsoft.com/?kbid=817248 it seems possible but I haven't idea if possible keeping in mind that it has been made by yourself no for others... So that, I mean, these assemblies comes along with Sql Server 2005 installation.

Thanks a lot for your support,

It is much simpler than the interop path described in that KB article. Just reference the typelibrary in DTS.DLL and use Application & Package classes from there.|||

Hi Michael,

What do you mean? From VB 6.0? Can you explain better?

Thanks a lot

|||

Enric,

I wrote an answer to this question on another thread that you started.

Please see http://forums.microsoft.com/MSDN/showpost.aspx?postid=408720&siteid=1

Best Regards,

PJ

|||

Yes, I know and I beg you pardon for your time dedicated for me in this post.

Such anwser half-satisfied so that I'm looking further explanations.

|||

enric12879 wrote:

Hi Michael,

What do you mean? From VB 6.0? Can you explain better?

Thanks a lot

The KB article describes how to build the typelibrary from managed code, but SSIS already has a native typelibrary and native COM objects that you can use directly from VB 6.

I don't have VB 6.0 around, so I can't send the detailed instructions, but VB can call any COM object. You add the typelibrary to the Project/Reference dialog, and then you can use any COM object from this typelibrary. The typelibrary lives in Program Files\Microsoft SQL Server\9.0\DTS\Binn\Dts.Dll.

|||

I've taken that file but when I try to register by regsvr32 fails.

Error in loadlibrary("c:\windows\system32\dts.dll")

Sql25k is installed on another server and VB in another one. Maybe the problem is there.

|||

enric12879 wrote:

Sql25k is installed on another server and VB in another one. Maybe the problem is there.

Yes, it is definetely a problem. To run the package, you need much more than DTS.DLL - the SSIS needs to be installed on the machine where the package is executed (both for technical and licensing issues).

If you want to run the package on client, install full SSIS on this machine. You don't need to register DTS.DLL - it should already be registered.

If you want to execute the package on server from a program running on another machine, the simplest way to do this is via Agent. Create a SQL Agent Job that will run the package (via UI on server machine, but you can also do it programmatically). Then invoke this job from your client code.

I'm not Agent expert, so I'm not sure what is the best way to communicate with Agent from VB - obviously you can connect to SQL Server using ADO and call Agent stored procedure; but DMO may also work.

|||

Hi Michael,

Thanks for your quick response. We current have got a vb application which is always running and checking up a specified filesystem. If there to find files it fires a DTS on the contraty it follows listening... Sql Agent functionality doesn't serve for our purposes but you are saying that I install SSIS in my workstation but how? Is it possible to install only SSIS features?

I think understand the SSIS data model now. DTS.DLL is then a COM object which can be called from Vb 6.0 and give you access to any SSIS whereas the rest ones are simply assemblies.

repldts.dll

\Program Files\Microsoft SQL Server\80\COM

C0M ?

DTS.dll

\Program Files\Microsoft SQL Server\90\DTS\Binn

C0M ?

Microsoft.SQLServer.ManagedDTS.dll

\Program Files\Microsoft SQL Server\90\SDK\Assemblies

.NET

Microsoft.SQLServer.DTSRuntimeWrap.dll

\Program Files\Microsoft SQL Server\90\SDK\Assemblies

.NET

Microsoft.SqlServer.DTSPipelineWrap.dll

\Program Files\Microsoft SQL Server\90\SDK\Assemblies

.NET

Our idea is to avoid .Net languages for to build a new solution. I know that it's stupid and silly but I can't decide regarding budget and that stuff...

Thanks again for your comments,

|||Where do you want the package to actually run - on the machine where your code runs (client), or on another machine (server)?
If on client, install SSIS - run SQL 2005 setup, check SSIS checkbox, you don't have to install SQL Server and other components. You do need a license for this machine however.
If on server - use the Agent. You don't need to create a schedule, so you are not restricted by Agent's scheduling capabilities. You will just use it as a remote service for running SSIS packages on demand. You will start the packages from the client.
BTW, the choices and recommendations above don't depend on whether you are using native or managed languages.|||

Hi again,

SSIS packages are stored in the server (msdb...)

I don't understand how after to define a job you can do that it is awared whether exists a file or not in a path

I meant, we've got a fixed path:

E:\..\..\..\SERVER\DTS\

And from there a folder for each ASP application or whatever. Each old DTS is fired when VB service find a .nul file or .TXT sended from a JCL from HOST, via FTP, email, etc..

Up to the moment I've done a SSIS which run another SSIS using a script task with .net.

Maybe a SSIS always running and checking for that structure and firing SSIS from himself? It's sound odd.

|||I don't understand where each code runs. It does not matter where the package is stored, like .EXE file it can be stored in one place, but runs where you execute it.

You write that you run child SSIS package from Script Task - this obviously happens on server, where SSIS is already installed. Why don't you run your VB code on the same machine?

How to launch package from client machine, display progress and finally results?

Please help. I'm completely new to SSIS, and I was hoping someone could point me in the right direction(s).

I am developing a winforms client app, and I need to be able to provide the user with the ability to import data in CSV format into our application's database.

I'd like to use SSIS if possible, as long as what I am trying to do isn't near impossible.

I'm thinking of a UI where the user can specify a flat file (CSV) to upload and be processed by an SSIS package on a remote database server.

This package will be responsible for validating the CSV file and inserting data into the database as appropriate.

Is there a way I can:

launch an SSIS package remotely, from a winforms app on the client machine that is not running SQL server (preferably asynchronously) -- and pass it some parameters, including the import file itself

(optionally) provide progress feedback to the client pc to let them know it is being processed

display a nice SSRS report on the client upon completion that tells them exactly what the success/failure of the import was (how many rows processed, which ones failed and why, etc)

Any helpful examples, links, etc would be most appreciated.

Thanks in advance!

1 - How about hosting it on the SQL Server, and start ith through T-SQL. The best way to get the asycn behaviour is to use a job.

How to: Run a Package Using a SQL Server Agent Job
(http://msdn2.microsoft.com/en-us/library/69d3958c-6abc-41ae-8428-312917867c9a.aspx)

2 - You will not get anything back from the job, as it you have no handle back to it. You could turn on logging in your package, perhaps to SQL Server, and then query the table on a polling basis to provide progress to a user.

3 - A combination of SQL logging and some custom logging within the package and you should be able to achieve this.

How to launch a SSIS package from VB or whatever

Dear all,

I am looking for any snippet of code where you can launch a SSIS package by DMO or VB 6.0. I read that it was posible to call dts.runtime assembly from VB 6.0 but at first it might be converted or something like that.

Issue comes from the moment that we’ve got an ASP 3.0 scheduler for hundreds of dts and now we have to migrate them to sql25k.

Thanks in advance for any info regarding this,

Hey there Enric,

I'm no expert in SSIS.. but I AM reading the Wrox book "Professional SQL Server 2005 Integration Services" which has a chapter on using SSIS with external applications.

If you get the book just look at chapter 17 and you'll find the info you need.

OR you could go to Wrox.com and download the sample code for chapter 17. It contains sample VB to call an SSIS package.

Basically you have to use the Microsoft.SqlServer.Dts.DtsClient namespace...

You import that namespace and use it to connect to the package...

Imports Microsoft.SqlServer.Dts.DtsClient

Then use an DtsCommand to execute the the package.

I don't want to post Wrox's sample code here (don't want no trouble) but if you search in books online for DtsCommand you should find stuff....

Its a bit silly calling an SSIS package with a DtsCommand isn't it?

Very confusing..

PJ

|||

The reason for the false naming is that the product was well into the development cycle when the decision was made to change the name from DTS to SSIS. That decision was actually made around Q3 2004, almost 4 years after development started.

At that late stage in the game it was considered too much of a job to go through and change all the code from DTS* to SSIS*. Its a shame but can't be helped.

Do as all techies do...blame the marketing department :)

-Jamie

|||

On Books online at

http://msdn2.microsoft.com/en-us/library/aa337077.aspx

there's an extensive coverage on how to run SSIS packages remotely.

You may need to be a bit seasoned developer to go through it and run it though, as the documentation is not a step-by-step instruction.

Rgds,

How to launch a SSIS package from VB or whatever

Dear all,

I am looking for any snippet of code where you can launch a SSIS package by DMO or VB 6.0. I read that it was posible to call dts.runtime assembly from VB 6.0 but at first it might be converted or something like that.

Issue comes from the moment that we’ve got an ASP 3.0 scheduler for hundreds of dts and now we have to migrate them to sql25k.

Thanks in advance for any info regarding this,

Hey there Enric,

I'm no expert in SSIS.. but I AM reading the Wrox book "Professional SQL Server 2005 Integration Services" which has a chapter on using SSIS with external applications.

If you get the book just look at chapter 17 and you'll find the info you need.

OR you could go to Wrox.com and download the sample code for chapter 17. It contains sample VB to call an SSIS package.

Basically you have to use the Microsoft.SqlServer.Dts.DtsClient namespace...

You import that namespace and use it to connect to the package...

Imports Microsoft.SqlServer.Dts.DtsClient

Then use an DtsCommand to execute the the package.

I don't want to post Wrox's sample code here (don't want no trouble) but if you search in books online for DtsCommand you should find stuff....

Its a bit silly calling an SSIS package with a DtsCommand isn't it?

Very confusing..

PJ

|||

The reason for the false naming is that the product was well into the development cycle when the decision was made to change the name from DTS to SSIS. That decision was actually made around Q3 2004, almost 4 years after development started.

At that late stage in the game it was considered too much of a job to go through and change all the code from DTS* to SSIS*. Its a shame but can't be helped.

Do as all techies do...blame the marketing department :)

-Jamie

|||

On Books online at

http://msdn2.microsoft.com/en-us/library/aa337077.aspx

there's an extensive coverage on how to run SSIS packages remotely.

You may need to be a bit seasoned developer to go through it and run it though, as the documentation is not a step-by-step instruction.

Rgds,