Report Model, which approach?

Hi All,

I'm a newbie to Report Model and not able to find some conceptual information, Can you guys answer following:

I’ve

Employee [Name]
->Employee_Days [Day] (1-*)
->Employee_Day_Activities [Activity_Type, HoursSpent] (1-*)

schema and a generated model out of it. Now I’ve few report requirements which will be developed based on Report Model. These Reports needs aggregate of All similar activities and the hrs spent and it'll be shown with every employee. Like Employee Xyz has spent 14 hrs total on Sick Activity, which will be shown as

Employee Sick Hrs Maternity Hrs WorkHrs
Xyz 14 0 20

Now i need to know the approach to develop it like i'v to ways in my mind

- create 3 custom fields(Sickhrs,Maternityhrs,Workhrs) in the Employee Entity(model), so that managers can create reports like above by simple drag and drop

- leave model as it is.. just create more descriptive fields in all the three table and let managers do the activity grouping etc to develop report like above..

Which approach should i follow? Moreover can you point me to some conceptual info like how report model works..etc..

regards
farazIt seems microsoft people are not interested in Report Model :)|||

I'd suggest creating filtered aggregates for these categories in the Employee entity in your report model (your first approach). Please see this post for more info:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=941599&SiteID=1

Report Model, which approach?

Hi All,

I'm a newbie to Report Model and not able to find some conceptual information, Can you guys answer following:

I’ve

Employee [Name]
->Employee_Days [Day] (1-*)
->Employee_Day_Activities [Activity_Type, HoursSpent] (1-*)

schema and a generated model out of it. Now I’ve few report requirements which will be developed based on Report Model. These Reports needs aggregate of All similar activities and the hrs spent and it'll be shown with every employee. Like Employee Xyz has spent 14 hrs total on Sick Activity, which will be shown as

Employee Sick Hrs Maternity Hrs WorkHrs
Xyz 14 0 20

Now i need to know the approach to develop it like i'v to ways in my mind

- create 3 custom fields(Sickhrs,Maternityhrs,Workhrs) in the Employee Entity(model), so that managers can create reports like above by simple drag and drop

- leave model as it is.. just create more descriptive fields in all the three table and let managers do the activity grouping etc to develop report like above..

Which approach should i follow? Moreover can you point me to some conceptual info like how report model works..etc..

regards
farazIt seems microsoft people are not interested in Report Model :)|||

I'd suggest creating filtered aggregates for these categories in the Employee entity in your report model (your first approach). Please see this post for more info:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=941599&SiteID=1

Report Model & Data Source Views

Hi,
(Newbie at SSRS, 10 years experience with SQL-Server & Web/App programming)
I recently (about 1 week ago) introduced myself to the world of SSRS - but
it wasn't as straightforward as I first thought it should be. Try yourself by
searching for documentation about installing reporting services on another
machine than the same as the sql server (ie: at the webserver). As usual: -
you have to read several different webpages, scan through endless
documentation created by linquist-speciallists (discussing everything but the
subject) - a.k.a. 'quickstarts'. Whehehe..
Anyhow, I've now successfully setup Reporting Services and it really excells
at everything it does :)
However, I find it a little bit strange generating the Report Model from the
Data Source View. Shouldn't it be the otherway around? - First creating the
Model (a simple schema of the database - right?), and THEN creating the view
- 'building' upon that model. Could someone please expand on this subject?
Why?
Then there seems to be an issue when I try to include a SQL Server "SQL
View" a.k.a. "Indexed Views" into the Report Model, so this results in that
neither of my SQL View are accessible from the online Report Builder tool.
Shouldn't it be possible to include views in the Report Model?
Best Regards,
FredrikThis is how I solved it:
- In the Data Source View, be sure to set Logical Primary Keys for the SQL
Views that you want to use. Just select the unique columns (if more than
one), rightclick and create the key.
- In the Report Model, add the entities (SQL views) manually - name & bind
them to the SQL views. Rightclick on an empty & newly created entity and
select autogenerate, proceed through the wizard. Add the identifying column
manually on the the entity (using the properties tool-window).
- Build and combine the .DSV & .SMDL file into one (fairly easy to google),
then upload the resulting "model.smdl" to the Report Manager.
- Enjoy SQL views in Report Builder!
"Fredrik Johansson" wrote:
> Hi,
> (Newbie at SSRS, 10 years experience with SQL-Server & Web/App programming)
> I recently (about 1 week ago) introduced myself to the world of SSRS - but
> it wasn't as straightforward as I first thought it should be. Try yourself by
> searching for documentation about installing reporting services on another
> machine than the same as the sql server (ie: at the webserver). As usual: -
> you have to read several different webpages, scan through endless
> documentation created by linquist-speciallists (discussing everything but the
> subject) - a.k.a. 'quickstarts'. Whehehe..
> Anyhow, I've now successfully setup Reporting Services and it really excells
> at everything it does :)
> However, I find it a little bit strange generating the Report Model from the
> Data Source View. Shouldn't it be the otherway around? - First creating the
> Model (a simple schema of the database - right?), and THEN creating the view
> - 'building' upon that model. Could someone please expand on this subject?
> Why?
> Then there seems to be an issue when I try to include a SQL Server "SQL
> View" a.k.a. "Indexed Views" into the Report Model, so this results in that
> neither of my SQL View are accessible from the online Report Builder tool.
> Shouldn't it be possible to include views in the Report Model?
>
> Best Regards,
> Fredrik

