I am new to ms access; I am working on a database in an administrative setting. I need to filter office titles by bureau while also counting the number of said titles in each bureau.Any ideas on how I would go about doing this?
A Crosstab query (a.k.a. SQL TRANSFORM/PIVOT query) provides some pivot table features. Whereas a pivot table provides dynamic features (allowing real-time drill down, column selection and criteria specification), the Crosstab provides a single view of the data. The "drill-down" capability can be handled by other Crosstab queries with more specific WHERE selection and finer pivot intervals. The Crosstab does not support multiple pivoting columns, but one can combine results of multiple Crosstabs into a combined query using UNION statements and other techniques.
As expressed in other forums, you can export the data to Excel and use pivot tables there.
Related
I have an ssrs matrix and have a lookup to another dataset2 field (Jurisdiction)
I want to row group by this dataset2 Jurisdiction.
The problem is that the tablix will work on a non group lookup but will not allow me to group on and display the dataset jurisdiction field.
is this possible in ssrs?
Thanks
As a general rule, it's much better to join subqueries in the SQL rather than using the Lookup function. Both in terms of efficiency and also avoiding the limitation you described in the report design.
If the datasets are truly different data sources, consider using an ETL process to combine them into a single table for the report to use as its dataset.
We have a system which contains 4 Hierarchies.
1. Senior Manager
2. Manager
3. Supervisor
4. Employee
Data related to all these are stored in different tables with respective details.
There is a single address table which contains address of all these hierarchies.
Sample Data Set
We would be able to do a count on each IDs by City, State and Country.
Since OLAP cubes cannot be directly used as data set in BIRT, Shall I combine all this data in one single table and load it and then create a cube with the following Hierarchy?
COUNTRY
STATE
CITY
SENIOR MANAGER
MANAGER
SUPERVISOR
EMPLOYEE
and add the below in summary fields.
SENIOR MANAGER COUNT
MANAGER COUNT
SUPERVISOR COUNT
EMPLOYEE COUNT
The goal is to report count of employee, by Territory or by role(senior manager, manager etc).
Thanks.
Usually it is best to do aggregation on the DB side, e.g. use SQL JOIN syntax and GROUP BY.
If you need aggregation data and details, you have two choices (depending on your DB, I don't know if MySQL supports this):
You can either select only the details (all in one query) and use BIRT's grouping and aggregation features on table or list items to get the aggregations alongside.
Or you can use SQL analytic functions (similar to group functions, but with an OVER(...) clause) to do it all in SQL and let BIRT just emit the results. You still need BIRT's grouping, though, to output the aggregations in the correct header or footer lines.
As a rule of thumb, it is usually best to let the DB do as much work as possible.
This is more reusable (say if you decide to use a different reporting library later) and also much faster, as this is what a RDBMS is designed for.
However, you can also nest table or list items in the BIRT report layout (a feature which is hardly known). This allows you to develop master/detail reports which use individual SQL queries for each level. But if you want aggregations, things will be much more complicated with this approach.
I have created 2 datasets that return data from a web service.
now I want to merge those two datasets in a single dataset, is it possible to create another dataset that contains those 2 merged ?
PS: you can also propose new solutions
Unfortunately SSRS doesn't offer that feature. One alternative is using the Lookup and LookupSet functions to use both datasets together in the report, but this is not efficient for large datasets. If the data doesn't need to be live, another option would be to create a procedure that caches the joined data in a table on a schedule and then use that table in the report. If those options aren't adequate, you may want to look at using a different reporting tool such as Excel (with web services and power query) or Tableau (if you have licenses).
I am in the process of setting up a new cube. This cube is going to be very similar to a cube that exists except it will contain only data where the date is not in the past.
The current table has data that is past and present. 1 idea was to create a database view on this table and include any rows where the date was >= getdate() but I don't think you can select a database view when setting up a cube, is this right? Another option would be to create a new database table that includes only those records with a present or future date.
The final option would be to filter the current cube but I think I would prefer a fresh cube with only this data as it will be predominantly used by users in excel pivot tables so I want to avoid any filters/mdx if possible.
What would be the way of achieving this?
Thanks
You can most definitely add a view in your SSAS DSV. You can select views or tables in the object chooser dialog box. You can also write a named query. Many people advise that you should always use views in your DSV for your cube. It creates a layer between the cube and the physical tables.
Another approach is to use the existing cube as a source for a Power Pivot model and filter the dates in the data model in Excel and then provide that model/Excel file to your users.
I have created a complex report in Microsoft Business Intelligence.
The report has its own (fairly complex) WHERE clause. Is it possible for the user to set the CreatedOn date as part of the criteria?
UPDATE
I was looking at this again. On a basic report (one table) if i import the report over one created with the report wizard, this give you the filter options and works.
On the more complex report that uses the union statement to pull data out of two tables the filter options are available however they have no effect, this is after removing the where clause.
END UPDATE
Thanks
Luke
I have been doing some research into this topic, and it appears that if you alias the fields and prefix them with CRMAF_ this allows you to add filtering. I'm going to look at this over the next few days and see how it works. However it has been noted that several people have been unable to get this to work correctly.
Please note you need to prefix both the table and fields.
You then can set the filter.