Showing posts with label view. Show all posts
Showing posts with label view. Show all posts

Friday, March 30, 2012

Report parameters

I have a report that reads from a view and in the report parameters I am
using "like <param value>%". The problem is that some of the values in the
datbase are nulls and I need those returned as well as the non null values.
Any help on this would be greatly appreciated.
--
JerryJust change your SQL
select * from sometable where somefield like 'blah%' or somefield is null
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Jerry" <Jerry@.jerry.com> wrote in message
news:AFF5F532-3E8A-4573-9B80-F329BD53B04A@.microsoft.com...
> I have a report that reads from a view and in the report parameters I am
> using "like <param value>%". The problem is that some of the values in
the
> datbase are nulls and I need those returned as well as the non null
values.
> Any help on this would be greatly appreciated.
> --
> Jerry|||I am using a view in Sql Server and adding a where clause in the view is no
problem and it works fine when you run the view. However I am using URL
Access in Sql Reporting Services and it is not working. IN the books online,
under "parameters, Reporting Services" is says the following:
If one of the values is null (that is, isnull), all other values specified
for that same parameter are ignored.
So if I enter &SomeField=%, it ignores the records with null values.
If use &SomeField=%&SomeField:isnull=true it returns nothing.
Is there a way to "OR" these together using URL Access?
Thanks for your help.
Jerry
"Bruce L-C [MVP]" wrote:
> Just change your SQL
> select * from sometable where somefield like 'blah%' or somefield is null
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Jerry" <Jerry@.jerry.com> wrote in message
> news:AFF5F532-3E8A-4573-9B80-F329BD53B04A@.microsoft.com...
> > I have a report that reads from a view and in the report parameters I am
> > using "like <param value>%". The problem is that some of the values in
> the
> > datbase are nulls and I need those returned as well as the non null
> values.
> > Any help on this would be greatly appreciated.
> > --
> > Jerry
>
>|||You have two different things here. One is URL and passing the parameter. If
your parameter allows nulls then you should be able to do this. Next is
getting your report to work with a null value. My suggestion is to first get
this to work from Report Manager before you try with URL. You have to have
two things for this to work. First, the parameter needs to allow nulls.
Second, the query itself that needs to be modified to work with Null. What I
showed you below was how to modify the query to work with null values.
I'm not sure why you are trying to send two values with the URL. You should
only be sending one value. I am a little confused on what you are wanting. I
thought what you wanted was to provide a value and see all records that have
that value for the field AND show all records where the value for the field
is null (For instance, lets say I had a field call Color, I want to see all
values where the color is blue or the color is not specified (is null)).
Then the query would be:
select * from mytable where color = @.colorparam or color is null
Note that the field name and the parameter name can be the same but they do
not have to be. There is a mapping between query parameter and report
parameter, make sure you understand this point.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Jerry" <Jerry@.jerry.com> wrote in message
news:B163FD9B-BFF9-46B7-A8F9-7A5863E43F88@.microsoft.com...
> I am using a view in Sql Server and adding a where clause in the view is
no
> problem and it works fine when you run the view. However I am using URL
> Access in Sql Reporting Services and it is not working. IN the books
online,
> under "parameters, Reporting Services" is says the following:
> If one of the values is null (that is, isnull), all other values specified
> for that same parameter are ignored.
> So if I enter &SomeField=%, it ignores the records with null values.
> If use &SomeField=%&SomeField:isnull=true it returns nothing.
> Is there a way to "OR" these together using URL Access?
> Thanks for your help.
> Jerry
>
> "Bruce L-C [MVP]" wrote:
> > Just change your SQL
> >
> > select * from sometable where somefield like 'blah%' or somefield is
null
> >
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "Jerry" <Jerry@.jerry.com> wrote in message
> > news:AFF5F532-3E8A-4573-9B80-F329BD53B04A@.microsoft.com...
> > > I have a report that reads from a view and in the report parameters I
am
> > > using "like <param value>%". The problem is that some of the values
in
> > the
> > > datbase are nulls and I need those returned as well as the non null
> > values.
> > > Any help on this would be greatly appreciated.
> > > --
> > > Jerry
> >
> >
> >sql

Wednesday, March 28, 2012

Report Parameter Dataset Running Twice?

