Report deployement

Hi,

I have a heavy report:

- 18 datasets (some with filters)

- 15 parameters

- about 10 tables (some with groups)

- lots of TextBox static or calculated (50 at least)

- and a little report footer

Anyway…

I’m using Visual Studio 2005 to deploy my report on a server. Recently, my deployments became very long and now, Visual Studio throw Timeouts when I deploy it. I walk around this problem with the report management site on the server But deploying my report through it takes about 8 or 10 minutes…quite long !

Here are my questions :

- What are report elements that causes such time span ?

- How lighten the deployment ?

- How configure the deployement timeout in visual studio ?

Thanks

Which exact error message are you experiencing ?

Jens K. Suessmeyer.

http://www.sqlserver2005.de
|||

The report services on the server has been installed with the french version

so the error message is in french : "Le dlai d'attente de l'opration a expir"

in english it looks like : "The wait delay of the operation has expire"

thanks

Report Builder and CRM 3.0

Hello:

Does anybody know of an easy way to give lots of end-users of MS CRM 3.0 permission to create reports using the Report Builder? Heck, what's an efficient way to give lots of non-admin type users (regardless of CRM) the capability to use the Report Builder? Right now it seems that every Windows user has to be granted rights on an individual basis.

Based on various documentation, it appears that assigning the Report Builder role is meaningless unless users are defined under Site-Wide Settings as being either a System Administrator or System User. I know CRM creates a user called ReportingGroup, but assigning it a site-wide setting of System User with a Report Builder role doesn't flow to the individual members of ReportingGroup.

According to some other documentation I came across, ReportBuilder is a clickonce app that essentially needs to verify that the actual individual Windows user is permitted to access ReportBuilder. Given this fact, then it would seem to me that granting a group appropriate permissions to Report Builder is pointless.

In general, I'm failing to find solid information on SSRS2005 security and CRM 3.0, specifically as it relates to Report Builder permissions.

Does anyone have recommendations? Thanks.

Giving CRM users access to Report Builder requires 2 things:

First, they need to be in a system-wide role that includes the ability to run ad hoc reports. Generally, this is the System User role. I believe that ReportingGroup is a folder / scoped role, not a system role. Anyway, you can just assigned a Windows group that has the users you want to have access to this role.

Report Builder and CRM 3.0

Hello:

Does anybody know of an easy way to give lots of end-users of MS CRM 3.0 permission to create reports using the Report Builder? Heck, what's an efficient way to give lots of non-admin type users (regardless of CRM) the capability to use the Report Builder? Right now it seems that every Windows user has to be granted rights on an individual basis.

Based on various documentation, it appears that assigning the Report Builder role is meaningless unless users are defined under Site-Wide Settings as being either a System Administrator or System User. I know CRM creates a user called ReportingGroup, but assigning it a site-wide setting of System User with a Report Builder role doesn't flow to the individual members of ReportingGroup.

According to some other documentation I came across, ReportBuilder is a clickonce app that essentially needs to verify that the actual individual Windows user is permitted to access ReportBuilder. Given this fact, then it would seem to me that granting a group appropriate permissions to Report Builder is pointless.

In general, I'm failing to find solid information on SSRS2005 security and CRM 3.0, specifically as it relates to Report Builder permissions.

Does anyone have recommendations? Thanks.

Giving CRM users access to Report Builder requires 2 things:

First, they need to be in a system-wide role that includes the ability to run ad hoc reports. Generally, this is the System User role. I believe that ReportingGroup is a folder / scoped role, not a system role. Anyway, you can just assigned a Windows group that has the users you want to have access to this role.