Report builder and report models

Hi,

the database my app is using contains information from multiple user organisations, a sort of multi organisation database. I intend using the reprot builder to provide access to a user ine ach organisation. However the issue of who sees what info has popped up and i'm trying to think of a way to restict the user of report builder to only be able to see their own organisations information. This is a social services type application which is used by mutlitple service providers so organisations get twitchy about other organisations being able to see detailed client info. on the application the security stops this but at am a t a loss as to how to best restirct access to an organisation won client data.

any thoughts? is this somehting that can be configured through the reprt model and the report builder user account?

few ideas or advise would eb v helpful,

trhanks

Are you using SQL Server as the back end?

R

|||test. sorry to intrude.|||

Repot Models can have security rights assigned to different piece within the model. You can set up Perspectives and assigned users or roles to those perspectives. Or you can assign rights to individual folders. This can be done not through the report model (or the report server), but by opening the Report Model's Properties in SQL Server Management Studio.

Hope this helps.

|||

hi,

prev q answer - yes this is sql server 2005.

havn't come across perspectives but sounds v interesting. is that in SSRS or is it in SSAS?

i will check it out

many thanks

Report Action + multi parameters

Hi

Using Report Action, Can accept multi parameters from Excel Pivot Table?

Exist some way of doing this.

Please help me

thanks for your commentaries

carlos

Your probably better off using an url action instead of report action(which behind the covers is basically the same). Because if you want to specify more than one value you must specify that parameter over and over again at design time(i think), instead of concatenating a string. This because a url with a multivalue parameter looks like this:

http://localhost/ReportServer?%2fCatalog%2fMultiReport&rs:Command=Render&ParameterTest=1&ParameterTest=2

Look at these two links, i think you will get on how to do it in a URL action:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1047470&SiteID=1
http://msdn2.microsoft.com/en-us/library/ms153586.aspx

|||

Hi, thank for the help.

But, When I select several cells, since I do to pass them as parameters to the URL?

Is it possible?

|||

Actions are executed for specific cells based on the co-ordinates of that cell, so I would not expect the Excel user interface to allow you to launch an action when multile cells are selected.

|||

Ok, thank a lot for you help

Replication: Transactional: Multi Publications, One Subscriber.

Greetings All, I was hoping that a replication sage might be able to
answer a question for me.

I want to have one subscriber subscribing to N publishers. I
essentially have a company that has a main headquarters and three
satellite offices. I want each of the satellite offices to push their
data up to the master database. From what I have read it seems like
this should not be a problem. Some questions that come to mind are:

1.)Does the master need to be read only or can it be configured to be
updateable as well?
2.)Can the distribution agent on all the publishers be set to
continuously distribute or should it be staggered so as not to cause a
problem when another distribution agent is running?
3.)If the distribution is set to "delay distribution" will this cause
changes on the subscriber to be pushed out to the publishers?

In this database guid's are used as pk's so the issue of pk collisions
is not a problem.

I hope that this question is not too vague. My experience thus far
with replication has been simple one way transactional and simple
merge replication.

Regards, Louis Frolio"Louis Frolio" <froliol@.yahoo.com> wrote in message
news:94c28610.0409221536.67fda321@.posting.google.c om...
> Greetings All, I was hoping that a replication sage might be able to
> answer a question for me.
> I want to have one subscriber subscribing to N publishers. I
> essentially have a company that has a main headquarters and three
> satellite offices. I want each of the satellite offices to push their
> data up to the master database. From what I have read it seems like
> this should not be a problem. Some questions that come to mind are:
> 1.) Does the master need to be read only or can it be configured to be
> updateable as well?
> 2.) Can the distribution agent on all the publishers be set to
> continuously distribute or should it be staggered so as not to cause a
> problem when another distribution agent is running?
> 3.) If the distribution is set to "delay distribution" will this cause
> changes on the subscriber to be pushed out to the publishers?
>
> In this database guid's are used as pk's so the issue of pk collisions
> is not a problem.
> I hope that this question is not too vague. My experience thus far
> with replication has been simple one way transactional and simple
> merge replication.
> Regards, Louis Frolio

You might want to post this in microsoft.public.sqlserver.replication, where
there are probably more replication sages than in this newsgroup.

Simon|||froliol@.yahoo.com (Louis Frolio) wrote in message news:<94c28610.0409221536.67fda321@.posting.google.com>...
> Greetings All, I was hoping that a replication sage might be able to
> answer a question for me.
> I want to have one subscriber subscribing to N publishers. I
> essentially have a company that has a main headquarters and three
> satellite offices. I want each of the satellite offices to push their
> data up to the master database. From what I have read it seems like
> this should not be a problem. Some questions that come to mind are:
> 1.)Does the master need to be read only or can it be configured to be
> updateable as well?
> 2.)Can the distribution agent on all the publishers be set to
> continuously distribute or should it be staggered so as not to cause a
> problem when another distribution agent is running?
> 3.)If the distribution is set to "delay distribution" will this cause
> changes on the subscriber to be pushed out to the publishers?
>
> In this database guid's are used as pk's so the issue of pk collisions
> is not a problem.
> I hope that this question is not too vague. My experience thus far
> with replication has been simple one way transactional and simple
> merge replication.
> Regards, Louis Frolio

Q #1
> 1.)Does the master need to be read only or can it be configured to be
> updateable as well?

A. The subscriber database can be updated by users on that end, it
does not need to be read only.

Q #2
> continuously distribute or should it be staggered so as not to cause a
> problem when another distribution agent is running?

A. It can be done either way without issue.

Q #3
> 3.)If the distribution is set to "delay distribution" will this cause
> changes on the subscriber to be pushed out to the publishers?

A. No.

All, I have answered my own questions since I posted this missive.|||"Simon Hayes" <sql@.hayes.ch> wrote in message news:<4152b7ee_1@.news.bluewin.ch>...
> "Louis Frolio" <froliol@.yahoo.com> wrote in message
> news:94c28610.0409221536.67fda321@.posting.google.c om...
> > Greetings All, I was hoping that a replication sage might be able to
> > answer a question for me.
> > I want to have one subscriber subscribing to N publishers. I
> > essentially have a company that has a main headquarters and three
> > satellite offices. I want each of the satellite offices to push their
> > data up to the master database. From what I have read it seems like
> > this should not be a problem. Some questions that come to mind are:
> > 1.) Does the master need to be read only or can it be configured to be
> > updateable as well?
> > 2.) Can the distribution agent on all the publishers be set to
> > continuously distribute or should it be staggered so as not to cause a
> > problem when another distribution agent is running?
> > 3.) If the distribution is set to "delay distribution" will this cause
> > changes on the subscriber to be pushed out to the publishers?
> > In this database guid's are used as pk's so the issue of pk collisions
> > is not a problem.
> > I hope that this question is not too vague. My experience thus far
> > with replication has been simple one way transactional and simple
> > merge replication.
> > Regards, Louis Frolio
> You might want to post this in microsoft.public.sqlserver.replication, where
> there are probably more replication sages than in this newsgroup.
> Simon

Simon, thanks I did not realize that that group existed.

L