Hi,
I have a DDL Report Parameter tied to a Dataset.
When I go to view the Report in RS the Dataset is run to populate the
Parameter, but it also seems to run the Dataset when I hit the View Report
button.
I don't have the Dataset tied to anything except the Report Parameter.
Is there a way to stop the 2nd run?
thank you
tOn May 22, 11:59 am, DigHazuse <DigHaz...@.discussions.microsoft.com>
wrote:
> Hi,
> I have a DDL Report Parameter tied to a Dataset.
> When I go to view the Report in RS the Dataset is run to populate the
> Parameter, but it also seems to run the Dataset when I hit the View Report
> button.
> I don't have the Dataset tied to anything except the Report Parameter.
> Is there a way to stop the 2nd run?
> thank you
> t
It should only be running to populate the report parameter. It sounds
like you possibly have the autorefresh set for the report (go to the:
Report drop-down tab -> Report Properties... -> General tab ->
autorefresh and see if it is selected). Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||Thank you for responding Enrique ... unfortunately that box is not checked.
Any other ideas?
thank you
t
"EMartinez" wrote:
> On May 22, 11:59 am, DigHazuse <DigHaz...@.discussions.microsoft.com>
> wrote:
> > Hi,
> > I have a DDL Report Parameter tied to a Dataset.
> >
> > When I go to view the Report in RS the Dataset is run to populate the
> > Parameter, but it also seems to run the Dataset when I hit the View Report
> > button.
> >
> > I don't have the Dataset tied to anything except the Report Parameter.
> >
> > Is there a way to stop the 2nd run?
> >
> > thank you
> > t
>
> It should only be running to populate the report parameter. It sounds
> like you possibly have the autorefresh set for the report (go to the:
> Report drop-down tab -> Report Properties... -> General tab ->
> autorefresh and see if it is selected). Hope this helps.
> Regards,
> Enrique Martinez
> Sr. Software Consultant
>sql

Report Parameter- 'All'

I am trying to make a report parameter that allows the user to select one of three values. Two of the values are what;s stored in the view's field right now: (as char 1) 'O' (open) or 'C' (closed). I need to add the choice 'All' that will show BOTH open and closed.

I made a dataset for the parameters as

select distinct valve_position

from view monitoring

where (not(valve_position is null))

Of course, that only yields choices of O or C, so I changed it to

select distinct valve_position , ''

from view monitoring

where (not(valve_position is null))

union

select 'All', -1

Then I changed the base query dataset to include

where valve_position = @.valve or valve_position = -1

When I run the report, O and C work, but All doesn't retrieve any records.

How do I something so simple? Of course, I see MSRS 2005 has a multi value check box...

Thanks for any help.

The comparisong valve_position = -1 should be @.valve = -1

For details about multivalue parameters please look at http://msdn2.microsoft.com/en-US/library/ms155917(SQL.90).aspx

|||Thank you!!! That worked!

Report Pagination

When you view the report in Report Manager it shows that it is Page 1 of 1
but when I export it to PDF it actually has 437 pages. Which is fine...no
probs there but would like to know the reason that it says Page 1 of 1 rather
than the 437.
Any help would be greatly appreacited on this, as its baffling me.Hi Nat,
Reports can appear different when rendered in different formats. For
example, your report is displayed using HTML in Report Designer preview
mode versus PDF when exported. So it is this formatting in HTML that
can cause the page number issue you describe (HTML has no concept of
page numbers - the whole report is '1' page...)
Maybe these suggestions can help?
1) When you preview a report in report designer, you can press the
<print preview> button (<print layout> in RS2005 if I recall...) on the
preview pane toolbar to display the report with pages (as it would
print out). At least you'll know how many pages the report truly has
this way.
2) If your report has hard page breaks set, you'll see the pages
displayed in preview window automatically.
HTH
Matt A
Reporting Services Newsletter at www.reportarchitex.com
Nat Johnson wrote:
> When you view the report in Report Manager it shows that it is Page 1 of 1
> but when I export it to PDF it actually has 437 pages. Which is fine...no
> probs there but would like to know the reason that it says Page 1 of 1 rather
> than the 437.
> Any help would be greatly appreacited on this, as its baffling me.

Friday, March 23, 2012

Report Models Data Source View

How does the report model know what data source view to use? I could not find it defined anywhere in the .smdl file.