Report Manager Home page is incomplete

First off, forgive the ignorance that I'm sure to display in this post. I'm a total newbie with SRSS and have been using it to follow along with the tutorials offered via the SQL Express website. I'm using it strictly for learning on my local machine for the time being.

All had been working well with Reporting Services until I upgraded Vista Ultimate 64-bit (which was running in free 30-day trial unactivated Evaluation mode) sideways to Vista Ultimate Upgrade Edition 64-bit Edition. (Sounds confusing, I know.) I also subsequently installed a SQL Server 2k5 critical update which was recommended by Windows Update.

Now when I attempt to access Report Manager via localhost the "Home page" is incomplete, showing only the SSRS "Home" page header. There are no properites, data sources, config options, etc. outside of links for "Home|Help". I am running IE as an Admin and all the Reporting Services Configuration settings are green.

Also, when I attempt to deploy from VS 2005 I now receive the error: "Permissions granted to user 'NT Authority\Network Service' are insufficient ..."

Some of the settings inside the Report Sever Config are as follows:

Windows Service Identity:

Service Acct: NT Authority\Network Service; Built-in Account: Network Service

Web Service Identity:

Asp.net Service Account; NT Authority\Network Service; Report Server and Manager are both using Classic.Net AppPool

I've attempted for hours to weed through Google and this forum but have repeatedly wound up back where I started and more confused than when I started. I would deeply appreciate any help in resolving this matter.

I just spent two weeks figuring it out. I have a thread on here somewhere called "Vista & SSRS". It's not like one would expect Microsoft to be able to install their own software properly onto their own OS.....

