There is an application which can be described as reporting as well as content management system. Most of the views of the application are tabular reports which can be extracted in excel.
Can anybody suggest a tool which would be useful to handle generation of tabular reports. Sometimes there might be 10-15 columns. Also the tool should have feature to handle documents as well; meaning possibility to upload documents and share the same to the application users.
Please note that the tool may not be open sourced. If there is any licensing cost, that will also holds good.
Thanks!
Use SQL Server reporting service by Microsoft and ASP.Net MVC or JAVA application for all your need.
Link : https://learn.microsoft.com/en-us/sql/reporting-services/create-a-basic-table-report-ssrs-tutorial?view=sql-server-2017
https://learn.microsoft.com/en-us/sql/ssdt/download-sql-server-data-tools-ssdt?view=sql-server-2017
SSRS is an independent reporting tool. Will work for both .Net or Java.
Related
This question already has answers here:
Compare SQL Server Reporting Services to Crystal Reports [closed]
(18 answers)
Closed 9 years ago.
I'm going to develop an application...Just wondering...
What are the difference between SSRS and Crystal Report?[Visual Studio 2010]
Can you provide pros and cons?
I have used both Although Crystal Reports is very well know and widely used. It can be a hassle at times (Not saying that SQL Server reporting services is not a hassle sometimes.)
Pros for Crystal Reports
May people use it and understand how to use it. Its ability in the
creation of more basic to intermediate reports quickly is a plus.
Even if you don't know SQL you can still fiddle with Crystal Reports
to get the result you want, and flatten out the data. Supports
Dynamic Cascading Prompts (version XI and Higher) Supports Web
Viewer, ActiveX, Java and HTML.
Cons for Crystal Reports
Crystal's Report Design Component seems to be full of strange
scenarios. I believe because the software has changed hands so many
times. Documentation is pretty limited for the Report Design
Component. A beginner can definitely create a nice formatted report
quickly and easily, but when it comes to more complex reports where
performance is needed. Going back to understanding SQL is necessary.
Pros for SQL Server Reporting
Web Based Reporting Server Report Rendering Engine supports a number
of formats (Excel, HTML, Image, and more) Publishing and scheduling
is a part of Reporting Services. In crystal you need Crystal Reports
Server or Business Objects Enterprise for Publishing and scheduling.
Or you would need to create your own custom app) Parameter prompting
is nicer in my opinion Saved Data sources can be accessed by excel
users. User login an permissions are built in. Subscriptions are a
built in feature
Cons for SQL Server Reporting
It can sometimes be a pain to implement the Report builder feature
for building simple reports is somewhat limited The best report
builder is Visual Studio's Business Intelligence Studio. This is only
a con because for a beginning end user this could seem overwhelming
In all SQL Server Reporting Services is my pick.
I'm currently in an internship and i have to create a whole BI application.
I think i'll use pentaho, and I have to use just open source component.
I know that Pentaho Analyzer is not free
My question is: Is saiku an equivalent of analyzer?
If yes, can I use it with pentaho instead of analyzer?
thks
I'm the developer of Pivot4J project and want to share my (subjective) opinion on the subject.
First, as though you righteously assumed Pivot4J to be more of an API than an application, it does not always mean you need to write lot of code to use it.
We also have a Pentaho BI plugin which does not require any coding and has comparable features to Saiku plugin, though it's targeted toward the yet unreleased Pentaho 5.0 platform.
And our sample application provides most of the functionalities that JPivot web application has, even though it lacks a data source configuration feature which will be soon to be fixed.
Compared to Saiku, I think each project has its own advantage in different scenarios.
Saiku has a much lightweight architecture on the client side than our sample application and the plugin, so it can be deployed and embedded virtually anywhere.
While it's not much difficult to create a full REST style analytic application with Pivot4J, our current sample and plugin applications require at least a Servlet container to run and are more difficult to be embeded than Saiku in certain environment.
On the other hand, as Pivot4J is designed to be UI independent API from the start, it could provide more flexibility than Saiku in my opinion to developers when they want to build their own application on top of it, or intend to customize core behaviors of the API.
For example, if you want to use Pivot4J with your own application which is build with ExtJS, DhtmlX, or any other UI toolkits, it'd be much easier to achieve a seamless integration with Pivot4J, as it provides you with convenient abstract extension points to do that.
Finally, if you're familiar with Javascript you might find working with Saiku easier as it delegates most of the UI related works to the client side.
On the other hand, if you're an old school Java developer like me :) you might find our sample application to be easier to understand and work with, as there's virtually no custom script involved and everything is done on the server side with JSF component model.
To conclude, I'd like to say that Pivot4J is not just an API which cannot be used without writing much codes as it already includes quite feature complete Pentaho BI plugin for the upcoming 5.0 release of the platform. And as Pivot4J and Saiku take rather different approach from each other, each has its own strength and advantage which could be leveraged to suit the specific use case.
Yes of course. Both the tools use the same underlying OLAP engine - Mondrian. Saiku is essentially the same as analyzer providing many of the same features - however it has a different architecture which additionally makes it very embeddable and pluggable. Plus Saiku can be used standalone too if you want to.
Check out the demo at dev.analytical-labs.com to see what it can do.
Also for help you wont find many tools with such a great community - hook up with them on Freenode IRC at either ##Pentaho or ##Saiku depending on your questions!
Pentaho is the right choice for OS BI too - Presume you looked at Jaspersoft as well? Worth a look but you'll no doubt realise the features are better in Pentaho.
Have you think about a pure javascript UI to pivot your olap cubes? There is one such component calls WebPivotTable at http://webpivottable.com
Jpivot, saiku and pentaho are all based on olap4j API so that they all need a java server side service. WebPivotTable use AJAX call to xmla service directly so that it can be used to pivot any xmla OLAP server, like mondrian, SSAS, iccube. Since it doesn't tie up with any java back end and also it is pure javascript based, you can easily integrate it into any website or web application.
I need to find a stand-alone (ie. no OpenOffice-based tools, for instance) Windows application that can present users with forms to enter records into an SQLite database. The goal is to migrate data from Excel sheets into a serverless, single-user database like SQLite.
As a bonus, the application would also have a somewhat-protected admin section so that I can also use it to CRUD data with the same app, but it's not a requirement.
There are a lot of applications listed on the official SQLite site: Can someone recommend one that is meant for end-users, either open- or closed-source?
Thank you.
Edit: the correct term I was looking for is "data entry form". Googling around didn't return a Windows application that makes it possible to easily write data entry forms to let end-users create/edit records, ie. with no direct access to the underlying tables.
I think FileMaker or Microsoft Infopath (May be with Sharepoint Services) could fulfill your needs completely. There are forms in both, validation, different available sources for keeping data, working over net. Both are very flexible and powerful. Infopath with Sharepoint Services can be installed and customized quite quickly.
I'm a junior VB.net developer with little application design knowledge. I've been reading a lot of material online regarding different design patterns, frameworks, and methodologies. It's become a bit confusing for me.
Right now I'm trying to decide on what language would be best suited to convert an existing VB6 application (with SQL server backend.) I need to update the UI and add more user functionality and reporting capabilities. Initially I was thinking of using WPF and attempting the MVVM model for this big project. Reports would be generated from SSRS.
A peer suggested using ASP.net and I don't have enough experience to determine what would be better. The senior programmers here are stuck on using VB6 and don't have any input on what to use. They are encouraging me to use the latest technologies.
This application would be for ~20 users in a central location. Ideally I would stick to a Microsoft .net language. Current interface is similar to a datagrid table where the user would click in to see the detail of each record. They would need to have multiple records open at any given time.
I look forward to all the advice I can get.
EDIT 2010/04/22 2:47 PM EST
What is your audience? Internal clients within an intranet
How complex are the interactions you expect to implement? not very... displaying data from SQL server to UI. Allow user updates to said data. Typically just one user modifying a record.
Do you require near real-time data updates? no
How often do you expect to update the application after the first release? twice/year
Do you expect a well-defined set of client platforms? Yes, windows xp environment, potentially upgrading to Win7. Currently in IE.6 moving to IE7 or 8 within a couple of months.
Do users need access from anywhere? No, just from their PC.
What would be wrong about building a simple ASP.Net application in VB.Net using Gridviews for allowing the data access and manipulation? Seems like a simple ADO.Net trial application if you aren't familiar with it in the beginning you will be by the end. CRUD applications are pretty common so it shouldn't be too hard to build it and then refine it as more requirements become apparent.
Sounds like you need to use a web-based solution--this eliminates alot of your potential distribution woes with multiple users. You could use silverlight, but if you are locked into SSRS, this might not be the way to go.
I'm in the middle of a contract that is porting a company's hand-rolled Microsoft Access-based CRM to Microsoft CRM 4.0. It's all gone pretty well, but now I have to migrate the data across.
The data is all over the place in the source .mdb. Lots of tables, lots of duplication, and generally shows all the signs of an ad-hoc database which has grown organically (like weeds) over time.
So, my dilemma is this. Do I bite the bullet and write lots of queries inside Access to export the data into some intermediate format that CRM can somehow import? Or is there some other way? Are there any middleware tools that map data from one to the other that anyone here knows about?
Note this is my first time using CRM, so if the question is obvious, I appologise.
Cheers,
Shane
Dynamics CRM 4.0 provides built in tool called Dynamics CRM 4.0 Data Migration Manager to help developers migrate data from previous database into Dynamics CRM 4.0 database. I haven't used it extensively, but as far as i know, the previous data needs to be exported into a "standard" excel format provided by CRM 4.0 Data Migration Manager (DMM).
You can refer to below references :
http://blogs.msdn.com/crm/archive/2008/01/04/microsoft-dynamics-crm-4-0-data-migration-manager-with-john-o-donnell.aspx
http://www.microsoft.com/downloads/details.aspx?FamilyID=6766880a-da8f-4336-a278-9a5367eb79ca&displaylang=en
There is also 3rd party solutions called Scribe http://www.scribesoft.com/ that will help you migrate to Dynamics CRM 4.0 database
I've had success just using the mscrm api in these kinds of cases. You can write a .net app which use odbc to connect to your mdb then use the mscrm api to create the entities you need on that end.
Anyway you cut it - it's not too pretty but you can get the job done.
Good luck.
Ms CRM Service Reference
I am sorry to say, I think you have to bite the bullet and write queries to pull the data from various sources and use some intermediate database like access ( You may also use SQL server or any db)
In my experience of handling several data migration projects for various small and large enterprises, I have always uses MS access as my data massaging/pulling tool. It works great. It might sound a lot of work but it’s is definitely lot cheaper than buying any expensive tools and spending thousands of dollars configuring them.
I would recommend you save all your queries and write a macro to automate the import.
Hower trivial the query is, SAVE it. This will be very useful as you will have to do this again and again before you actually go live.
Once you automate it, it is just a matter of clicking a button.
Typically and data migrating project will undergo at least 2 iterations and it could go up to 10.
Once you have data in the intermediate database, you can use de duping tools to standardize and remove dups from your data. There are a lots of cheap tools available both online and offline.