My problem is this. I have a Report Model project with two data sources, two data source views and multiple report models. When I try and bind a data source to an entity in the report model I do not get to choose which data source view to use to choose what table/view I want to bind the entity too and only the tables in one of my DSV's shows up. When I first created it, it worked fine. It automatically selected the correct view and table and was successfully created but now when I open the project, that correlation is lost.

Any suggestions or help is appreciated, thanks.

I found out that if I close my solution and reopen it, the mappings are fixed. Does anyone know if this is a bug or if I could be doing something wrong? I can not find any documentation anywhere describing how data models are mapped to data source views. I really wish you can manually specify what datasource view you want to be using for each model. The autogenerate is nice to initially create the model but if you have already altered the elements or attributes in the model it can be a hassle. Any thoughts?

Report Model/Datasource View, Primary Data Source Problem

I have a datasource view DSV1. It points to a datasource DS1 that is considered the "primary".

I have created a Report Model that uses DSV1 (and thus uses DS1)

I created a new datasource, DS2 that I would like to use instead of DS1. (I can't just modify DS1 because if I modify it, it will overwrite it when we go to our Production environment and break that datasource)

So, I can go into DSV1 and change all the references from DS1 to DS2.

But that's where the problem lies.

When I try to build, I get the following error:

"The Table property of the Entity "E1" refers to the Table "dbo_View", which is not in the primary data source."

Somehow, the entity is tied to the "primary" datasource. When I change it back to DS1, everything works fine. Any thoughts? What can I do?

Here is what I've noticed:

If I look at the code for the Data Source DS1, the XML shows an <ID> tag and a <NAME> tag.

In SSRS, it is requiring that the ID be named "DS1", but the name can be whatever I want.

So if I change the name, it looks like I can deploy no problem without overwriting my old Datasource, but I just wish I could have these two pieces updated without a problem.

Any idea why this is?

Report Model Wizard

I created a data soure view that has tables from two data sources (both sql databases). when I try to generate a report model using this data source view, I get an "invalid object name" error for the first table it encounters that is not from the "primary" data source for the view. Is there something I need to do so the report model retrieves the connection strings for both data sources? Any help is greatly appreciated. Thank you in advance!Did you ever figure this out? I'm having the same problem.|||Cross-database report models are not supported in Model Designer. You can get around this by creating a view on top of the second table. We should probably give you a more informative error (or add support for it).|||Thank you for the reply.. I'm not sure I understand the workaround though. I am trying to do a proof of concept for my department and we have several data sources that I need to report from. Any help I can get is truly appreciated. I've been reading up on the different BI tools available with SQL server 2005 and it seems that maybe my best bet is to work on a data integration project... not sure which route to go. I do have a very good understanding of our database schema, its just a matter of how I can simplify it for end users to be able to write their own reports.|||I think I might have misread your original question. Are the two databases on the same server? If not, you will need to use the Linked Server feature of SQL to make this work. There are some performance implications with cross-server joins that may mean that you should pull the two sources into a single database using Integration Services,|||I actually have both cases... But I can't even get the view to work for two databases on the same server.. can you shed some light on that scenario?|||

Yudi,

If the databases are on one instance on one server, you can use the full name of the table to access the data in a named query. For instance,

SELECT col1, col2, col3 FROM table1

would be the first named query in the original database. In another named query you could use

SELECT col1, col2, col3 FROM DB1.dbo.table2

Provided you have the correct permissions on that database, you will be able to see the data in both databases. I use that technique and it works fairly well.

R

sql

Report Model Wizard

I created a data soure view that has tables from two data sources (both sql databases). when I try to generate a report model using this data source view, I get an "invalid object name" error for the first table it encounters that is not from the "primary" data source for the view. Is there something I need to do so the report model retrieves the connection strings for both data sources? Any help is greatly appreciated. Thank you in advance!Did you ever figure this out? I'm having the same problem.|||Cross-database report models are not supported in Model Designer. You can get around this by creating a view on top of the second table. We should probably give you a more informative error (or add support for it).|||Thank you for the reply.. I'm not sure I understand the workaround though. I am trying to do a proof of concept for my department and we have several data sources that I need to report from. Any help I can get is truly appreciated. I've been reading up on the different BI tools available with SQL server 2005 and it seems that maybe my best bet is to work on a data integration project... not sure which route to go. I do have a very good understanding of our database schema, its just a matter of how I can simplify it for end users to be able to write their own reports.|||I think I might have misread your original question. Are the two databases on the same server? If not, you will need to use the Linked Server feature of SQL to make this work. There are some performance implications with cross-server joins that may mean that you should pull the two sources into a single database using Integration Services,|||I actually have both cases... But I can't even get the view to work for two databases on the same server.. can you shed some light on that scenario?|||

Yudi,

If the databases are on one instance on one server, you can use the full name of the table to access the data in a named query. For instance,

SELECT col1, col2, col3 FROM table1

would be the first named query in the original database. In another named query you could use

SELECT col1, col2, col3 FROM DB1.dbo.table2

Provided you have the correct permissions on that database, you will be able to see the data in both databases. I use that technique and it works fairly well.

R

Report Model Project: Multiple Data Sources

I have setup a "Report Model Project" with multiple data sources, and
imported tables from each of these into my data source view. When I try to
use the wizard to create a report model I get an error on the "Completing the
Wizard" stage when I click "Run".
An error occurred while executing a command.
Message: Invalid object name 'dbo.<table name>'.
Command:
SELECT COUNT(*) FROM [dbo].[<table name>] t
The <table name> will always relate to the first table it attempts to
process from the secondary (non-primary) data source. I figured this out by
setting up the project from scratch with the opposite data source as primary.
It seems like it is looking in the primary data source for the table that it
should be trying to use the secondary data source to query.
Any help is appreciated. :)A report model can only reference one data source in this release. Data
source views are more flexible than supported by report models.
-Carolyn
"Greg T. Smith" wrote:
> I have setup a "Report Model Project" with multiple data sources, and
> imported tables from each of these into my data source view. When I try to
> use the wizard to create a report model I get an error on the "Completing the
> Wizard" stage when I click "Run".
> An error occurred while executing a command.
> Message: Invalid object name 'dbo.<table name>'.
> Command:
> SELECT COUNT(*) FROM [dbo].[<table name>] t
> The <table name> will always relate to the first table it attempts to
> process from the secondary (non-primary) data source. I figured this out by
> setting up the project from scratch with the opposite data source as primary.
> It seems like it is looking in the primary data source for the table that it
> should be trying to use the secondary data source to query.
> Any help is appreciated. :)

