How do I add a static column to a matrix?

Folks,
I'm getting data back from the database in the following format:
row_id | col_Name | col_Value
0 | ID | 10
0 | Name | First
0 | Jan | 1
0 | Feb | 2
1 | ID | 20
1 | Name | Seconds
1 | Jan | 10
1 | Feb | 20
...
We are grouping based on the row_id db column, thus creating dynamic columns
for ID, Name, Jan, Feb, etc.
However, I need to customize the ID and Name column which is, to my
understanding, not something that can be done if they are dynamic columns in
the matrix.
So, what I was thinking of doing was to make two static columns, ID and
Name, and then filter those rows out of the dynamic columns. However, when I
make a second ColumnGrouping in the RDL file for these, and define the two
static columns, what happens is that they appear set up such that these
columns would be in a separate row, rather than off to the left of the rows
of dynamic columns (hopefully I'm explaining this well enough).
What would be the best way to accomplish this, presuming that we can't
simply have the returned data changed to a better format?
Thanks!
randyAssuming you want to transform your table to:
ID | Name | Jan | Feb
10 | First | 1 | 2
20 | Seconds | 10 | 20
etc.
The easiest is to tweak your SQL, but I am assuming this is the result of a
SP that you can't since you said:
> What would be the best way to accomplish this, presuming that we can't
> simply have the returned data changed to a better format?
I'm not sure if you can, but you might have to do this with a custom code
module to transform your data and then bind the report to the dataset from
code. Maybe someone else knows way to modify the underlying dataset
structure.
"Randy Chapman" <RandyChapman@.discussions.microsoft.com> wrote in message
news:5F87A271-7591-4453-975F-06394CC8E2A8@.microsoft.com...
> Folks,
> I'm getting data back from the database in the following format:
> row_id | col_Name | col_Value
> 0 | ID | 10
> 0 | Name | First
> 0 | Jan | 1
> 0 | Feb | 2
> 1 | ID | 20
> 1 | Name | Seconds
> 1 | Jan | 10
> 1 | Feb | 20
> ...
> We are grouping based on the row_id db column, thus creating dynamic
> columns
> for ID, Name, Jan, Feb, etc.
> However, I need to customize the ID and Name column which is, to my
> understanding, not something that can be done if they are dynamic columns
> in
> the matrix.
> So, what I was thinking of doing was to make two static columns, ID and
> Name, and then filter those rows out of the dynamic columns. However,
> when I
> make a second ColumnGrouping in the RDL file for these, and define the two
> static columns, what happens is that they appear set up such that these
> columns would be in a separate row, rather than off to the left of the
> rows
> of dynamic columns (hopefully I'm explaining this well enough).
> What would be the best way to accomplish this, presuming that we can't
> simply have the returned data changed to a better format?
> Thanks!
> randy
>

how come the validation doesn't seem to end keep on running?

Hi folks,

it is me again. Just want to enquire how come with the control flow of the Data flows been set appropriately, why when it is executed manually in the sql server 2005 file system, the validation shows the incorrect flow of data flows been executed and doesn't seem to end? Thanks in advance

Regards,

Ken

Hi Ken,

It's probably just me combined with the fact I've had no coffee yet, but I don't follow. Can you restate the issue?

Thanks,
Andy

|||

Hi Andy,

Thanks again for helping this newbie. Ok I have input my package into the SQL Server 2005 file system located under Stored Packages. I run them manually which displays a validation report on its progress. But i notice from the validation report that it doesn't run the validation check as how I drew the flow of the components and it seems to be running endlessly. Is there a way to edit the package so that it can signal the end of the package.

|||

Hi Ken,

You are most welcome - I was a newbie myself not long ago.

If I'm understanding you correctly, either your package is stuck in Validation (or appears to be) or stuck in execution (or appears to be).

If the package is stuck in validation, you can change the Package level property DelayValidation to True. The package will load and attempt to run. Any errors will likley cause it to crash, but it may give you insight into why it is behaving in this fashion.

If the package is stuck in execution, I suggest you implement logging. Also consider custom logging using Execute SQL Tasks on the Control Flow and in OnError event handlers.

Hope this helps,

Andy

|||Are you executing child packages from a parent package, by any chance?