Friday, March 30, 2012
New to Reporting Services
I am new to reporting services of SQL Server. I just read an article about
it. In our organization, we are using Crystal Reports to develop reports for
our system. Backend is of course SQL Server 2000.
Can anyone please guide me that from where I should start to explore this
new technology?
Also is it necessary to use the reporting services of SQL Server 2000 via
VS.NET 2003 or can my VB 6 application develop the same kinds of reoprts?
Thanks in advance.
Syed Hussain Itiba NaqviI would purchase the book "Hitchiker's Guide to SQL Server 2000 Reporting
Services."
You can get a good deal at www.BookPool.com
David
"Syed Hussain Itiba Naqvi" <Syed Hussain Itiba
Naqvi@.discussions.microsoft.com> wrote in message
news:6E7B4BEB-9417-448F-B430-D29411BA114D@.microsoft.com...
> hi
> I am new to reporting services of SQL Server. I just read an article about
> it. In our organization, we are using Crystal Reports to develop reports
> for
> our system. Backend is of course SQL Server 2000.
> Can anyone please guide me that from where I should start to explore this
> new technology?
> Also is it necessary to use the reporting services of SQL Server 2000 via
> VS.NET 2003 or can my VB 6 application develop the same kinds of reoprts?
> Thanks in advance.
> Syed Hussain Itiba Naqvi|||Syed,
Reporting Services comes in two parts.
1. The Server
2. Development Tools.
Ideally The Server components need to be on the same box as a SQL instance
(if you want to run it under the same license - see licensing for further
details) and the same box should have Web Server on also. RS uses the SQL
instance to store it's two new DBs to run the service.
The Development tools can be loaded onto any development machine, but
require VS.NET 2003. Once installed it adds Business Intelligence Projects to
the available solutions, and the Report Designer runs inside of VS.NET IDE
(as does the Crystal designer).
The cool thing about the designer is that you can preview (in like
real-time) the report results from inside the IDE, and also, by deploying it
to your localhost, you can see how the Reporting Server will handle it also,
all prior to deploying it to the 'real' server.
two books to get: Professional SQL Server Reporting Services - WROX and
Step-by-Step SQL Server 2000 Reporting Services - Microsoft. These two books
hold so much instructional info for the beginner.
Also, contact your local Microsoft Area Rep, they will assist you greatly. I
did, and they web-demo'd the technology to myself and my Managers during a
conference call. They have been excellent and very supportive.
Hope this assists,
Tony
"Syed Hussain Itiba Naqvi" wrote:
> hi
> I am new to reporting services of SQL Server. I just read an article about
> it. In our organization, we are using Crystal Reports to develop reports for
> our system. Backend is of course SQL Server 2000.
> Can anyone please guide me that from where I should start to explore this
> new technology?
> Also is it necessary to use the reporting services of SQL Server 2000 via
> VS.NET 2003 or can my VB 6 application develop the same kinds of reoprts?
> Thanks in advance.
> Syed Hussain Itiba Naqvi
New to reporting service
1. Are the report object and report viewer in VS2005(winform) related to those of SQL server reporting service? If yes, what are the relationship?
2. If I just want to create/view report with report viewer of VS2005 in my app which connect to SQL Server Express, do I need reporting service?
3. I can see there are options to install reporting service while installing SQL Server Express(free of charge), can I develop app for my client which use reporting service with SQL Server Express?
Thank a lot!Any idea?|||
Okay, here we go.
Reporting Services
Reporting Services is a component of SQL Server 2000 and SQL Server 2005. Basically the Reporting Services acts as a Report Repository and supports such features as:
* Server-Side Rendering = The server does the work
* Subscriptions - Reports can be generated at scheduled times and be automatically distributed to email or file shares.
* Report Snapshots - Report output can be rendered and stored on the server, for instance a monthly report can have a monthly snapshot. This way you never to need to print and store common reports, the server has the old copy even if the orginial report data is gone.
ReportViewer Control
Okay, so Reporting Services basically rocks because it solved the majority of your reporting issues and comes free with most versions of SQL Server. Now, in with SQL Server 2005 and Visual Studio 2005 there are 2 new controls that make reporting services even better. There is a Windows forms and asp.net ReportViewer control. The control can work in 2 modes, Remote and Local. In Remote mode it can be used to integrate with Reporting Services as users can view reports stored on the server. In local mode (what you want) it can displayed reports that have been embedded within your application. In this mode Reporting Services is not required, which makes it ideal to use with SQL Express. There are only 2 minor disadvantages to running in local mode. The first is that the client computer has to do all the work and report rendering, but its not bad for smaller applications. The second is that the client must have this ReportViewer pack installed. Basically, it contains all of the rendering pieces needed to render a report on the client machine. The great news is that if you deploy your application using the new ClickOnce, you can automatically deploy the ReportViewerPack (also it is very small like only a couple of MB!).
New to reporting service
1. Are the report object and report viewer in VS2005(winform) related to those of SQL server reporting service? If yes, what are the relationship?
2. If I just want to create/view report with report viewer of VS2005 in my app which connect to SQL Server Express, do I need reporting service?
3. I can see there are options to install reporting service while installing SQL Server Express(free of charge), can I develop app for my client which use reporting service with SQL Server Express?
Thank a lot!
Any idea?|||
Okay, here we go.
Reporting Services
Reporting Services is a component of SQL Server 2000 and SQL Server 2005. Basically the Reporting Services acts as a Report Repository and supports such features as:
* Server-Side Rendering = The server does the work
* Subscriptions - Reports can be generated at scheduled times and be automatically distributed to email or file shares.
* Report Snapshots - Report output can be rendered and stored on the server, for instance a monthly report can have a monthly snapshot. This way you never to need to print and store common reports, the server has the old copy even if the orginial report data is gone.
ReportViewer Control
Okay, so Reporting Services basically rocks because it solved the majority of your reporting issues and comes free with most versions of SQL Server. Now, in with SQL Server 2005 and Visual Studio 2005 there are 2 new controls that make reporting services even better. There is a Windows forms and asp.net ReportViewer control. The control can work in 2 modes, Remote and Local. In Remote mode it can be used to integrate with Reporting Services as users can view reports stored on the server. In local mode (what you want) it can displayed reports that have been embedded within your application. In this mode Reporting Services is not required, which makes it ideal to use with SQL Express. There are only 2 minor disadvantages to running in local mode. The first is that the client computer has to do all the work and report rendering, but its not bad for smaller applications. The second is that the client must have this ReportViewer pack installed. Basically, it contains all of the rendering pieces needed to render a report on the client machine. The great news is that if you deploy your application using the new ClickOnce, you can automatically deploy the ReportViewerPack (also it is very small like only a couple of MB!).