Difference Between Query Parameters and Report Parameters

Hi Guys,
Can somebody explain me cleraly the difference between Query and Report
Parameters.
Report Parameters r automatically created when u put some variable in a
query.
2)
One more thing is there a way we can hide query string in the IE as I dont
want the users to see the report URL.
3)
My Stored Proc expects 2 parameters but I dont want to pass them in the URL
string is there any other way I can pass parameters to the report from the
front end other than URL strings
Many Many Thanks
Chandra
--
Message posted via http://www.sqlmonster.comwell report parameters r used to get input from the user for the report
and report parameters got attached with query parameters to pass on
input from the user to query in order to build query at run time when u
define query parameter in ur query report automatically generates a
report parameter and attach that report parameter to the specific query
parameter to see further details click EDIT DATASET option n click
parameters tab u ll c how report parameters r getting associated to
query parameters
as far as ur question of hiding parameters is concerned u got to use
reporting services class (SOAP API) n make ur own application to access
the reports instead of accessing reports through URL or u got to set
any property of Ineternet explorers in the registery to hide the
address bar and status bar as well
hope this answers
take care
regards|||Go here:
http://msdn.microsoft.com/library/en-us/RSCREATE/htm/rcr_creating_interactive_v1_50fn.asp?frame=true
It will tell you all you need to know about parameters.
"Chandra Kotha via SQLMonster.com" wrote:
> Hi Guys,
> Can somebody explain me cleraly the difference between Query and Report
> Parameters.
> Report Parameters r automatically created when u put some variable in a
> query.
> 2)
> One more thing is there a way we can hide query string in the IE as I dont
> want the users to see the report URL.
> 3)
> My Stored Proc expects 2 parameters but I dont want to pass them in the URL
> string is there any other way I can pass parameters to the report from the
> front end other than URL strings
> Many Many Thanks
> Chandra
> --
> Message posted via http://www.sqlmonster.com
>|||Others have answered most of your questions. Just a little bit more about
query parameters versus report parameters. RS does automatically create a
report parameter when you put in a query parameter. However, you do not have
to use it. You can set the query parameter to a different report parameter,
you can set it to an expression (which means that if you want you can first
have some custom code massage the report parameter first). A very common
scenario where there is not a one to one relationship between report and
query parameters is when you have several datasets in a report. Let's say I
have several datasets that all use a fromdate and todate. I sure don't want
the user to have to put in the same date multiple times. So, I delete the
extra report parameters and have all the datasets query parameters point to
the same set of report parameters.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Chandra Kotha via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:698d0fc48f2b42f69c5c9fdc8632204a@.SQLMonster.com...
> Hi Guys,
> Can somebody explain me cleraly the difference between Query and Report
> Parameters.
> Report Parameters r automatically created when u put some variable in a
> query.
> 2)
> One more thing is there a way we can hide query string in the IE as I dont
> want the users to see the report URL.
> 3)
> My Stored Proc expects 2 parameters but I dont want to pass them in the
URL
> string is there any other way I can pass parameters to the report from the
> front end other than URL strings
> Many Many Thanks
> Chandra
> --
> Message posted via http://www.sqlmonster.com|||Thanks Guys for ur responses
--
Message posted via http://www.sqlmonster.com

Difference between Matrix and Table

