Showing posts with label package. Show all posts
Showing posts with label package. Show all posts

Wednesday, March 21, 2012

Retrieving native progress events for a 2000 package from SSIS. Is it possible?

Dear all,

AFAIK I don't think so. Let me know if possible and how.

I'm talking about a SSIS package which owns a Execute DTS 2000 Package Task and from there it calls a DTS 2000. Programatically, from our VB .Net front-end app we're seeing only SSIS events (when validate and execute methods are called) and any kind of information is provided from RCW proxy (I suppose that internally it gonna be created in order to send messages between managed and unmanaged code).

When a task inside our DTS 2000 fails we're awaring by means a "generic message" such this:

Error: System.Runtime.InteropServices.COMException (0x80040427): Execution was canceled by user.at DTS.PackageClass.Execute()at Microsoft.SqlServer.Dts.Tasks.Exec80PackageTask.Exec80PackageTask.ExecuteThread()

Thanks a lot for your time and comments,

hi guys any idea?

Monday, March 12, 2012

Retrieving and storing file timestamp

I have a package that processes a flat file, which is generated by a separate system each weekday around 3:30AM. I would like my package to store the timestamp of the input file and compare it to the timestamp of the next day's file. If they are the same, then the package can exit without reprocessing a particular file again.

So, my first question is whether a package variable can be updated so that its value will persist from one run to the next?

Second, what is the syntax to retrieve the file's timestamp, either directly from the file connection manager or within a script task?

Thanks,

Phil

Philsky wrote:

I have a package that processes a flat file, which is generated by a separate system each weekday around 3:30AM. I would like my package to store the timestamp of the input file and compare it to the timestamp of the next day's file. If they are the same, then the package can exit without reprocessing a particular file again.

So, my first question is whether a package variable can be updated so that its value will persist from one run to the next?

No! That'd be nice wouldn't it. I've requested similar functionality in the past although not formally via the Product Feedback Center. Perhaps you could submit it?

Philsky wrote:

Second, what is the syntax to retrieve the file's timestamp, either directly from the file connection manager or within a script task?

Thanks,

Phil

There's some code here that shows how you can access this information: http://blogs.conchango.com/jamiethomson/archive/2005/10/10/2253.aspx

Check lines 7 & 8 of the first code block.

-Jamie

Wednesday, March 7, 2012

Retrieve package varialbe from SQL configuration table?

Hi,

I have been trying to get a variable in my package to retrieve its data from the SQL configuration table.. so that in future i am able to alter them all easily.

On the SSIS > Package Configurations menu, there seems to only be the option to pass a variable FROM the package TO SQL

whereas what i want to do is infact the opposite...

any help would be much appreciated

regards

Chris

You were on the right track, you just second-guessed yourself.

On SSIS > Package Configurations menu set the following...

-Configuration type: 'SQL Server'

-Connection: 'Name of you SQL Server connection manager'

-Configuration table: 'Name of your SQL Server configuration table'

-Configuration filter: 'The name of the field that identifies the variable(s) you want to bring in to ssis'

This will not pass variables from SSIS to SQL Server but from the way you want it to, SQL Server to SSIS

|||Hi,

cheers for that, it turns out that it was wokring fine all the time!

I was expecting the variables to get updated when the package ran, but instead they seemt o get updated when the package is opened..

very odd

how does this affect the variables when the packages are run from outside of SSIS, i.e. scheduled in SQL Server?

Thanks!
|||

However the package is executed, it will always pull from that SQL Server config table to get the most current information.

So whether you execute the package in BIDS, or from a command line, or from SQL Server Agent, each will poll the table for current information each time. As you've found out, it also polls the table every time you open that package.

|||

Configurations are checked/updated on many occasions:

-Upon first opening up the package.

-In BIDS when you right-click on a package in the solution explorer and click 'reload with upgrade'.

-Run-time. Regardless of how it is executed (sql server agent, dtexec,BIDS).