I had to add both Report Mgr & Reporting Services to the Classic .net pool (whatever that is...it's in SSRS config)

I had to turn off that annoying thingie MS added to Vista to make it impossible to do anything - the thing Apple makes fun of in their commercials.

I had to add my user account and adin acct to the IIS user group

I had to install every IIS option, basic install leaves some out.

I think that was all.....good luck

|||

Thanks for the tips, JohnSLG. I had already done all but adding my user and admin accounts to the IIS User group. Unfortunately, my problem is still not resolved.

Just going to have to keep trolling here and Google in the hopes to find an answer. What twists my noodle more than anything is that I went through a helluva long and frustrating effort to get SRSS working before I had to upgrade Vista.

|||

I'm now just so flippin' lost ... Was finally able to access Report Manager after I created a new application pools from the RS Config Manager but then was unable to deploy reports from VS2005 and receive error message that "Report Server Web Service is unable to access secure ... verify WebServiceAccount is specified correctly in report server config file". Then I implusively hit "apply default settings" checkbox and then Apply and now I'm back where I started.

The simple fact is that I can no longer keep track of all the various settings I've changed from IIS Manager to RSConfig Manager to rsreportsever.config, user security settings, new app pools, etc. I'd like to start from scratch. removing every app pool every report server etc but that does not work because that stuff shows up again in RS Config Manager even after uninstall/reinstall. I simply don't know how to remove every last scrap and start the whole damn thing from scratch with the defaults. In short, I'm just in over my head and confused.

Think I'm going back to Access databases where I at least know what in the heck I'm doing. Right now, I'm just simply compounding problems by willy-nilly following every seemingly related tip I find on this board. It's my ignorance, but MS really could have done a much better job in making Reporting Services much less complicated with a simple to follow step by step install and configure instructions for those with my specific setup. I've got Vista Ultimate 64-bit edition with SQL Server 2005 Express SP2 and VS Studio 2005 and all I want to do is run the dam thing on my local machine so I can learn how it works. I want to be able to access the Report Manager via localhost\reports and be able to deploy reports from VS2005. Having to mess around with all these relatively arcane configuration and network settings is a royal pain in the rump.

/frustrated whining and moaning

|||

I hear you....I'm not sure exactly what I did to finally get it to work for me, but I think it was adding the admin user account to the IIS group. I've since dumped Vista 64 - it's ***, no drivers, buggy and went back to Vista - probably should have gone back to XP....I had to go through the same gyrations to get report manager to work again.....fortunately it worked for me after following my 4 step program.

I don't know why Microsoft cannot install their own software on their own operating systems.

Report Manager Home page is incomplete

First off, forgive the ignorance that I'm sure to display in this post. I'm a total newbie with SRSS and have been using it to follow along with the tutorials offered via the SQL Express website. I'm using it strictly for learning on my local machine for the time being.

All had been working well with Reporting Services until I upgraded Vista Ultimate 64-bit (which was running in free 30-day trial unactivated Evaluation mode) sideways to Vista Ultimate Upgrade Edition 64-bit Edition. (Sounds confusing, I know.) I also subsequently installed a SQL Server 2k5 critical update which was recommended by Windows Update.

Now when I attempt to access Report Manager via localhost the "Home page" is incomplete, showing only the SSRS "Home" page header. There are no properites, data sources, config options, etc. outside of links for "Home|Help". I am running IE as an Admin and all the Reporting Services Configuration settings are green.

Also, when I attempt to deploy from VS 2005 I now receive the error: "Permissions granted to user 'NT Authority\Network Service' are insufficient ..."

Some of the settings inside the Report Sever Config are as follows:

Windows Service Identity:

Service Acct: NT Authority\Network Service; Built-in Account: Network Service

Web Service Identity:

Asp.net Service Account; NT Authority\Network Service; Report Server and Manager are both using Classic.Net AppPool

I've attempted for hours to weed through Google and this forum but have repeatedly wound up back where I started and more confused than when I started. I would deeply appreciate any help in resolving this matter.

I just spent two weeks figuring it out. I have a thread on here somewhere called "Vista & SSRS". It's not like one would expect Microsoft to be able to install their own software properly onto their own OS.....

I had to add both Report Mgr & Reporting Services to the Classic .net pool (whatever that is...it's in SSRS config)

I had to turn off that annoying thingie MS added to Vista to make it impossible to do anything - the thing Apple makes fun of in their commercials.

I had to add my user account and adin acct to the IIS user group

I had to install every IIS option, basic install leaves some out.

I think that was all.....good luck

|||

Thanks for the tips, JohnSLG. I had already done all but adding my user and admin accounts to the IIS User group. Unfortunately, my problem is still not resolved.

Just going to have to keep trolling here and Google in the hopes to find an answer. What twists my noodle more than anything is that I went through a helluva long and frustrating effort to get SRSS working before I had to upgrade Vista.

|||

I'm now just so flippin' lost ... Was finally able to access Report Manager after I created a new application pools from the RS Config Manager but then was unable to deploy reports from VS2005 and receive error message that "Report Server Web Service is unable to access secure ... verify WebServiceAccount is specified correctly in report server config file". Then I implusively hit "apply default settings" checkbox and then Apply and now I'm back where I started.

The simple fact is that I can no longer keep track of all the various settings I've changed from IIS Manager to RSConfig Manager to rsreportsever.config, user security settings, new app pools, etc. I'd like to start from scratch. removing every app pool every report server etc but that does not work because that stuff shows up again in RS Config Manager even after uninstall/reinstall. I simply don't know how to remove every last scrap and start the whole damn thing from scratch with the defaults. In short, I'm just in over my head and confused.

Think I'm going back to Access databases where I at least know what in the heck I'm doing. Right now, I'm just simply compounding problems by willy-nilly following every seemingly related tip I find on this board. It's my ignorance, but MS really could have done a much better job in making Reporting Services much less complicated with a simple to follow step by step install and configure instructions for those with my specific setup. I've got Vista Ultimate 64-bit edition with SQL Server 2005 Express SP2 and VS Studio 2005 and all I want to do is run the dam thing on my local machine so I can learn how it works. I want to be able to access the Report Manager via localhost\reports and be able to deploy reports from VS2005. Having to mess around with all these relatively arcane configuration and network settings is a royal pain in the rump.

/frustrated whining and moaning

|||

I hear you....I'm not sure exactly what I did to finally get it to work for me, but I think it was adding the admin user account to the IIS group. I've since dumped Vista 64 - it's ***, no drivers, buggy and went back to Vista - probably should have gone back to XP....I had to go through the same gyrations to get report manager to work again.....fortunately it worked for me after following my 4 step program.

I don't know why Microsoft cannot install their own software on their own operating systems.