I have a SQL Database from which I need to create reports daily, weekly and monthly. I am thinking of Creating Crystal Reports Manually so That I can execute that particular function periodically using a timer. Would this be a good approach or is there any other way in which I can do so?
An example would be greatly appreciated...
Thanks in advance.
I know you asked for Crystal Reports, but assuming you have SQL Server 2008 Reporting Services installed, you can create reports that way and not have to get a second software package.
Both Microsoft Technet ("How to: Schedule Report and Subscription Processing (Reporting Services in SharePoint Integrated Mode") and Code Snippets ("SSRS: Scheduling Reports Using SQL Server Reporting Services 2008") have some examples of scheduling reports.
Related
We are planning on creating reports to be run on the same computer that the database application is running on.
Can you tell me which of these is the best approach? (SQL Server Reporting Services or creating a rdlc ReportViewer report)
Also I tried to locate detailed rdlc ReportViewer report tutorials both in books and online and found none. It's probably because I'm looking in the wrong places.
We are also using VB.Net as the language.
All help will be appreciated.
In a nutshell, .rdlc is the client version. You cannot host these on the report server. These reports do not know how to fetch the data, you MUST get the data yourself and pass it to the report. For this reason, you cannot even preview the report while designing. ReportViewer.ProccessingMode = Local
The .rdl or server reports know how to fetch the data. You configure the datasource and upload them to the report server. Because of this, you can preview the reports while designing them. You can use the web/desktop ReportViewer control to run the reports from inside your app...like a proxy between your application and the report server.ReportViewer.ProccessingMode = Remote
I prefer rdl for any sql datasource, but rdlc is also good for cases where your datasource is very complex or can only be built through the application code. I think there might be ways to configure an object datasource for rdl but I haven't looked into that yet.
I'm .net developer and have no experience with Visual Foxpro. I have to migrate old system use Visual Fox upto Asp.Net. The old system already use SQL Server to store data, but there are many reports must be migrated, if i can connect to the processed report data. It's seem to be save lot of my effort.
Pls, give me a suggest for this situation.
http://www.vfpconversion.com/Vfp2NetReports.aspx#4
they have a tool that converts foxpro reports to ssrs or crystal reports
There's no magic bullet I'm afraid. You will have to re-do them using, for example, SQL Server Reporting Services.
I am in the process of evaluiting Ad-Hoc reporting tool on top SQL Server 2008 R2. I would like to know what are the limitations around the Report Builder 3.0 which comes with SQL server.
What reports we can do in VS 2008 with BIDS and which we can not do in Report Builder 3.0 We are trying to answer what can be done what can be done with Report Builder.
Please share your real time experiance
We went through this same evaluation not that long ago. Basically BIDS and Report Builder 2/3 allow you to do the same thing. Report Builder is for those users who want to create or modify their own reports without needing to install BIDS. Report Builder has a Microsoft Office look and feel. It has the ribbon controls similar to Excel and Word. The same .RDL or .RDLC is generated by both. However, Report Builder 3 only targets SSRS 2008 R2. The .RDL format has changed for SSRS 2008 R2.
Either way the report can be deployed to an SSRS server, Sharepoint or the Microsoft Report Viewer (for .RDLC files).
As you may or may not know, there is no BIDS for Visual Studio 2010 (yet). If you want to use BIDS, you'll need to use VS 2008, which targets SQL Server 2008.
I think for a Power User who already has gone through tools like Cognos and Business Objects, the reprot builder 3.0 seems to lack lot of features while reporting against the cube. Here are the main.
I cannot create a variable which I can use in multiple tables in the report. I thought I could use "calculated member" but it does not let me use any kind of aggregate function on any of the objects against the cube as it treats everything as aggregate objects.
I cannot use a simple "OR" statement in the query filter.
Power user while building the report need to always pay attention to "row group", which I think is frustrating. In other tools the measure or fact groups it only groups by the dimension u have in the table.
Row limitations while exporting to excel.
Friends I have a problem with SQL Server Reporting Services ..!!!
I have some reports that show no data, the reports are on a separate server from the server that contains the database, the Data Sources of the reports is well configured.
Stored procedures are executed while the server (display data)
users have the necessary permissions.
What is the problem ..? Thanks
Also, look at reporting services logs. they all end in .log, and begin with Report. I forget where they are on the server, but am pretty sure they are under the program files directory for mssql, just as you would find logs for sql server.
It sounds as though the definition of your data sources in production may be different from that in development. Have you tried redeploying your data sources?
You should be able to access the Database on a server separate from the report server. That all sounds good. When you run the Reports in Visual Studio Preview mode....do you see any data?
I want to send SQL server Dashboard & Health Report to my client on daily basis, so is there ant script / tool to generate report for sql server 2005.
You can download the Performance Dashboard reports and then edit them for use inside reporting services manually, or use them as they are provided.
http://www.microsoft.com/downloads/details.aspx?FamilyId=1d3a4a0d-7e0c-4730-8204-e419218c1efc&displaylang=en
These install the reporting services RDL files to c:\program files\Microsoft SQL Server\90\Tools\Performance Dashboard, and there is a setup.sql script that contains the actual TSQL objects that are used by the reports. This can easily be the basis for what you are trying to do, and the RDL files can be imported into Reporting Services to allow subscriptions to automate delivery. There is a known issue with one of them where a datediff using milliseconds overflows the int datatype but you can find a fix to this on Robs blog post:
http://blogs.technet.com/rob/archive/2009/02/18/performance-dashboard-reports-for-sql-server-2008.aspx
You don't really have to do a lot of excess work reinventing the wheel if you start off with the basic Performance Dashboard reports provided by Microsoft with SQL Server 2005 SP2 Feature Pack and then doing small customizations as necessary to meet your needs.
This sounds like a perfect job for SQL Server Reporting Services.
As to the queries that you need, that will all depend on what you want to show.