Hello.
I'm fairly new to Reporting Services, so my question might seem really
simple to you guys. But what is the difference between a matrix and a table?
When should I use what? Are there any articles on the web that explain this?
The best I've found is in this article:
http://www.ftponline.com/vsm/2004_09/magazine/columns/databasedesign/default_pf.aspx
[Quote]
The report type defines the structure, or data region, of the data returned
by your query. The Report Wizard lets you present this information as either
a table or a matrix, though you have more options outside the wizard. The
main difference between these two types of data regions is the number of
columns. A table has a fixed number of columns; a matrix has a variable
number determined by the query results.
[/quote]
- But I'd like to see a more practical explanation.
Any input appreciated!
Kaisa M. LindahlI use matrix when I have both row and column groupings. What I mean is if I
have row groupings as Dept, Group, User (drill down) and in the column I have
year, quarter, month drilldowns, u have to use a matrix. If you just have row
groupings I would suggest use the table, because a matrix is quite buggy when
it comes to exporting to excel.
Hope this helps
"Kaisa M. Lindahl" wrote:
> Hello.
> I'm fairly new to Reporting Services, so my question might seem really
> simple to you guys. But what is the difference between a matrix and a table?
> When should I use what? Are there any articles on the web that explain this?
> The best I've found is in this article:
> http://www.ftponline.com/vsm/2004_09/magazine/columns/databasedesign/default_pf.aspx
> [Quote]
> The report type defines the structure, or data region, of the data returned
> by your query. The Report Wizard lets you present this information as either
> a table or a matrix, though you have more options outside the wizard. The
> main difference between these two types of data regions is the number of
> columns. A table has a fixed number of columns; a matrix has a variable
> number determined by the query results.
> [/quote]
> - But I'd like to see a more practical explanation.
> Any input appreciated!
> Kaisa M. Lindahl
>
>

Difference between LEFT n RIGHT JOIN

Hi,
I have got a query for you guys. Can any one temme the difference between
"FROM Table_A LEFT JOIN Table_B" and "FROM Table_B RIGHT JOIN Table_A"
;)
Thanks,
Rahul JhaRead Books online|||There is no functional difference between the two examples you gave. LEFT OUTER JOIN is preferred for clarity and consistency.

Development server vs Live server deployment