report model project problem - entity not showing up

I have a client table and a clientdoctors table.
In the data source view i see all the needed tables in the diagram organizer
pane. I also see the relationship between the clientdoctors table (which
holds clientid and doctorid), as well as client table and doctor table.
That all looks fine. The problem however is that when in my report model i
do not see those relationships at all between the client - client doctor -
doctor tables. There are a few situations just like this that i cannot
explain.
I am new to the report model project but i dont know why i dont see these
relationships inthe report model or while using report builder.
Any ideas please'Have you deployed properly? I mean you didn;t get any error. After deploying
you get to see in Report Builder. Just check.
Amarnath
"dave" wrote:
> I have a client table and a clientdoctors table.
> In the data source view i see all the needed tables in the diagram organizer
> pane. I also see the relationship between the clientdoctors table (which
> holds clientid and doctorid), as well as client table and doctor table.
> That all looks fine. The problem however is that when in my report model i
> do not see those relationships at all between the client - client doctor -
> doctor tables. There are a few situations just like this that i cannot
> explain.
> I am new to the report model project but i dont know why i dont see these
> relationships inthe report model or while using report builder.
> Any ideas please'|||Yes everything deployed properly. It seems like the problem was related to
keys on the tables. i.e. i had to place keys on the middle table.
"Amarnath" wrote:
> Have you deployed properly? I mean you didn;t get any error. After deploying
> you get to see in Report Builder. Just check.
> Amarnath
>
> "dave" wrote:
> > I have a client table and a clientdoctors table.
> >
> > In the data source view i see all the needed tables in the diagram organizer
> > pane. I also see the relationship between the clientdoctors table (which
> > holds clientid and doctorid), as well as client table and doctor table.
> >
> > That all looks fine. The problem however is that when in my report model i
> > do not see those relationships at all between the client - client doctor -
> > doctor tables. There are a few situations just like this that i cannot
> > explain.
> >
> > I am new to the report model project but i dont know why i dont see these
> > relationships inthe report model or while using report builder.
> >
> > Any ideas please'|||You need to have key relationship otherwise it wont select tables in the
report model itself. If you have completed the wizard of creating report
model. then it would have asked for keys when you select tables for
relations. So just check if all the keys are in place and deploy.
Amarnath
"dave" wrote:
> Yes everything deployed properly. It seems like the problem was related to
> keys on the tables. i.e. i had to place keys on the middle table.
>
> "Amarnath" wrote:
> > Have you deployed properly? I mean you didn;t get any error. After deploying
> > you get to see in Report Builder. Just check.
> >
> > Amarnath
> >
> >
> > "dave" wrote:
> >
> > > I have a client table and a clientdoctors table.
> > >
> > > In the data source view i see all the needed tables in the diagram organizer
> > > pane. I also see the relationship between the clientdoctors table (which
> > > holds clientid and doctorid), as well as client table and doctor table.
> > >
> > > That all looks fine. The problem however is that when in my report model i
> > > do not see those relationships at all between the client - client doctor -
> > > doctor tables. There are a few situations just like this that i cannot
> > > explain.
> > >
> > > I am new to the report model project but i dont know why i dont see these
> > > relationships inthe report model or while using report builder.
> > >
> > > Any ideas please'

