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.
Related
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.
Interested to know if anyone has had any experience with moving a VB6 application from SQL Server 2000 to a newer version of SQL Server.
There are VB6 legacy apps on a Windows 2000 Server
These VB6 apps connect to a SQL 2000 Database
We are looking to upgrade from SQL 2000 to SQL 2014
We are reporting with Crystal Reports
The VB6 apps have inline SQL within them
I'd like to understand what the possible implications could be?
Thanks
For one thing, there is no direct migration path from 2000 to 2014. This article (http://sqlmag.com/sql-server-2014/sql-select-steps-migrate-sql-server-2000-sql-server-2014) outlines some potential steps to take to perform the upgrade.
Things that may trip you up not mentioned in this article:
DTS no longer exists so if you have any DTS packages, it will be a project to upgrade/convert them all over to SQL Server Integration Serices (SSIS) packages.
If your VB6 app contains hard coded SQL statements, rather than just calling stored procedures, you could have minor syntax issues that would have to be rectified (so test EVERYTHING)
If you are also looking to migrate VB6 to .NET, there is an upgrade wizard out there somewhere, but it is HORRIBLE, so depending on the need, it may be faster to just re-write from scratch. If you are implying that the VB6 application would just connect to the migrated 2014 database, the note on the main question is accurate, but again...test EVERYTHING.
3a. If you are referencing any old COM components or old OCX controls, it will be a source of pain.
3b. Does your app do any reporting? old 2000 SSRS, or Crystal reports? again, another project.
Good luck!
I've done it, and there were stored procedures / user functions that needed to be updated for compatibility. Here is a Microsoft tool, SQL Server Upgrade Advisor. If you are using inline SQL in your code I'm not sure if this tool will help you. I was fortunate in that most on teh application SQL was implemented as stored procedures inside the database itself.
Here is an MSDN blog post about upgrade considerations and using the Upgrade Advisor tool.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
Apologies beforehand if I've been an unlucky searcher, but I feel like I'm either using the wrong keywords or there is nothing to find on the subject.
A colleague of mine has been using MS Access for decades and has no experience with other SQL tools. Most of the systems in our organisation are built on Oracle databases (and in quantities too large for MS Access), so data integration is often complex for him. To facilitate things, he will be moving his data sources to one of the Oracle servers, and will be able to access that data with Oracle SQL Developer.
All I'm able to find on the internet is how to migrate data but I'm looking for functionality differences from the perspective of a data analyst or a reporting developer, who works with preparated data.
I tried explaining it in simple terms, such as: "there are tables here as well", or "Oracle views are like Access queries", but there's a lot of ground to cover and I'm looking for some handles.
Do any of you know of a good source to read on this subject? Books, videos, articles, websites, anything. If at all possible, it should be in terms familiar to an MS Access user.
You not make it clear what developer tools you plan to replace Access with. Remember Access has two parts. The database part (the data engine). The data engine allows you to build tables, and execute SQL queries to retrieve data. This is also what the Oracle database allows you to accomplish.
Then there is the developer part. That is the part that lets you build forms (to edit data) and that of reports. This part is NOT part of the database engine (for Access or oracle).
So the differences in the database engine are NOT that important here, but MOST important is what tools you plan to build the reports and forms to edit data with?
You can most certainly continue to develop your software using Access. So Access has a VBA programming system, has the ability to develop forms, and also that of reports. However the database engine and table can be form the Oracle database.
So your question shows much confusing here since you not making any distinction between the developer tools (Access), and the database system you choose to WORK WITH Access. Access is a developer tool, much like VB6, c++, vb.net etc. It allows you to build reports and write code and build a user interface. A database system such as ACE, or Oracle or SQL server has no such ability.
The Access database engine (used to be called JET and is now called ACE) is a separate issue.
So a developer writing some software in say vb.net can choose to use the Oracle database system or can use the Access database engine called ACE.
It not clear if you plan to continue to use the Access development system, and then choose an appropriate database system such as SQL Server, MySQL or in your case Oracle as the database engine to work with Access.
If you plan to not use the Access development system to build reports and forms and write code, then you have to share with everyone here what tool(s) you plan to use. Since it sounds like the user is being dictated that they MUST use Oracle as the database system, then it likely that what developer tools such as vb.net, C++ or perhaps MS Access is also going to be forced upon the user.
Until such time you expand on what developer tools which are SEPARATE ISSUE from the database system is shared here, then any real answer is sheer speculation and a waste of our time.
So keep in mind that the Access databases engine, or SQL server, or Oracle or MySQL are database engines. AFTER you choose the database engine/system, you can then write code + forms in something like:
Vb.net
MS Access
Asp.net
Etc. etc. etc .etc
You also choose such systems as SQL reporting services, or whatever oracle has these days.
So if you crystal reports with ACE (the Access database engine), or you use crystal reports with SQL server or Oracle, then the feature set in crystal reports is VERY MUCH THE SAME in all cases.
And you might use MS Access reports with Oracle or SQL server or often the ACE (the default database engine for Access).
The user can continue to use Access as the user “interface” developer tool, and the data can be in any industry database engine that supports ODBC. The database system does not have nor include the user interface and reporting tools.
You not shared what reporting and development tools you plan to use with Oracle. As to what tool, well that like asking what kind of car to drive or what software development system should one choose. We don’t even know if the user has a choice. If they have a choice then they can continue to use Access and you have no need for a question here!
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.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
Which reporting technology would fit for the best situation/type of product? I am now thinking of 3 technologies:
Embedded Reports (Crystal Reports;MS Reporting services)
Server reports (MS Reporting Services)
OLAP Databases (MS Analysis Services)
Which report technology would you use for an off the shelf product? Is it possible to have a OLAP type based reporting side of things from a off the shelf product?
Which technology is best suited for historical data? I would guess here OLAP database would be quicker, but that would depend the size of the database, because I reckon you could also use Embedded Reports for historical data.
Which technology would be best for custom software solutions?
I like the idea of having reporting on the server where a user can go log in and run reports like with MS Reporting services. And really only have reports for stuff like invoices, bills, customer information sheet etc as Embedded reports. And also have Reporting services over an OLAP database for historical data.
Unfortunelaty does management not see this layout and wants a off the shelf product, with olap reporting right inside the application with all other reports.
OLAP isn't a reporting platform, it's in the database layer.
If you're going to have a collection of pre-planned, canned reports, then Crystal or RS are the best ideas. Personally I prefer Crystal but it can be quite a pain to develop reports - but when they're approved, Crystal is a rock steady platform. (We integrate Crystal with .NET apps.)
RS integrates just as nicely, but you do have to maintain the server. Their big advantage is dynamic/reactive menuing, but they are just as tricky to develop and maintain when not quite perfect.
OLAP is a really powerful technology - but if you've not got local knowledge, it's a really challenging product to deploy accurately. But, again, it's not a reporting product - but there are some interesting layers on top of it (e.g. ProClarity, Excel plug-in).
I like reporting services. It can be used as you say, with the customer logging into the reporting services web site. But there is also a component you can add to your application which uses reporting services on the back end. Best of both worlds.
Also, you can access data in analysis services or any other database.
Also you could take a look at (our very own) i-net Clear Reports (used to be i-net Crystal-Clear). Fully Java-based, can read Crystal Reports templates, and offer both a nice and simple API as well as a servlet for any major web server. Has nice charts using JFreeChart. Can export to PDF, HTML, SVG, as well as to a Swing Java Viewer you can embed into your own applications. We also offer a free and fully functional standalone report designer.
Costs a lot less than CR, also.
We are using XtraReports from DevExpress. The ratio price/productivity is very high and you can get source codes.
You can use it for desktop or web applications ( or export to pdf, doc, html, etc...) and end-user designer is delivered natively by DevExpress. I believe, this is one of the best reporting suite ( with Telerik Reports ).
I really like Reporting Services. You can embed reports into web pages, you can give users access to your reports over the web, you can even automate report delivery by having reports emailed to users at a set schedule. You can also create reports off OLAP databases. Plus Reporting Services comes with SQL Server so it can save some money.
Crystal reports is very easy and quick to use but it is also fairly limited. If all you need to do is slap some aggregate information onto a report, right out of a database, then crystal reports will be fine for you. Not sure about the others.