Showing posts with label expressions. Show all posts
Showing posts with label expressions. Show all posts

Friday, March 23, 2012

Row Sampling Transform

The "Sampling Value" is now exposed on the Control Flow so we can use expressions to determine the amount of rows that flow through a pipeline . What is missing as far as I can see is the ability to say "ALL".

I know I could remove the transform but what if I do not want to touch the packages. The way i will set the value is through DTExec.

This would be useful for testing in that I could have a series of runs and each one ramping up the row counts. The final one would be "ALL" but without something on the transform to say "ALL" I would need to determine the count of rows up front. A waste IMHO.
I suppose the workaround is to use the % sampling transform and specify 100%.
Allan
www.sqlis.com
Allan\stick it on the SSIS Requests thread Allan...

Wednesday, March 21, 2012

Row Number Tranformation

I have looked to no avail...

Anybody see a dynamic way to set the seed in the Row Number Transformation? I do not see any expressions property and the only property that takes a variable is the FINAL number...

I would have though that a very common use would be to get the maximum IDENTITY from a table and use that value (after adding one) as the starting number for the rows being imported...

See if this help

http://www.sqlis.com/default.aspx?93

|||That was it. Missed it the first (and second and third) time I read it. The expression gets set at the Control Flow level instead of the individual component level.

Thanks.
|||To be clear, the Seed is a property and that property accepts expressions. For Data Flow components, expressions are set on the parent Data Flow, not the transformation. In otherwords tasks can have expressions, and the Data Flow is a task. Transformations or components do not support expressions directly, but they can mark their properties as supporting expresssions, but available through the task. The component author can choose to expose a property via an expression, and indeed this has been done for the Row Number Transformation, but as with all components you need to go up to the (Data Flow) task to see this.|||

Hi

I've read the previous steps and trying to initialise the seed property.

I retrieve the latest id from a table in the database which needs to be the starting seed. This is set to a variable of type Int32, there is no decimal option. When I try to use this variable to set to the seed I get a 'cannot convert 'System.Int32' to 'System.Decimal', that's ok, understand that but when I do cast it using (DT_DECIMAL,2) it then complains it cannot convert 'System.Single to 'System.Decimal'

Please help!!

|||

Sorry about that, there is a strange problem with the current release. Sometimes SSIS decides that a literal 1 is decimal, and sets the property type to System.Decimal. A quick fix is to close the package, right-click View Code, and search for the component name, this should get you to the <component> element. Then below that look at the <property> for seed/increment and fix the type, changing it to System.Int32.

A refresh will be out soon that fixes this. Unfortunately it is still possible to get stuck in this problem as component properties are not really strongly typed, they infer the type from the value, and it can even change in some circumstances. Not very nice behaviour, but ultimately beyond my control.

Row Number Tranformation

I have looked to no avail...

Anybody see a dynamic way to set the seed in the Row Number Transformation? I do not see any expressions property and the only property that takes a variable is the FINAL number...

I would have though that a very common use would be to get the maximum IDENTITY from a table and use that value (after adding one) as the starting number for the rows being imported...

See if this help

http://www.sqlis.com/default.aspx?93

|||That was it. Missed it the first (and second and third) time I read it. The expression gets set at the Control Flow level instead of the individual component level.

Thanks.
|||To be clear, the Seed is a property and that property accepts expressions. For Data Flow components, expressions are set on the parent Data Flow, not the transformation. In otherwords tasks can have expressions, and the Data Flow is a task. Transformations or components do not support expressions directly, but they can mark their properties as supporting expresssions, but available through the task. The component author can choose to expose a property via an expression, and indeed this has been done for the Row Number Transformation, but as with all components you need to go up to the (Data Flow) task to see this.|||

Hi

I've read the previous steps and trying to initialise the seed property.

I retrieve the latest id from a table in the database which needs to be the starting seed. This is set to a variable of type Int32, there is no decimal option. When I try to use this variable to set to the seed I get a 'cannot convert 'System.Int32' to 'System.Decimal', that's ok, understand that but when I do cast it using (DT_DECIMAL,2) it then complains it cannot convert 'System.Single to 'System.Decimal'

Please help!!

|||

Sorry about that, there is a strange problem with the current release. Sometimes SSIS decides that a literal 1 is decimal, and sets the property type to System.Decimal. A quick fix is to close the package, right-click View Code, and search for the component name, this should get you to the <component> element. Then below that look at the <property> for seed/increment and fix the type, changing it to System.Int32.

A refresh will be out soon that fixes this. Unfortunately it is still possible to get stuck in this problem as component properties are not really strongly typed, they infer the type from the value, and it can even change in some circumstances. Not very nice behaviour, but ultimately beyond my control.

sql

Tuesday, March 20, 2012

Row Level Security Expressions in Yukon

Has row level security expressions made it into Yukon or has it been dropped
? I see its in the white paper but was wondering if it looks like it will ma
ke it at this point in the beta? No I wasn't invited to the beta so I can't
post to that newsgroup. Tha
nks!I can't really discuss what features are in or out of Yukon.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.