April 22, 2014 at 7:58 am
Hi all:
Ok, I'm somewhat new to SQL/SRSS and could really use some help in getting started on something I"m tasked with below. If anyone can chime in to point me to the right path, I'd be very thankful for.
I am trying to create a report that summarizes the total count of transactions that each salesperson has processed per a given month.
A transaction is defined when there is a $ value populated in the "Sold" column. Ie. if there is an amount in the row table for the salesperson, it means that a transaction was done.
The report would be simple:
Salesperson Number of Transactions
John5
Jane8
Robert9
Rick15
Mary 0
Would someone be able to direct me to the steps required to generate the above report? Not sure what the query would be, so if someone could help me on that that'll be great.
I'm thinking that after the dataset is completed, all I would need to do is bind it to the new report correct?
Thanks!
April 22, 2014 at 8:56 am
1. Define a datasource (points to your database)
2. Define a dataset (query that gets the data from the datasource)
3. Choose a Table from the toolbox and bind it to the dataset, selecting the fields you want in your report.
4. Voila!
April 22, 2014 at 9:14 am
Thanks! So I would just create the dataset to include all fields and have the the grouping done in SSRS?
April 22, 2014 at 10:35 am
Yeah, that's the easy way
April 22, 2014 at 12:46 pm
see this article I wrote on how to create a basic SSRS report using parameters http://sqlsaga.com/ssrs/how-to-create-a-basic-ssrs-report-with-parameters/[/url]. In your case I don't think you need the parameters.
SSRS again, not SRSS 😀 🙂
Good Luck 🙂 .. Visit www.sqlsaga.com for more t-sql code snippets and BI related how to articles.
April 23, 2014 at 6:26 am
Great link! Thank you for sharing and it really really helps me put things into context!
I"m still a bit confused which is typically the "Best Practice" to where I should put the criteria: in the SQL query, or should it be done within filters in the SSRS? Ie. if the critieria is *** simple as say SalespersonID = 12345
Thanks again.
P.S. SRSS 🙂 Yeah, I did a typo, and wanted to change it but editing the post didn't allow me to correct it......besides, I was just testing you all who would point it out 😀 😀
April 23, 2014 at 6:41 am
richardgregory06 (4/23/2014)
I"m still a bit confused which is typically the "Best Practice" to where I should put the criteria
It depends!
Check which method yields the best performance.
p.s.
Which is better
asking SQL Server to select a thousand rows from one million and pass a thousand rows to the Report Server
or
asking SQL Server to pass a million rows to the Report Server and asking the Report Server to filter for a thousand rows.
Far away is close at hand in the images of elsewhere.
Anon.
April 23, 2014 at 6:46 am
Well, that makes sense now now that you put it into perspective. It would be more efficient for SQL to do the front work in filtering the records first before passing it into the Report Server.
p.s.
Which is better
asking SQL Server to select a thousand rows from one million and pass a thousand rows to the Report Server
or
asking SQL Server to pass a million rows to the Report Server and asking the Report Server to filter for a thousand rows.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply