There were two obvious alternatives: stick with the free version of Crystal Reports that comes with Visual Studio (which is limited) or buy a commercial reporting tool. The old R&R Report Writer from dBase days was inexpensive and effective. Suffice to say that reporting tools today are dramatically more expensive.
Months later I learned about something called SQL Server Reporting Services. The only problem was finding it. Have you seen how many versions of SQL Server there are out there? MSDE, Express, Workgroup, Standard, Developer, Enterprise... Then you have to sort through Add-Ons such as Analysis Services, Reporting Services and Integration Services. Then you have to figure out what combinations of add-ons can be used with which versions of SQL Server. Finally, you have to figure out what obscure file to download to enable each of the various add-ons.
And did I mention the difficulty in sorting out the licensing rights to the various versions for us in development (non-production) environments?
And, to top it all of, it'll be a cold day in hell before you find any of this in Microsoft documentation. It was actually easier to find some of the information in Wikipedia than in Microsoft's docs!
So here I am, running Visual Studio 2008 on Windows Vista. Of course, VS2008 doesn't ship with SQL Server, you have to install SQL Server Express 2005. No problem there, but SQL Server Express 2005 doesn't ship with Reporting Services and you won't find any download labeled Reporting Services.
I thought I had struck gold when I found an article titled Introducing Business Intelligence Development Studio. That article says that Visual Studio 2005 has specific project types for creating reports and that you just need to select Add New Project. Fantastic! Of course, when I looked in VS2005 there was no such project type and the article had no troubleshooting tips.
Are you detecting a trend here?
I found a post where numerous people attempted to figure out how to get through this morass. The final conclusion was that you had to uninstall the Workstation components and install a new copy from a fresh download of the "SQL Express Toolkit." Of course, the person didn't post the link to that download and it isn't on MSDN Downloads.
I finally found it under the name Microsoft SQL Server 2005 Express Edition Toolkit. When I tried to install it on Vista I got a "compatibility warning." It remains to be seen what problems that causes. (Note that the Business Intelligence components under Workstation are not selected by default, so you have to make sure you check them manually.)
At this point I opened VS2008, tried to add a new project, and discovered that Business Intelligence Project was not one of the choices. (And yes, I did restart VS2008.) More digging on the web uncovered this little gem: Visual Studio 2008 Will NOT Support SQL Server 2005 Reporting Services projects.
So I started VS2005 and saw that Business Intelligence Projects was now visible at the top of the list in the Add New Project dialog in VS2005. Under that project type were two entries for Report Server Project. I also found the SQL Server Business Intelligence Development Studio (BIDS) in my Start menu under SQL Server 2005. I'm not yet sure exactly what the difference is between BIDS and the VS2005 projects.
If you need to install something other than Reporting Services, the instructions above won't help you much. After Setup is complete, you'll see this message:
The version of Business Intelligence Development Tools that is included in SQL Server 2005 Express Edition Toolkit does not include projects for SQL Server 2005 Integration Services or SQL Server 2005 Analysis Services. These projects are available only with editions of SQL Server 2005 that include Integration Services and Analysis Services. SQL Server 2005 Express Edition does not include Integration Services or Analysis Services.You'll notice that this message does not tell you which versions of SQL Server will do what you need.
So I've gotten further than I was, but I still have several questions to resolve:
- What is the relationship between BIDS and VS2005?
- How do I install Analysis Services?
- How do I install the server-side components of Reporting Services?
- How will all of this change when SQL Server 2008 is released?
[Update 1/9/2008] Here are some initial answers to my questions:
- BIDS runs in Visual Studio 2005. It's a "personality", just like C++ versus C#.
- TBD
- You have to install SQL Server 2005 Express Edition with Advanced Services SP2. In addition, when you do that installation, you have to specifically enable the features for Reporting Services. My recommendation is to enable everything. Don't forget to enable the subprojects. Make sure you install this BEFORE you install Visual Studio 2005 or 2008.
- TBD
Hi Jim,
ReplyDeleteI came across this blog and am trying to figure out the best way to get a report writer for a simple Office app that I am developing using VS2008 Express. I see you recommend using SQL Server Express with advanced services which includes Reporting services - is this a report writing tool like Access reports (which i am very used and quite like)?
Thanks for the advice.
TimK,
ReplyDeleteSetting up and using the Reporting Services environment is something I've only played with. It's also not supported in VS2008.
If you already know how to use Access, then connect to the SQL Server with Access and use the Access reporting engine.
If you need to programmatically drive the report, then you may be looking at some serious $$$. I have not found an inexpensive reporting tool for SQL Server. The Professional version of VS2008 comes with a stripped down version of Crystal Reports, but I've never tried it. Anyone else have any ideas?
Hi Jim,
ReplyDeleteThanks for your response. Yes Access is something I'm comfortable with and find useful, but it's not the best solution for scalability. So I'm very tempted to go with this, but if the app becomes useful for others (which is possible) then a neater solution would be to use embedded Crystal reports in VS2008.
I may be able to get a license for VS2008 Pro, so I should get to try that option, but can't help think this discussion is one that should have better "out of the box" answers - do we just go from Access to big $$$, what's in between for the mid-range situation such as mine where I would like the scalability of VS WinForms, without the big $$$??