How do you guys handle this? I want to create and develop our reports on our
development report services server with its own SQL server 2005 server...
then later when they are tested and working deploy them to our live server
with a completly different instance of SQL Server 2005 (enterprise edition)
and have them run there on its report services server with its data source
as itself... how would you go about doing this? thanks! Also is there a way
to change the database and database server at runtime (say in a VB.NET
application?) thanks!Smokey,
Check this page :
http://msdn2.microsoft.com/en-us/library/ms160854.aspx
for "PublishSampleReports.rss"
This should answer your "how would you go about doing this" part of the
question...
Andrei.
"Smokey Grindle" <nospam@.dontspamme.com> wrote in message
news:%23fQIZjOOHHA.1248@.TK2MSFTNGP03.phx.gbl...
> How do you guys handle this? I want to create and develop our reports on
> our development report services server with its own SQL server 2005
> server... then later when they are tested and working deploy them to our
> live server with a completly different instance of SQL Server 2005
> (enterprise edition) and have them run there on its report services server
> with its data source as itself... how would you go about doing this?
> thanks! Also is there a way to change the database and database server at
> runtime (say in a VB.NET application?) thanks!
>|||any idea how you would change the dataset's database and database server at
runtime of a report?
"Andrei" <andrei.toma@.era-environmental.com> wrote in message
news:O4ukonOOHHA.2236@.TK2MSFTNGP02.phx.gbl...
> Smokey,
> Check this page :
> http://msdn2.microsoft.com/en-us/library/ms160854.aspx
> for "PublishSampleReports.rss"
> This should answer your "how would you go about doing this" part of the
> question...
> Andrei.
> "Smokey Grindle" <nospam@.dontspamme.com> wrote in message
> news:%23fQIZjOOHHA.1248@.TK2MSFTNGP03.phx.gbl...
>> How do you guys handle this? I want to create and develop our reports on
>> our development report services server with its own SQL server 2005
>> server... then later when they are tested and working deploy them to our
>> live server with a completly different instance of SQL Server 2005
>> (enterprise edition) and have them run there on its report services
>> server with its data source as itself... how would you go about doing
>> this? thanks! Also is there a way to change the database and database
>> server at runtime (say in a VB.NET application?) thanks!
>|||Are you supporting multiple databases with the same structure or is this
just going from development to production? If you use shared datasources
then you configure it once on each server and after that you are good to go.
The reports go against the shared datasource which defaults to not being
overwritten so when you deploy it is left alone.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Smokey Grindle" <nospam@.dontspamme.com> wrote in message
news:eRK0myOOHHA.3212@.TK2MSFTNGP02.phx.gbl...
> any idea how you would change the dataset's database and database server
> at runtime of a report?
> "Andrei" <andrei.toma@.era-environmental.com> wrote in message
> news:O4ukonOOHHA.2236@.TK2MSFTNGP02.phx.gbl...
>> Smokey,
>> Check this page :
>> http://msdn2.microsoft.com/en-us/library/ms160854.aspx
>> for "PublishSampleReports.rss"
>> This should answer your "how would you go about doing this" part of the
>> question...
>> Andrei.
>> "Smokey Grindle" <nospam@.dontspamme.com> wrote in message
>> news:%23fQIZjOOHHA.1248@.TK2MSFTNGP03.phx.gbl...
>> How do you guys handle this? I want to create and develop our reports on
>> our development report services server with its own SQL server 2005
>> server... then later when they are tested and working deploy them to our
>> live server with a completly different instance of SQL Server 2005
>> (enterprise edition) and have them run there on its report services
>> server with its data source as itself... how would you go about doing
>> this? thanks! Also is there a way to change the database and database
>> server at runtime (say in a VB.NET application?) thanks!
>>
>|||multiple databases, We have this structure in our application...
Our Live server can have multiple databases with the same exact schema (we
have a Live system with real time data, and a testing system with weekly
data from the live system for testing out stuff) when we log into our
application you select the server and which database you are going to work
with... in crystal reports we manually changed the mappings in the report to
get it to work with the different databases on the server then ran the
report, just wondering how you can do something similar in reporting server.
90% of the time the reports are ran in the live system, but we still have to
support the other 10% and dont want to make copies of reports for each
database, because techincally, someone could make another database at any
point in time with the same schema
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:uiAgLBSOHHA.4848@.TK2MSFTNGP04.phx.gbl...
> Are you supporting multiple databases with the same structure or is this
> just going from development to production? If you use shared datasources
> then you configure it once on each server and after that you are good to
> go. The reports go against the shared datasource which defaults to not
> being overwritten so when you deploy it is left alone.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Smokey Grindle" <nospam@.dontspamme.com> wrote in message
> news:eRK0myOOHHA.3212@.TK2MSFTNGP02.phx.gbl...
>> any idea how you would change the dataset's database and database server
>> at runtime of a report?
>> "Andrei" <andrei.toma@.era-environmental.com> wrote in message
>> news:O4ukonOOHHA.2236@.TK2MSFTNGP02.phx.gbl...
>> Smokey,
>> Check this page :
>> http://msdn2.microsoft.com/en-us/library/ms160854.aspx
>> for "PublishSampleReports.rss"
>> This should answer your "how would you go about doing this" part of the
>> question...
>> Andrei.
>> "Smokey Grindle" <nospam@.dontspamme.com> wrote in message
>> news:%23fQIZjOOHHA.1248@.TK2MSFTNGP03.phx.gbl...
>> How do you guys handle this? I want to create and develop our reports
>> on our development report services server with its own SQL server 2005
>> server... then later when they are tested and working deploy them to
>> our live server with a completly different instance of SQL Server 2005
>> (enterprise edition) and have them run there on its report services
>> server with its data source as itself... how would you go about doing
>> this? thanks! Also is there a way to change the database and database
>> server at runtime (say in a VB.NET application?) thanks!
>>
>>
>

Determining Proper Maxdop, Threshold and Worker Threads.

Hey guys - I am wondering if anyone can suggest some good literature on determining the proper Maxdop, Parallel Threshold, and # of worker threads to run.

We were in the MS Lab out in San Jose last week benchmarking our app against SQL 2k and SQL 2k5, and it seems that CXPackets were killing us in 2k5 (running against 4 dc opterons). Turning off Maxdop helped, but we have a pretty wide range of queries in our application - stuff ranging from a couple of milliseconds to an occasional 10k ms. I would like to use maxdop, but I am wondering how to approach finding the ideal threshold (other than just benchmarking it to death).

Also, same kind of question on worker threads - is there a methodology for finding the right setting for my environment, or is it pin the tail on the donkey?

Our app typically runs against 16 or 32 way boxes with tons of memory.

Hi,

There is a rule of thumb concerning the worker threads in the BOL of SQL Server 2005.
In SQL Server 2005 this is 'self tuning' by default.

I don't know of any 'wonder' formulas to determine the other settings (except benchmarking it to death) :-)
If I do find something I'll let you know.

Kr