Showing posts with label component. Show all posts
Showing posts with label component. Show all posts

Wednesday, March 21, 2012

Creating a Script component using SSIS Object model

I had a SSIS Package which was developed on Beta Version Of SSIS, Now We have Standard Edition Of SSIS(Sql2k5) Installed.
In the Package we have One Flat file Source, One Script Component and A Sql Server as Target, We are programaticaly creating the package, Now When we open this Package in the Designer and Try to Run We get this error
"The script component is configured to pre-compile the script, but binary code is not found. Please visit the IDE in Script Component Editor by clicking Design Script button to cause binary code to be generated. "
Now when we just open the Script Designer and close it, The package runs.
I found the Error description at this link
http://msdn2.microsoft.com/en-us/library/microsoft.sqlserver.dts.runtime.hresults.dts_e_binarycodenotfound.aspx
but could not find any help on this.

Same thing use to work on Beta version now it is now working.
From my understanding the problem is that in beta version, the script use to run at runtime, Now what they have done is that they generate a compiled code out of script and run.
My problem is that since i am using C# code to generate the package, How Will I Create a Binary Code out of Script.

Creating the binary code is very easy. Go into the script component, click on "Script..." button to bring up VSA (i.e. the script editor) and then close VSA down again. This will create the binary code for you.

-Jamie

|||

What changed is that the default value of the Precompile property changed from False to True.

If you are not precompiling your scripts, all you need to do is change the value of that property on the Script component. Note that this will give you a significantly smaller package file, but you'll pay a small performance penalty at runtime.

-Doug

Sunday, March 11, 2012

Creating a new Integration Service Component

Good morning everybody,

I made a Java application to pre-process portuguese texts (stopwords, stemming, BOW creating, etc.)

I want to transform this application on a Integration Service component. I understand I will have to code this new component from zero. But I have no idea on how to start.

I'm reading and testing several tutorials on Integration Services that came with the SQL Server install package but none of them has clues on developing new components. These tutorials seams more focused on demostrate the (awesome) capabilities of Integration Services.

Is there any tutorials on how to implement new components to Integration Services ?

Any help will be very appreciated.

Thanks a lot,

-Renan Souza

Hello, Renan

A few Integration Services Samples are available at codeplex : http://www.codeplex.com/MSFTISProdSamples

you might also want to check this out: "SQL Server Integration Services (SSIS) Hands on Training - Creating Custom Components" at http://www.microsoft.com/downloads/details.aspx?familyid=1c2a7dd2-3ec3-4641-9407-a5a337bea7d3&displaylang=en

Hope this helps

|||

Thanks a lot for your prompt reply.

It was very helpfull, as usual.

Wednesday, March 7, 2012

Creating a Data-Flow Component

I try to create a new Data-Flow Component.

In Books-Online I found this link:

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.de/dtsref9/html/9d96bcf5-eba8-44bd-b113-ed51ad0d0521.htm

and the following pages.

But I have not realized, how I have to create the new Data-Flow Component.

What I to do for my first "Hello World"-Component?
SQL Server also includes 4 code samples of working data flow components, one each of the 4 types that can be created. This is a good place to start.

-Doug|||

I have found the example and have installed the "ADO Source"-Component.
The installation is a little bit more difficult, than I thought.

But it is a good example to start.

Thanks - Loom

|||Since you will be using the same series of steps to deploy and test your own data flow components, best to resign oneself!

Note that Visual Studio 2005 supports post-build event scripts that you can use to copy your updated assembly to the PipelineComponents folder, remove the previous version from the global assembly cache, and install the latest version.

Before you get started, read the docs too to make sure that you can't do what you want to do with the Script Component...it will save you a massive amount of time and coding overhead!

-Doug

Saturday, February 25, 2012

Creating a custom transformation component Walkthrough

Microsoft published a "Creating a custom transformation component Walkthrough" published on

http://www.microsoft.com/downloads/details.aspx?FamilyID=1c2a7dd2-3ec3-4641-9407-a5a337bea7d3&DisplayLang=en

Does anyone know where to get the Hands-On Lab Files mentioned?

Thanks

Alex

I could not see any mention of files over and above the word document. There are plenty of samples available separately on MS Downloads, just search for SSIS.|||

On page 15, Task 1, Step 1 a path "c:\ssis hands-on-lab\scratch\.... " is mentioned. I just wanted to take a look at the regcomponent shown in setp 3.

Thanks anyway

|||

You create that yourself by going through pages 1 to 14!

-Jamie

|||http://www.microsoft.com/downloads/details.aspx?FamilyID=fc4de21d-9c5b-4b1d-aeef-ce43aadab4e4&DisplayLang=en

Creating a custom transformation component Walkthrough

Microsoft published a "Creating a custom transformation component Walkthrough" published on

http://www.microsoft.com/downloads/details.aspx?FamilyID=1c2a7dd2-3ec3-4641-9407-a5a337bea7d3&DisplayLang=en

Does anyone know where to get the Hands-On Lab Files mentioned?

Thanks

Alex

I could not see any mention of files over and above the word document. There are plenty of samples available separately on MS Downloads, just search for SSIS.|||

On page 15, Task 1, Step 1 a path "c:\ssis hands-on-lab\scratch\.... " is mentioned. I just wanted to take a look at the regcomponent shown in setp 3.

Thanks anyway

|||

You create that yourself by going through pages 1 to 14!

-Jamie

|||http://www.microsoft.com/downloads/details.aspx?FamilyID=fc4de21d-9c5b-4b1d-aeef-ce43aadab4e4&DisplayLang=en