SELECT

COUNT(*) OVER (PARTITION BY name), name, surname

FROM

Info

Are you using a 'SQL Server Destination' in your dataflow? SQL Server Destination only works at the server-side. If your package has to connect to a remote server, use the...

IsEmpty (without a space) is a MDX function. In SSRS use IsNothing e.g.

=IIf(IsNothing(Fields!ClientID.Value), True, False)

Peter

The Join function in SSRS expects an array of objects or strings as its first argument. It concatenates all string values of the elements in the array and separates them...

You can add a calculated field NewField to your dataset with the expression

=IIF(Fields!FieldA.Value="Y",0,Fields!FieldB.Value)

Now can summarize on the field NewField in the group footer.

Peter

Try

Dim connection As ConnectionManager

connection = Dts.Connections("flatfileconn")

' Store it in a defined variable flatfileconnString

Dts.Variables("flatfileconnString").Value = connection.Properties("ConnectionString").GetValue(connection)

' Or display

MsgBox(CStr(connection.Properties("ConnectionString").GetValue(connection)))

Success

Peter

Note that right now you are using string concatenation to build you query. If @[System::ErrorDescription] contains a single quote, the statement will become invalid, which probably explains the error you...

Maybe the error description contains characters which breaks the statement. Try parameterizing the statement.

Peter

I guess you forgot the parentheses. Try

"INSERT stg.Errors(error_code)

VALUES (

'' + @[System::ErrorCode] + '')

"

Peter

Use the menu item "Add Existing Item" to re-include the package. Don't use the "Add Existing Package" menu item. It will make a copy of your package.

Peter

After some googling I found two solutions:

1. use a dummy select statement as the first select statement in your procedure to provide the metadata:

ALTER procedure [dbo].[up_test]

as

begin

set nocount...

The 'column has no name' error is caused by the statement 'select 1/0'. I suggest to use the RAISERROR statement for raising errors. I tested this using the following procedure:

create...

Oops, you're absolutely right! I agree with Peter Rijs, it's easy to make a mistake without proper testing. Anyway, the idea was clear, I suppose.

Peter

I hope I do unstand your question this time.

Set the following label/value pairs as the available (non-queried) values to your parameter (let's name it AgeRange):

18-40, 18040

41-60, 41060

61 and above, 61999

Now...

As an alternative to using T-SQL, you can add a calculated field to your report dataset and use an expression like:

=Switch(

Fields!Age.Value >= 18 And Fields!Age.Value <= 40, "18-40",

Fields!Age.Value >= 41...