Report Model Generator freezes VS2005

Hi,

I'm trying to generate data source model from appropriate relational

data source view with Report Model Wizard. But at the end of "Step 2:

processing rules on relations" Visual Studio devenv process aquires all

CPU resources and freezes VS.

What's wrong with my view? May be it contains some features that aren't supported by model generation process.

Regards,

Anatoly.

что произойдет если оставить машину в таком состоянии на какое-то время?
какая версия репорт сервера?
попробуй приаттачить DSV, кстати какой размер DSV файла?

Wednesday, March 21, 2012

Report Model from multiple data source

Creating a Data Source View from multiple Data Sources is no problem but what happens when you try to create the actuall Report Model. Using the primary Data Source doesn't give access to other databases, since each table name starts with dbo. Is there a option/flag to set to include database name?

Report Model DSVs only support one database, to pull in data from other databases you'll need to create a Named Query.

Analysis Services, on the other hand, don't have that problem, except for being limited to one database per DSV.

Note: I'm pretty sure I'm correct, but not 100%

sql

Report Model DSV Data Source change.

I have a Data Source View that is based on DS_Dev and all the table/named queries are based on this Data Set. I want to point the DSV to DS_Prod, but when I refresh the DSV it is still trying to look at DS_Dev. I know I must be overlooking something. How can I change all the tables in the DSV to point to the new data source?

I'm assuming I have to replace each table with the corresponding table in the new data source. I hope not.sql

Report Model as datasource in ordinary report

I think the report model concept is great and it works well for the report
builder. Can a report model or a data source view be used as a datasource for
ordinary reports? We have a large number of reports built upon complex
relational queries (join join join join...), but pretty much the same query
for all the reports. One way of solving this is by building an olap cube, but
the thing is that all this reports are automaticly genererated from a
"backroom" database for quality checking and then all the data is loaded into
a final datawarehouse. But maybe it's possibel to do this without a cube in
the backroom.OK, I've figured it out myself. A report model can definitly be the data
source for a report and it works very well, actually!
"Erik Hedlund" wrote:
> I think the report model concept is great and it works well for the report
> builder. Can a report model or a data source view be used as a datasource for
> ordinary reports? We have a large number of reports built upon complex
> relational queries (join join join join...), but pretty much the same query
> for all the reports. One way of solving this is by building an olap cube, but
> the thing is that all this reports are automaticly genererated from a
> "backroom" database for quality checking and then all the data is loaded into
> a final datawarehouse. But maybe it's possibel to do this without a cube in
> the backroom.|||I didn't think that it could be, can you clue me in?
"Erik Hedlund" <ErikHedlund@.discussions.microsoft.com> wrote in message
news:EB83FAA1-FCE7-4A89-8125-18FEB3C71489@.microsoft.com...
> OK, I've figured it out myself. A report model can definitly be the data
> source for a report and it works very well, actually!
> "Erik Hedlund" wrote:
>> I think the report model concept is great and it works well for the
>> report
>> builder. Can a report model or a data source view be used as a datasource
>> for
>> ordinary reports? We have a large number of reports built upon complex
>> relational queries (join join join join...), but pretty much the same
>> query
>> for all the reports. One way of solving this is by building an olap cube,
>> but
>> the thing is that all this reports are automaticly genererated from a
>> "backroom" database for quality checking and then all the data is loaded
>> into
>> a final datawarehouse. But maybe it's possibel to do this without a cube
>> in
>> the backroom.|||Create a data source, a datasource view and a report model and deply it to
the report server.
Create a report and select report model as the data source and specify a
connectionstring for it. Example:
server=http://localhost/reportserver;datasource=/Models/name of report model
And then your on!
"Steve MunLeeuw" wrote:
> I didn't think that it could be, can you clue me in?
> "Erik Hedlund" <ErikHedlund@.discussions.microsoft.com> wrote in message
> news:EB83FAA1-FCE7-4A89-8125-18FEB3C71489@.microsoft.com...
> > OK, I've figured it out myself. A report model can definitly be the data
> > source for a report and it works very well, actually!
> >
> > "Erik Hedlund" wrote:
> >
> >> I think the report model concept is great and it works well for the
> >> report
> >> builder. Can a report model or a data source view be used as a datasource
> >> for
> >> ordinary reports? We have a large number of reports built upon complex
> >> relational queries (join join join join...), but pretty much the same
> >> query
> >> for all the reports. One way of solving this is by building an olap cube,
> >> but
> >> the thing is that all this reports are automaticly genererated from a
> >> "backroom" database for quality checking and then all the data is loaded
> >> into
> >> a final datawarehouse. But maybe it's possibel to do this without a cube
> >> in
> >> the backroom.
>
>sql

