September 10, 2008 at 7:38 am
This is a "big" question, and I'm looking for general ideas, books to look at, your experiences:
What would you recommend as the "best" development pathway for me to meet my organization's needs?
What I Need
I need to periodically push/send reports (not yet created) to users, preferably by email, preferably as something like an Excel spreadsheet so users can manipulate the data. But, I'd also like users to be able to run these reports themselves, probably from a web page, using some criteria they specify.
What would you suggest? Is there an advantage in learning .NET for any of this? What books/websites would you recommend for learning about sending data from SQL Server to Crystal or learning/using Reporting Services?
Thanks very much,
Rich Mechaber
What I Have to Work With
I consider myself an intermediate level SQL dba, with web development skills in ASP classic and PHP. We're running SQL Server 2005 Enterprise, IIS 6, and Crystal Developer XI. Our main DB App is a third party system written in ASP classic (with many DLLs in middleware, the logic of which is mostly inaccessible to me as a developer) using SQL back-end, generating user-initiated Crystal Reports delivered to desktops with a Crystal ActiveX. I don't have Reporting Services installed and I haven't worked with it. I'm a beginner with Crystal Reports, but it's similar enough to Access report development, at which I'm reasonably experienced (sub-reports, code-driven formatting, etc.).
September 10, 2008 at 7:47 am
Reporting Services ticks all the boxes for your requirements. It also has some similarities with Access so it shouldn't be too hard to figure out. The interface to email reports will be simpler than other tools.
Recommend Microsoft SQL Server 2005 Reporting Services - Brian Larson
Published by Osborne
September 10, 2008 at 8:45 am
First, you really should direct efforts to users never taking the results of reports and making modifications. I know this is sometimes difficult, but it is not only inefficient from a user standpoint, but it is a compliance problem in a lot of areas.
As far as a tool, don't get too bound to one tool because they all have their strengths and weaknesses. I would say learn Reporting Services and drop Crystal. Crystal is more mature and therefore can do some things more easily than you can in Reporting Services, but from an Enterprise Reporting standpoint, if you are already using MS SQL, Reporting Services will be less expensive overall (software and resources) and ultimately be able to give you nearly the same results.
From there, in my opinion, DBA's should be gently directing companies into the data warehousing direction.
September 10, 2008 at 9:28 am
SSRS is the way to go. I have over 200 custom reports I use in various ways. Most are on demand by the user, they click on the web link in Report Server and enter some criteria in dropdown boxes, a few seconds later they have their report, can export to Excel and do what they want with the data.
I also have a few that I schedule after known db processes, then email the reports to a few top level persons.
It is tight with SQL, secure by way of AD and light because it's web. Create reports in BIDS ( Business Intelligence Studio) it's really easy to use, and if you already know your tables/data, it won't take you long at all to catch on. The best part: you already own it.
September 10, 2008 at 2:10 pm
Thanks to all who replied. SSRS is something I will definitely look into.
To Michael Earl: I do appreciate the need for consistent reporting. Many times, however, I work with managers who aren't yet sure themselves how best to present the reports, or they just need a static but searchable/sortable list as of a certain date, say. If I give them a report they can manipulate - and this is data they already have access to.
Rich Mechaber
September 11, 2008 at 7:02 pm
It sounds like you have total freedom to explore all roads to meet your needs, but if your company has paid for Crystal, you may want to take some time and talk to people who may be key decision makers. They may expect you to use Crystal, or at least outline why SSRS is a better choice.
(SSRS is really easy to work with, just remember to do the data organization in the view or procedure and not in the report)
its only a small amount of foot work, but will gain some people on your side, rather than against.
Even consider taking a short check list of what you have found so far and discuss with them.
Do not under-estimate the value of internal networking, and this gives you a really valuable one to press the flesh. Reports are a people oriented part of technology. use it wisely.
The more you are prepared, the less you need it.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply