How to run a database report?

Is there anyone who knows how to create a database report in SQL server 2000 after we run queries?
Thanks for helpto create something pretty you need to use a reporting tool like sql reporting services or crystal or access or you can DIY with a programming language like ASP.|||Is there anyone who knows how to create a database report in SQL server 2000 after we run queries?
Thanks for help

There are really a boat load of different ways to do different things...maybe if you clue us in on what you want to do we could probably suggest something

M$ Access best feature, in my opinion, is reporting.|||M$ Access best feature, in my opinion, is reporting.Could not agree more wholeheartedly or with greater vigour.|||to create something pretty you need to use a reporting tool like sql reporting services or crystal or access or you can DIY with a programming language like ASP.

I agree with you. In your opinion, SQL reporting services is a good tool to create a database report in SQL queries compared to other ones?
Thanks|||the setup for SQL Server Reporting Services 2000 can be an adventure. I have set it up on a few client sites and done a a couple of setups in house and it never goes right the first time and the problem with the setup has been different everytime.

However, the one time I setup SQL Reporting Services 2005 all I had to do was hit a checkbox during the SQL Server 2005 setup and everything worked out of the box. I was shocked.

The other upside to SQL RS, is that it will not cost you anything if it is installed on the same machine as SQL Server. The drawbacks to this are you will have IIS on your DB box and it violates the best practice of having your application code and your DB server on different machine.|||the setup for SQL Server Reporting Services 2000 can be an adventure. I have set it up on a few client sites and done a a couple of setups in house and it never goes right the first time and the problem with the setup has been different everytime.

However, the one time I setup SQL Reporting Services 2005 all I had to do was hit a checkbox during the SQL Server 2005 setup and everything worked out of the box. I was shocked.

The other upside to SQL RS, is that it will not cost you anything if it is installed on the same machine as SQL Server. The drawbacks to this are you will have IIS on your DB box and it violates the best practice of having your application code and your DB server on different machine.

Seems i've been lucky with Reporting services. Istruggled in first installation only. For other attempts i had a cakewalk...|||But doesn't every business person want their reports in Excel?|||Seems i've been lucky with Reporting services. Istruggled in first installation only. For other attempts i had a cakewalk...

do deal with one internal homogeneous envrionment or do you deploy to various customers where things are different everytime?|||Not sure if you care, but RS sucks if you have to generate localized reports, even on 2005.|||I have not written a "report" in a few years. I have report writers for that. All I do these days is fix the nastiest problems.|||I had to maintain all the reports in SSMS until yukon was released, so I know painfully well that RS 2005 doesn't support localization :)

I don't write reports anymore either thankfully. Those rdl files were pretty nasty looking!|||But doesn't every business person want their reports in Excel?RS will gleefully deliver reports as XLS files.

-PatP|||Not sure if you care, but RS sucks if you have to generate localized reports, even on 2005.Interesting point of view, can you elaborate a bit? I agree that RS can't deal well with poorly constructed queries that pre-localize the data, but I've never had a problem with simply retrieving the data via a query then allowing RS to present it. I've actually found the RS makes it much easier for me to deliver localized reports (with the exception of one other enterprise grade reporting tool, with an enterprise grade price tag).

-PatP|||are you saying you are able to build a single report and have it render properly in multiple languages?

I am pretty sure that's not possible with the WinForms ReportViewer (which is what I had to use, the one in the Microsoft.Reporting.Winforms namespace). RDL files don't use resx files to store strings like a regular localized winform would, so they can't be localized easily.

It may be different if you host your reports on a RS server, which it sounds like you were doing.

I couldn't do that because SSMS needs to carry its reports around with it, and can't depend on a RS instance being installed somewhere. So maybe it's not that RS itself sucks, it's that Microsoft.Reporting.Winforms.ReportViewer sucks (at least when it comes to localization. otherwise it's ok) :)|||This is my first time to try to create the database report (the sample posted on web site) but I had the problem to deploy the report, when I click F5, it showed the error messages:
"No Report Server was found at http://localhost/ReportServerDB"

even though I already registered the ASP.net and checked IIS to see if it is running.
Also, after installation I clicked Report Manager I saw the error messages of this page like this:

Server Error in '/Reports' Application.
--------------------

Access to the path "C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportManager\bin" is denied.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.UnauthorizedAccessException: Access to the path "C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportManager\bin" is denied.

ASP.NET is not authorized to access the requested resource. Consider granting access rights to the resource to the ASP.NET request identity. ASP.NET has a base process identity (typically {MACHINE}\ASPNET on IIS 5 or Network Service on IIS 6) that is used if the application is not impersonating. If the application is impersonating via <identity impersonate="true"/>, the identity will be the anonymous user (typically IUSR_MACHINENAME) or the authenticated request user.

To grant ASP.NET write access to a file, right-click the file in Explorer, choose "Properties" and select the Security tab. Click "Add" to add the appropriate user or group. Highlight the ASP.NET account, and check the boxes for the desired access.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[UnauthorizedAccessException: Access to the path "C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportManager\bin" is denied.]
System.IO.__Error.WinIOError(Int32 errorCode, String str) +393
System.IO.Directory.InternalGetFileDirectoryNames( String fullPath, String userPath, Boolean file) +229
System.IO.Directory.InternalGetDirectories(String path, String userPath, String searchPattern) +24
System.IO.Directory.GetDirectories(String path, String searchPattern) +477
Microsoft.ReportingServices.Diagnostics.Localizati on.GetInstalledCultures()
Microsoft.ReportingServices.Diagnostics.Localizati on..cctor()

[TypeInitializationException: The type initializer for "Microsoft.ReportingServices.Diagnostics.Localizati on" threw an exception.]
Microsoft.ReportingServices.Diagnostics.Localizati on.SetCultureFromPriorityList(String[] localeList) +0
Microsoft.ReportingServices.UI.GlobalApp.Applicati on_BeginRequest(Object sender, EventArgs e)
System.Web.SyncEventExecutionStep.System.Web.HttpA pplication+IExecutionStep.Execute() +60
System.Web.HttpApplication.ExecuteStep(IExecutionS tep step, Boolean& completedSynchronously) +87

Please show me how to solve the problem.
Thank you for your time.|||this looks like a permissions issue.

when you log into http://<yourservername>/Reports on the properties tab do you see your windows user name or a group you are a part of? Depending on how this is setup will determine what IIS settings you will need.|||this looks like a permissions issue.

when you log into http://<yourservername>/Reports on the properties tab do you see your windows user name or a group you are a part of? Depending on how this is setup will determine what IIS settings you will need.

No, I don't see any user name or group on the properties tab.