Report Model (Data Source View) issue

We've built an oltp that uses nothing but synonyms that reach out to various DB's in the organization thru linked servers.

The issue that we are having is Data Source Views can only see tables and views. Is it possible to use synonyms? If not what would be a work around.

Please advise. Thanks

Steve

I use linked servers in reports (actually, let's be honest, I use linked servers pretty much ALL THE TIME ).

I haven't done this with Report Models that I can recall. But I am pretty sure that what works for me would work in Report Models.

There are a couple of things you can do as a workaround:

1. If you don't have other uses for the synonyms, eliminate the synonym from the equation entirely and just use fully-qualified syntax in views, for example (and of course you don't have to use * here!) :

CREATE VIEW vw_Synonym1 AS SELECT * FROM MyLinkedServer.MyDB1.dbo.MyTable

2. I'm not entirely sure that the models can't use synonyms! It's likely that they can but the wizards and interfaces that you're given in the designer cannot. If I'm right, you just need to write something to handle the model XML directly to get what you want.

I am not going to mess with this to test it out, because I don't spend a lot of time with report models, but start with the XSD (which must be published) and figure out whether the appropriate values should go. Then alter a copy of an existing model that you have to test -- I bet it works. If you want to go this route and get stuck on the details, holler. <g>

3. If you do have other uses for the synonyms, as apparently you do, and if you don't want to mess with the model xml, you can create a view that represents each synonym in a one-to-one relationship. IOW, pretty much CREATE VIEW vw_Synonym1 AS SELECT * FROM Synonym1. Again I know that * is evil but you get the picture <s>. Extend this properly as follows:

You can avoid the evil "*" by interrogating the properties of the thing underneath. You can automate all current synonyms to create new views (and leverage the interrogation code you just wrote) by examining SELECT * FROM sys.synonyms and writing code that works through the list. You can automate all future synonyms you create to do the same thing automatically by using a database trigger. Here is a sketch:

Tuesday, March 20, 2012

Report Model

Can you have more than one data source view in one report model? I have data from multiple sql databases that I want to combine into a single report model for the users.

Currently only one data source per model is supported.

It may be possible however to use Data Source View editor to manually add named queries which reference other databases.

|||

Lev is right. If you want to create a model over a set of databases you need to do some manual work with your DSV.

In model designer start with generating DSV for primary database (the one containing more data). Then manually add named queries to the DSV each selecting data from another database (select * from myotherdb.dbo.tableN). For each named query manually add info about which columns should be treated as PK and which are FKs. This is important for semantic model generation that would omit tables without PKs and will note create roles between entities without FKs.
After you finish with your DSV - generate model in model designer.

Report Manager/Viewer Help!!

