What about breaking out the code for the users into its own package. Create another package for the developers which in turn calls the "user" package.

If the amount of data you're dealing with is small (few hundred thousand rows), the lookup, condition split will work. For larger data volumes, use the staging table and...

Are you referring to foreign keys? Then the answer would generally be yes.

Be aware that the SCD transform in SSIS does generally not scale well on large datasets.

Have you done a restore of the ReportServer database on that server recently?

The columns would not be the same as in the matrix but would appear the same as the dataset. That is the drawback to this approach.

SSRS does support columns. The setting is found under the layout tab of Report Properties. Be aware columns apply to the entire report and they will not appear until...

Another option would be to add a table to use only for export to CSV. Hide it when display but set the columns to export. I had the...

Are you trying to set them in the Report Manager GUI for running a report? If so, the calendar will most likely not work for you. Have you...

This is a known issue with SSRS 2005 and earlier; Reporting Services is memory dependent. On very large reports, you are consuming all available RAM and the server is...

I'd suggest returning the data to the report already in percentages.

No, only a single data set is supported.

It's available as a Global in the report, User!UserID. The tricky part will be for the subscription as I assume it will pass the system account in. What...

If you're going to use subscriptions, you won't be able to use NT Authentication on the data source as the report runs under the system account for a subscription. ...

Unfortunately no; they are locked at design time.