I have wpf application and it needs report printing. for example daily, monthly sales. Should I use Crystal report or Flow Document with tabular will do? I know this is naive question.
I need faster and free reporting solution....
thanks
Microsoft SQL Server Reporting Services are well worth looking in to: in my experience far less buggy than Crystal and all you need to is add a Report (RDL) file to your project and drag on a viewer (with WPF may be necessary to host it in a WindowsFormsHost control, though). Or you can go the whole hog and install SQL Server with reporting services, so that the reports are processed on the server. You get a load of decent export options (PDF, HTML,..) and there's plenty of flexibility and customisation for logic and rules in the report.
Related
We are using the IBM Cognos Report Studio for Making the Reports.
And we have 1000s of reports developed and using.
Now i need to fetch all the SQL queries written in these 1000+ reports.
For that at present i am opening the report studio for each individual report and getting the query.
But it is very tedious job and taking months to get all the SQLs in these 1000+ reports.
So i am looking for a way to get all these queries from database behind Cognos studio.
Does these report parameters (including the SQL) store in a Database or only in Contentstore?
If it store in DB then is it possible to access the Report Studio in a Database tool like Oracle SQL Developer?
So that i can fetch all the SQLs in one shot from the database table.
Thanks for the help!
My experience migrating from one reporting product to another is like what you are asking. I think I had 7000 reports that I was aware of plus many reports sitting on workstation hard drives. At some point along the way we realized that the new product had different features than the old one, so report redesign was a good option in most cases. It took 18 months once we actually started working on the reports. That was to replace the 700 "standard" reports. Users were on their own (with support from IT and subject matter experts) for their custom work. I now have about 19,000 reports in Cognos.
Except where the report developer wrote SQL in a SQL object in the Queries area, Cognos reports do not contain SQL code. Cognos generates the SQL at runtime based on the report spec and user interaction (what parameters they set, what page the opened, etc.). Short of writing your own report spec parser, duplicating the work that Cognos does for you, there is no way I know of to generate the SQL.
One possibility: I haven't dug too deeply into the Cognos SDK. There may be a method there to generate the SQL for each report. Then you can do it automatically. Be aware that for thousands of reports you'll want to run this process during non-work hours. It could run for hours and may use a lot of resources.
Another possibility: Turn on native query logging (Cognos Administration | System | All dispatchers | | Set properties | Settings | Logging | Check the boxes for "Audit the native query..."). Then have a person, a product like those from Motio, or a Cognos SDK program you create yourself run every report. Then you can get the SQL from the Audit database. Of course, the problem here is answering prompts. It will probably take a person to run these.
To add two columns to a list, or two data elements to a report or page header or footer, or two filters (I don't know what you mean by "clause"), you'll want to use the Cognos SDK.
Choose relevant examples of different types of reports.
Examine the XML report spec for each of those reports.
Determine how to identify where the new element should appear in the XML.
Write a program (probably in C# or Java) to use the SDK to...
inspect every report in your environment.
determine which pattern the report fits.
add the data elements.
save the report.
How can one extract report solutions from SQL Server Reporting Services?
I may need to take over development of reports, but original solutions are... missing.
What can be done in such situation?
Yes that is possible. It depends on how many reports you have, but if you edit the properties of a report in the reporting services manager web site you can choose to download the rdl file, just add those to a new solution in visual studio.
Have a look at this link
There are automated ways to get all rdl files if you want that too.
There is a SQL only way for example.
The easiest way in my opinion is using the RS.exe command line interface
I am currently working on TFS 2013 and would like to know how to generate custom reports.
Tried google to find out a tutorial but couldn't find anything great. If someone has then please let me know.
Whether SQL Server 2008 R2 Enterprise Reporting Service will be ok for TFS 2013 to generate reports?
TFS has a few mechanisms for doing reporting:
Work Item Queries (WIQ) - Work Item Queries can be created and saved for reuse. Work Item Queries are easy to create, and can answer the majority of questions that users have.
Excel Reporting - Work Item Queries can be exported to Excel to provide more advanced capabilities around analyzing the data resulting from the Query. Various different views of the data along with charts/graphs can be created using standard Excel functionality. Creating Excel Reports requires some expertise in Excel, but the resulting file can be saved and the data can be automatically refreshed from TFS.
SSRS (SQL Server Reporting Services) - This is the most advanced Reporting option. SSRS reports require a developer to create, but it provides the flexibility to report and analyze any data stored in TFS in almost any way imaginable.
TFS Web Access (TWA) - TFS Web Access provides some basic charts/graphs that can be viewed in the browser (Burndown, Cumulative Flow, Velocity Chart, etc). In addition, web-based Charts/Graphs can be generated based on the results of Work Item Queries. This is less flexible than the Excel option, but also more user-friendly and usable by any TFS user.
The advanced option - SSRS Reports - are just your run-of-the-mill SSRS reports that use the TFS Data Warehouse and/or the TFS Cube as a data source. You can read a guide about developing custom SSRS reports for TFS here: http://vsarreportguide.codeplex.com/
I have been looking into PowerPivot and concluded that for "self service BI" and ahoc buidling of cubes it has its uses. In particular I like the enhanced UI that you get from using PowerPivot rather than just using a PivotTable hooked up to an analysis services datasource.
However it seems that hooking up PowerPivot to an existing analysis services cube is not a solution for "organisational BI". It is not always desireable to suck millions of rows into excel at once and the interface between PowerPivot and analysis services is very poor in my book.
Hence the question is can an existing analysis services solution get the enhanced ui features that power pivot brings, without using powerpivot as the design tool? If powerpivot is aimed at self service/personal BI then it seems bizare that the UI for this is better than for bigger/more costly analysis services solutions.
Although I agree that PowerPivot has a nicer UI than using Analysis Services via standard pivot tables, PowerPivot through the Excel client has some really bad drawbacks when trying to use it in lieu of Analysis Services.
You have to download all the rows into your spreadsheet to "refresh" the data. In large data warehouses, this is equivalent to having users run SELECT * queries directly against your database. It's horribly slow for the user and has a high resource usage cost to your server.
It is extremely easy for someone to either intentionally or unintentionally walk out of the office with your entire data warehouse in a non-secure manner. Ouch!
The end-user machines need to be pretty powerful. I tried using PowerPivot with a few small tables (5 million rows or less) on our standard company machine build and it did not have sufficient memory to refresh PowerPivot. The only way I can see to deploy PowerPivot across the enterprise is to upgrade all of the analyst machines to 64-bit Windows 7 with at least 6GB to 8GB of RAM. Although this can be feasible in a small organization, it is not a reasonable solution in a large enterprise.
You won't have any good metrics on how people are using your data if you hand out PowerPivot with unrestricted access to your data warehouse. Yes, you may have metrics on how frequently people hit the refresh button and you may be able to log which tables they are querying, but you won't see how they use the data unless you audit their spreadsheets directly. And even then, you will only get their final result -- not their path to how they got to the final result.
PowerPivot generates really, really big files. Even if someone drills the data down to a small subset of the total data, it is still difficult to share the files with others since large PowerPivot files generally exceed minimum Exchange server file size limits. I've encountered this at my organization despite never having had this problem with an Analysis Services files.
PowerPivot does not have a very good security model. Sure, you can restrict who gets to the data the first time, but you can't restrict it once it is in the spreadsheet. Analysis Services prevents users from making changes to the spreadsheet if they don't have access to the underlying cube. It's just so easy to compromise the security of your most valuable business data with PowerPivot.
PowerPivot does not currently scale for very large data sources. I have several multi-billion fact tables that just can't be downloaded by PowerPivot unless I pre-aggregate them down to a few hundred million rows. PowerPivot works really well for small data warehouses, but it doesn't elegantly scale to large data warehouses.
Please note my above comments don't apply to PowerPivot via SharePoint. I haven't tried the SharePoint integrated product out, but many of the above concerns seem to have been addressed from the documentation and demonstrations that I've seen of the SharePoint version of the product.
Despite all of the above comments, PowerPivot could work as a replacement for Analysis Services if you have a very small or immature data warehouse. If your largest fact table is a few million rows, then the overhead of building and maintaining a data warehouse may not be cost effective if you are a BI team of 1-2 people. PowerPivot is probably a great new feature for a department that doesn't have a dedicated BI team and only has a handful of Excel junky analysts. It doesn't take much sophistication to put together a virtual data mart from disparate data sources with PowerPivot. But if you want to build a truly professional data warehouse that is secure, scalable, and highly manageable, then I would recommend building cubes in Analysis Services and either use Excel or a 3rd party vendors tools for connecting to the Analysis Services OLAP cubes.
Now that SQL Server 2012 is released, you may want to take a look at using one or more SSAS BISM models, rather than PowerPivot. You get interop with PowerPivot, but you can now build your model using SSDT (in Visual Studio) and can get more control over security and can host on a dedicated server.
I'll be presenting live and online this spring and summer of the BISM - here's my latest deck on slideshare - http://www.slideshare.net/lynnlangit/sql-2012-bism
Now that Office 2013 preview is out, you can check out PowerView inside of Excel (PowerPivot) without the need to have SharePoint. It remains to be seen when MSFT will remove the dependency on Silverlight (i.e. move to HTML5). The preview release of Office 2013 that I got in September still included PowerPivot which required Silverlight. I am looking forward to the release built on HTML5. Here's a deck by Jen Underwood to give you an idea of what PowerView looks like.
WebPivotTable is a pure javascript pivot table and pivot chart component which can be used to pivot csv data and all kinds of OLAP cubes, include microsoft SSAS. It mimics all functionalities of Excel but web based, no dependence on any other plugins, drivers, server side compoenents. It can be easily to integrated into any web application and web sites.
Here is Demo and Documents
I know that Powerpivot is a free download for Excel 2010, but for a better desktop client experience you should look at the ProClarity client.
Also worth looking at Analyzer by Strategy Companion (http://www.strategycompanion.com).
I've found it provides a smooth web-based interface for slicing and dicing in pivot tables (and charts) that is nicer than what is provided by Excel 2007.
ProClarity was the runaway best option until Microsoft bought them and killed the product. Some of the features are making their way into other tools, but the product itself is no longer supported. Panorama or Tableau are probably the best 3rd party options.
This is the best I've found so far that is up-to-date: http://www.varigence.com/products/vivid/videos
Edit: http://silverlight.galantis.com is also a possible solution - WPF version comes out next month that could be used is a VSTO add-in.
Is there a simpler interface for end users to run "queries" on pre-existing SqlServer Analysis Service cubes? I'm looking for a way to deploy the cubes and allow the users to work with the data through a simpler interface than BIDS. Is this even possible?
I would recommend Excel too. It is an environment that your users are familiar with anyway, and they will be able to perform additional analysis (totals etc) without learning any new interfaces.
However, I would advise against pivot tables as a method of getting the data into Excel. I once worked on a project using pivot tables, and it was a filthy nightmare. The more recent versions of Office have a slightly different tool called "Microsoft Office Excel Add-in for SQL Server Analysis Services" which can get OLAP data into Excel. I downloaded XLAddinSetup.msi for Excel 2002/3 or you can use this method for Excel 2007.
You can use Excel with pivot tables for that, no need to write any queries at all, they can drill down to all the data they need
There's a couple of End User Reporting Tools around.
Our tool - RSinteract, is quite cheap and effective. It uses an AJAXy web interface so no need to install on the client and has drag and drop functionality similar to the other tools. It also has a 30 day evaluation.
There are many, many tools. An incomplete overview can be found here: http://www.ssas-info.com/analysis-services-client-tools-frontend
Dundas has a set of tools that let you drag and drop dimensions/hierarchies/measures to create visualizations like charts and/or grids. The product name is Dundas Chart for ASP.NET Enterprise Edition, and it has a free demo.
ProClarity also had a suite of tools. Not sure how you get those tools any longer, but I think they are part of MSDN now.
As stated by Jay, there are several client tools you can use to query the cubes that give the end user the ability to drag and drop dimensions for ad-hoc querying.
ProClarity has been acquired by Microsoft, and most of the functionality is being incorporated into PerformancePoint
Panorama Software (original developers of Analysis Services) also provide access with their NovaView products
Another option is Report Builder, that comes for free with SQL Server.
Though the SQL Server 2005 version is a bit cranky, the new release with SQL Server 2008 seems to work much better.
Although it isn't as flexible as excel for ad-hoc queries,it comes very handy for some scenarios.