The parameters box in the report view displays in tabular format if you have
at least two parameters. Can I change this in anyway so it displays in
columan format.
Current display
1. parameter box 2. parameter box
3. parameter box 4. parameter box
Can I change it to display like:
1. parameter box
2. parameter box
3. parameter box
4. parameter boxThe answer is no you can't! Sorry.
You could generate you're parameter asp page and run the report with
url access from a button on the asp page. That way you can be much more
fancy with the parameters.
Chris
OriginalStealth wrote:
> The parameters box in the report view displays in tabular format if
> you have at least two parameters. Can I change this in anyway so it
> displays in columan format.
> Current display
> 1. parameter box 2. parameter box
> 3. parameter box 4. parameter box
> Can I change it to display like:
> 1. parameter box
> 2. parameter box
> 3. parameter box
> 4. parameter box

Monday, March 12, 2012

Report Manager HELP ASAP! I get this error when running a repor

Your browser does not support scripts or has been configured not to allow
scripts. Click here to view this report without scripts.
What does this mean?Nevermind. Web browser issue. Thanks.
"OriginalStealth" wrote:
> Your browser does not support scripts or has been configured not to allow
> scripts. Click here to view this report without scripts.
> What does this mean?

Report Manager error

I am able to view reports by navigating directly to /ReportServer however the
report manager (/Reports/Home.aspx) gives the following:
ERROR.
Object reference not set to an instance of an object.
No other info is provided. I'm using SSL and RS SP2 is installed, SQL has
SP4. I've looked in the Reporting Services Log files but I don't see
anything there to help trap this error.
What "object" might this be? Any ideas about how to debug this?
Thanks,
Jeff Munson
University of WashingtonMaybe this will help someone?
When I hit https://localhost/SQLReports/Pages/Folder.aspx from the web
server itself and view source here is what's displayed in the HEAD tag:
(Note that the virtual directories are actually SQLReports and
SQLReportServer - this wasn't how I labelled them in my first post)
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" >
<HTML>
<HEAD> <script language="JScript" type="text/Javascript"
src="/SQLReports/js/ReportingServices.js"></script>
<TITLE>Report Manager</TITLE>
<link href="http://links.10026.com/?link=/SQLReports/styles/ReportingServices.css"type="text/css"
rel="stylesheet">
<META Name='Generator' CONTENT='Microsoft SQL Server Report Manager
8.00.1038.00'>
<META Name='Report Server' CONTENT='http://MYDOMAIN/SQLReportServer'>
<META Name='StackTrace' CONTENT='System.NullReferenceException: Object
reference not set to an instance of an object.
at
Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetReportServerAuthentication()
at Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetWebRequest(Uri
uri)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)
at
Microsoft.SqlServer.ReportingServices.ReportingService.ListSecureMethods()
at Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
at Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
at
Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
methodname)
at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
at
Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
level)
at Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
sender, EventArgs args)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Web.UI.Control.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain()'>
"JMunson" wrote:
> I am able to view reports by navigating directly to /ReportServer however the
> report manager (/Reports/Home.aspx) gives the following:
> ERROR.
> Object reference not set to an instance of an object.
> No other info is provided. I'm using SSL and RS SP2 is installed, SQL has
> SP4. I've looked in the Reporting Services Log files but I don't see
> anything there to help trap this error.
> What "object" might this be? Any ideas about how to debug this?
> Thanks,
> Jeff Munson
> University of Washington

Friday, March 9, 2012

Report Manager blank

I've got a report that works fine in development (and in production too until
recently) but no longer loads in production. When I click "View Report", it
just reloads the page as it is, without generating a report.
I've tried deleting and reloading it clean into production, but with the
same results.
I'd think it was something wrong with my stored procedure, except that it
has been working fine in development (and working off the same database as in
production).
Is there anything like this that anyone else has run into?I have seen this as a credential problem (reason that it is blank). Check
that the credential for the report has the proper rights for the SP.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Mike R" <MikeR@.discussions.microsoft.com> wrote in message
news:D737759F-EF2D-48C3-81B8-5205DF64C4DA@.microsoft.com...
> I've got a report that works fine in development (and in production too
> until
> recently) but no longer loads in production. When I click "View Report",
> it
> just reloads the page as it is, without generating a report.
> I've tried deleting and reloading it clean into production, but with the
> same results.
> I'd think it was something wrong with my stored procedure, except that it
> has been working fine in development (and working off the same database as
> in
> production).
> Is there anything like this that anyone else has run into?