It seems like you don't need to specify SQL's ORDER BY to match Page and Group breaks in RS. I.e., RS does
this handling by itself, with the added work and memory requirements to do it.
My question is whether RS will understand that I do have ORDER BY in the query that matches my Page and Group
breaks, and just read off the input stream without doing the sorting etc by itself. If it doesn't, I wouldn't
want to burden the DBMS with the sorting as it would be redundant...
I tried a report, which was indeed alphabetically grouped by RS without a SQL ORDER BY. Even when adding ORDER
BY NEWID() (which returns rows in a different "random ordering for each execution), the report was still
grouped alphabetically.
(I am not referring to the ordering of the details info, I understand that ORDER BY is needed for that.)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/You don't ever need to use ORDER BY in your query, even to order the
details. RS supports many different types of data sources (and you can
easily add your own by writing a custom data processing extension), not just
SQL, and some these data sources may not have the ability to sort. Also, RS
does not examine your query and cannot detect that you have an ORDER BY.
--
Rajeev Karunakaran [MSFT]
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OPN1N6ifEHA.1644@.tk2msftngp13.phx.gbl...
> It seems like you don't need to specify SQL's ORDER BY to match Page and
> Group breaks in RS. I.e., RS does
> this handling by itself, with the added work and memory requirements to do
> it.
> My question is whether RS will understand that I do have ORDER BY in the
> query that matches my Page and Group
> breaks, and just read off the input stream without doing the sorting etc
> by itself. If it doesn't, I wouldn't
> want to burden the DBMS with the sorting as it would be redundant...
> I tried a report, which was indeed alphabetically grouped by RS without a
> SQL ORDER BY. Even when adding ORDER
> BY NEWID() (which returns rows in a different "random ordering for each
> execution), the report was still
> grouped alphabetically.
> (I am not referring to the ordering of the details info, I understand that
> ORDER BY is needed for that.)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
>
Showing posts with label itself. Show all posts
Showing posts with label itself. Show all posts
Thursday, March 22, 2012
Sunday, February 26, 2012
does a view refresh itself when i reference it? (was "Question On Views")
guys, ive never worked with Views before so forgive me.
i know how to create one, and that it creates a virtual table in memory, but i've got one small question.
if i create a view:
CREATE view dbo.myView
as
select Distinct FirstName,LastName from SomeTable
When ever i reference that view, such as
Select FirstName,LastName
from myView
where LastName like 'Jo%'
does that View Refresh itself??
in other words does it run each time i Reference it? or is it static from when i created it.
Wouldnt it be easier just to use a #TempTable or some other Table thats used to hold a few values?
thanks for any help
rikDont worry man ,view is not static .It always fetch records from base table.It is uptodate unless u r using index on views|||You know - I've always thought that the definition of a view as something like a virtual table as very confusing. When I studied relational databases the chapter on views made an assumption that the reader would be very confused at what differentiated a view from a table and spent line after line emphasising the difference. "No " thought I "I can very well differentiate a view from a table - what the flip is the distinction between a view and a query?"
The way I tend to think of views (indexed views excluded) is that a view is best thought of as a persistent, optimised, stored query that can usually be treated in the same way that you would treat a table as far as viewing data is concerned. It is, however, just that - a view of the data. As such, it does not store any data itself. Every time you call it it views the data afresh.
HTH|||thank you guys so much. that's exactly the answer i was looking for.
thanks again
rik
i know how to create one, and that it creates a virtual table in memory, but i've got one small question.
if i create a view:
CREATE view dbo.myView
as
select Distinct FirstName,LastName from SomeTable
When ever i reference that view, such as
Select FirstName,LastName
from myView
where LastName like 'Jo%'
does that View Refresh itself??
in other words does it run each time i Reference it? or is it static from when i created it.
Wouldnt it be easier just to use a #TempTable or some other Table thats used to hold a few values?
thanks for any help
rikDont worry man ,view is not static .It always fetch records from base table.It is uptodate unless u r using index on views|||You know - I've always thought that the definition of a view as something like a virtual table as very confusing. When I studied relational databases the chapter on views made an assumption that the reader would be very confused at what differentiated a view from a table and spent line after line emphasising the difference. "No " thought I "I can very well differentiate a view from a table - what the flip is the distinction between a view and a query?"
The way I tend to think of views (indexed views excluded) is that a view is best thought of as a persistent, optimised, stored query that can usually be treated in the same way that you would treat a table as far as viewing data is concerned. It is, however, just that - a view of the data. As such, it does not store any data itself. Every time you call it it views the data afresh.
HTH|||thank you guys so much. that's exactly the answer i was looking for.
thanks again
rik
Friday, February 17, 2012
Document Map
Problems with Document Map creating a side scroll to get to Up/Down Scroll for the Map itself. There are two scroll bars once you side scroll over in the map window. Anyone seen this or know how to fix? Or Anyone know how to change any of the properties on the Document Map or map window?
Thanks!!!!!
There has to be a way to change the properties on the Document Map Window - Come on MSFT guys......|||So no one knows how to change any configuration on the Document map or why it creates a side scroll and a seperate vertical scroll from the main report?|||seriously?!?!?!|||truely!?!?!?!|||Can you try posting a screen shot of what you are describing?|||How do I post a screen shot?|||You can email it to me @. john[dot]gallardo [at] microsoft[dot]com.
|||Hi, I wondered if you ever got a resolution on this. I have a similar problem that once I deploy the report the scroll bar for the document map does not let you scroll to the document map. It only allows you to scroll through what initially fits when the report is first displayed. Before it was deployed, when the report was previewed, the scrolling worked fine... it was only after it was deployed that I could not scroll.
Your issue was a little different, but since it did have to do with the scroll bar of the document map, I'm hoping you got a little further to see how/where/and if it can be configured.
Thank you very much, Julie
|||We are working on it....hopefully we get it resolved soon and I will let you know|||It is a known issue for which we have a repro for. Unfortunately there is not a very good workaround other than simply dragging the frame containing the document map larger.Document Map
Problems with Document Map creating a side scroll to get to Up/Down Scroll for the Map itself. There are two scroll bars once you side scroll over in the map window. Anyone seen this or know how to fix? Or Anyone know how to change any of the properties on the Document Map or map window?
Thanks!!!!!
There has to be a way to change the properties on the Document Map Window - Come on MSFT guys......|||So no one knows how to change any configuration on the Document map or why it creates a side scroll and a seperate vertical scroll from the main report?|||seriously?!?!?!|||truely!?!?!?!|||Can you try posting a screen shot of what you are describing?|||How do I post a screen shot?|||You can email it to me @. john[dot]gallardo [at] microsoft[dot]com.
|||Hi, I wondered if you ever got a resolution on this. I have a similar problem that once I deploy the report the scroll bar for the document map does not let you scroll to the document map. It only allows you to scroll through what initially fits when the report is first displayed. Before it was deployed, when the report was previewed, the scrolling worked fine... it was only after it was deployed that I could not scroll.
Your issue was a little different, but since it did have to do with the scroll bar of the document map, I'm hoping you got a little further to see how/where/and if it can be configured.
Thank you very much, Julie
|||We are working on it....hopefully we get it resolved soon and I will let you know|||It is a known issue for which we have a repro for. Unfortunately there is not a very good workaround other than simply dragging the frame containing the document map larger.
Subscribe to:
Posts (Atom)