Menus

Saturday, December 22, 2012

Joins Using LINQ in C#

In this article we will see how to perform join operation using LINQ queries. I have created two tables in database named 'Candidate'. The first table name is Employee. the second table name is Student. I have used LINQ to SQL to communicate with database.

The data context name created for LINQ To SQL is: DataClasses1DataContext.

The Design Mode of Employee Table looks like this:

Employee Table.png

The Design Mode of Student Table looks like this:

Student Table.png


The Complete Code for WebForm1.aspx looks like this:

<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="WebForm1.aspx.cs" Inherits="JOINS_LINQ.WebForm1" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <html xmlns="http://www.w3.org/1999/xhtml">
 <head id="Head1" runat="server">
    <title></title>
    <style type="text/css">
        .gridstyle
        {
            float: left;
        }
    </style>
 </head>
<body>
    <form id="form1" runat="server">
    <div>
        <center>
            <asp:Label ID="Label2" runat="server" Text="Left Outer Join" Font-Bold="true" CssClass="gridstyle"></asp:Label><br />
            <br />
            <asp:GridView ID="GridView1" runat="server" CssClass="gridstyle" BackColor="White"
                BorderColor="#3366CC" BorderStyle="None" BorderWidth="1px" CellPadding="4" OnLoad="PageLoad">
                <FooterStyle BackColor="#99CCCC" ForeColor="#003399" />
                <HeaderStyle BackColor="#003399" Font-Bold="True" ForeColor="#CCCCFF" />
                <PagerStyle BackColor="#99CCCC" ForeColor="#003399" HorizontalAlign="Left" />
                <RowStyle BackColor="White" ForeColor="#003399" />
                <SelectedRowStyle BackColor="#009999" Font-Bold="True" ForeColor="#CCFF99" />
                <SortedAscendingCellStyle BackColor="#EDF6F6" />
                <SortedAscendingHeaderStyle BackColor="#0D4AC4" />
                <SortedDescendingCellStyle BackColor="#D6DFDF" />
                <SortedDescendingHeaderStyle BackColor="#002876" />
            </asp:GridView>
        </center>
        <br />
        <br />
        <center>
            <asp:Label ID="Label1" runat="server" Text="Right Outer Join" Font-Bold="true" CssClass="gridstyle"></asp:Label><br />
            <br />
            <asp:GridView ID="GridView2" runat="server" BackColor="White" CssClass="gridstyle"
                BorderColor="#3366CC" BorderStyle="None" BorderWidth="1px" CellPadding="4" OnLoad="PageLoad">
                <FooterStyle BackColor="#99CCCC" ForeColor="#003399" />
                <HeaderStyle BackColor="#003399" Font-Bold="True" ForeColor="#CCCCFF" />
                <PagerStyle BackColor="#99CCCC" ForeColor="#003399" HorizontalAlign="Left" />
                <RowStyle BackColor="White" ForeColor="#003399" />
                <SelectedRowStyle BackColor="#009999" Font-Bold="True" ForeColor="#CCFF99" />
                <SortedAscendingCellStyle BackColor="#EDF6F6" />
                <SortedAscendingHeaderStyle BackColor="#0D4AC4" />
                <SortedDescendingCellStyle BackColor="#D6DFDF" />
                <SortedDescendingHeaderStyle BackColor="#002876" />
            </asp:GridView>
        </center>
        <center>
            <asp:Label ID="Label3" runat="server" Text="Concat Operation" Font-Bold="true" CssClass="gridstyle"></asp:Label><br />
            <br />
            <asp:GridView ID="GridView3" runat="server" BackColor="White" CssClass="gridstyle"
                BorderColor="#3366CC" BorderStyle="None" BorderWidth="1px" CellPadding="4" OnLoad="PageLoad">
                <FooterStyle BackColor="#99CCCC" ForeColor="#003399" />
                <HeaderStyle BackColor="#003399" Font-Bold="True" ForeColor="#CCCCFF" />
                <PagerStyle BackColor="#99CCCC" ForeColor="#003399" HorizontalAlign="Left" />
                <RowStyle BackColor="White" ForeColor="#003399" />
                <SelectedRowStyle BackColor="#009999" Font-Bold="True" ForeColor="#CCFF99" />
                <SortedAscendingCellStyle BackColor="#EDF6F6" />
                <SortedAscendingHeaderStyle BackColor="#0D4AC4" />
                <SortedDescendingCellStyle BackColor="#D6DFDF" />
                <SortedDescendingHeaderStyle BackColor="#002876" />
            </asp:GridView>
        </center>
    </div>
    </form>
 </body>
</html>

Code Toolbox Requirements:
  • 3 Labels and 3 Grid Views.
The Complete Code for WebForm1.aspx.cs looks like this:

using System;
 using System.Linq;
namespace JOINS_LINQ
{
    public partial class WebForm1 : System.Web.UI.Page
    {
        protected void PageLoad(object sender, EventArgs e)
        {
            LeftOuterJoin();
            RightOuterJoin();
            Concat();
        }
        public void LeftOuterJoin()
        {
            var db = new DataClasses1DataContext();
            var query = from p in db.Employees
                        join r in db.Students
                        on p.EmpId equals r.PersonId into temp
                        from t in temp.DefaultIfEmpty()
                        select new
                        {
                            Designation = p.EmpDesignation,
                            EmployeeName = p.EmpName,
                            FirstName = t.FirstName,
                            LastName = t.LastName,
                            Age = t.Age
                        };
            GridView1.DataSource = query;
            GridView1.DataBind();
        }
        protected void Concat()
        {
            var db = new DataClasses1DataContext();
            var query1 = from r in db.Students select r.FirstName;
            var query2 = from p in db.Employees select p.EmpName;
            var concatquery = query1.Concat(query2);
            GridView3.DataSource = concatquery;
            GridView3.DataBind();
        }
        protected void RightOuterJoin()
        {
            var db = new DataClasses1DataContext();
            var query = from r in db.Students
                        join p in db.Employees
                        on r.PersonId equals p.EmpId into temp
                        from t in temp.DefaultIfEmpty()
                        select new
                        {
                            FirstName = r.FirstName,
                            LastName = r.LastName,
                            Age = r.Age,
                            Designation = t.EmpDesignation,
                            EmployeeName = t.EmpName
                        };
            GridView2.DataSource = query;
            GridView2.DataBind();
        }
    }
}

The Output of the application looks like this:

LINQ Joins output.png
Posted by at No comments:
Labels:

Sample Example of RANKING Functions – ROW_NUMBER, RANK, DENSE_RANK, NTILE

SQL Server 2005 has total of 4 ranking function. Ranking functions return a ranking value for each row in a partition. All the ranking functions are non-deterministic.
ROW_NUMBER () OVER ([<partition_by_clause>] <order_by_clause>)
Returns the sequential number of a row within a partition of a result set, starting at 1 for the first row in each partition.
RANK () OVER ([<partition_by_clause>] <order_by_clause>)
Returns the rank of each row within the partition of a result set.
DENSE_RANK () OVER ([<partition_by_clause>] <order_by_clause>)
Returns the rank of rows within the partition of a result set, without any gaps in the ranking.
NTILE (integer_expression) OVER ([<partition_by_clause>] <order_by_clause>)
Distributes the rows in an ordered partition into a specified number of groups.
All the above definition and syntax are taken from BOL. It is difficult to explain above function anything else than what they are explained in BOL. Following example is excellent example from BOL again. This function explains usage of all the four function together in one query.
USE AdventureWorks;
GO
SELECT c.FirstName, c.LastName
,ROW_NUMBER() OVER (
ORDER BY a.PostalCode) AS 'Row Number'
,RANK() OVER (
ORDER BY a.PostalCode) AS 'Rank'
,DENSE_RANK() OVER (
ORDER BY a.PostalCode) AS 'Dense Rank'
,NTILE(4) OVER (
ORDER BY a.PostalCode) AS 'Quartile'
,s.SalesYTD, a.PostalCode
FROM Sales.SalesPerson s
INNER JOIN Person.Contact c
ON s.SalesPersonID = c.ContactID
INNER JOIN Person.Address a
ON a.AddressID = c.ContactID
WHERE TerritoryID IS NOT NULL
AND SalesYTD <> ;
Resultset:
Posted by at No comments:
Labels:

Query to Find Column From All Tables of Database

How many tables in database AdventureWorks have column name like ‘EmployeeID’?
USE AdventureWorks
GO
SELECT t.name AS table_name,
SCHEMA_NAME(schema_id) AS schema_name,
c.name AS column_name
FROM sys.tables AS t
INNER JOIN sys.columns c ON t.OBJECT_ID = c.OBJECT_ID
WHERE c.name LIKE '%EmployeeID%'
ORDER BY schema_name, table_name;
In above query replace EmployeeID with any other column name.
SELECT t.name AS table_name,
SCHEMA_NAME(schema_id) AS schema_name,
c.name AS column_name
FROM sys.tables AS t
INNER JOIN sys.columns c ON t.OBJECT_ID = c.OBJECT_ID
ORDER BY schema_name, table_name;
Posted by at No comments:
Labels:

SQL Server 2005 Reporting Services Tutorial

For a relatively new product, Reporting Services has a quite complex architecture. The full Reporting Services architecture includes development tools, administration tools, and report viewers. There are a number of ways to get to Reporting Services programmatically, including SOAP and WMI interfaces.
Figure 18-1 shows a simplified diagram of the main Reporting Services components that we'll be using in this chapter.
Figure 18-1: Report Server architecture
Figure 18-1: Report Server architecture
In this chapter you'll learn about these components:
  • Report Server is the core engine that drives Reporting Services.
  • Report Manager is a Web-based administrative interface for Reporting Services.
  • Report Designer is a developer tool for building complex reports.
  • Report Builder is a simplified end-user tool for building reports.
  • The Report Server database stores report definitions. Reports themselves can make use of data from many different data sources.

SSRS Tutorial: Using Report Designer

Reporting Services includes two tools for creating reports:
  • Report Designer can create reports of any complexity that Reporting Services supports, but requires you to understand the structure of your data and to be able to navigate the Visual Studio user interface.
  • Report Builder provides a simpler user interface for creating ad hoc reports, directed primarily at business users rather than developers. Report Builder requires a developer or administrator to set up a data model before end users can create reports.
We'll start our tour of Reporting Services with Report Designer. Report Designer runs inside the Business Intelligence Development Studio shell, and offers several ways to create reports. You can either use the Report Wizard to quickly create a report, or you can use a set of design tools to build a report from scratch. You can also use the design tools to modify a report created with the wizard.
Using the Report Wizard
The easiest way to create a report in Report Designer is to use the Report Wizard. Like all wizards, the Report Wizard walks you through the process in step-by-step fashion. You can make the following choices in the wizard:
  • The data source to use
  • The query to use to retrieve data
  • Whether to use a tabular or matrix layout for the report
  • How to group the retrieved data
  • What visual style to use
  • Where to deploy the finished report
Try It!
To create a simple report using the Report Wizard, follow these steps:
  1. Launch Business Intelligence Development Studio.
  2. Select File > New >Project.
  3. Select the Business Intelligence Projects project type.
  4. Select the Report Server Project Wizard template.
  5. Name the new report ProductReport1 and pick a convenient location to save it in.
  6. Click OK.
  7. Read the first page of the Report Wizard and click Next.
  8. Name the new data source AdventureWorksDS.
  9. Click the Edit button.
  10. Log on to your test server.
  11. Select the AdventureWorks database.
  12. Click OK.
  13. Click the Credentials button.
  14. Select Use Windows Authentication.
  15. Click OK.
  16. Check the Make This a Shared Data Source checkbox. This will make this particular data source available to other Reporting Services applications in the future.
  17. Click Next.
  18. Click the Query Builder button.
  19. If the full query designer interface does not display by default, click the query designer toolbar button at the far left end of the toolbar. Figure 18-2 shows the full query designer interface.
    Figure 18-2: Query Builder
    Figure 18-2: Query Builder 
  20. Click the Add Table toolbar button.
  21. Select the Product table and click Add.
  22. Click Close.
  23. Check the Name, ProductNumber, Color, and ListPrice columns.
  24. Click OK.
  25. Click Next.
  26. Select the Tabular layout and click Next.
  27. Move the Color column to the Group area, and the other three columns to the Detail area, as shown in Figure 18-3.
    Figure18-3: Grouping columns in the report
    Figure18-3: Grouping columns in the report
  28. Click Next.
  29. Select the Stepped layout and click Next.
  30. Select the Ocean style and click Next.
  31. Accept the default deployment location and click Next.
  32. Name the report ProductReport1.
  33. Check the Preview Report checkbox.
  34. Click Finish.
Figure 18-4 shows the finished report, open in Report Designer.
Figure 18-4: Report created by the Report Wizard
Figure 18-4: Report created by the Report Wizard
Figure 18-4 shows the main features of Report Designer:
  • The Datasets window shows the data that is available to the report.
  • The main design window lets you view the report itself. You can see a preview of the report, work with the report in a layout designer, or work with the query that returns the data for the report.
  • The Solution Explorer, Output, and Properties windows are the standard Visual Studio windows.
Modifying a Report
Now that you've created a report with the Report Wizard, you can modify it with the Report Designer. If you've used any sort of visual report design tool in the past, you should have no problem making changes here. Among the possibilities here:
  • You can change the available data or the sort order for the report by modifying the query on the Data tab.
  • You can resize or rearrange controls on the Layout tab.
  • You can use the Properties window to change properties of individual controls including their font, alignment, colors, and so on.
Try It!
To modify the report that you just created, follow these steps:
  1. Click the Data tab to view the query for the report.
  2. Select a Descending sort type for the ListPrice column.
  3. Click the Layout tab.
  4. Click in the textbox at the top of the report, where the report name is displayed.
  5. Use the Properties window to change the Value property of this control to Products By Color.
  6. Click on the header for the Product column.
  7. Place the cursor between the Name and Product Number columns to display a double-headed arrow. Hold down the mouse button and drag the cursor to the right to widen the Name column.
  8. Place the cursor between the Product Number and ListPrice columns to display a double-headed arrow. Hold down the mouse button and drag the cursor to the right to widen the Product Number column.
  9. Click on the Preview tab to view the modified report, as shown in Figure 18-5.
    Figure 18-5: Modified product report
    Figure 18-5: Modified product report
Designing a Report From Scratch
You can also use Report Designer to build your own reports starting from scratch. In general, you'll follow these steps to create a report:
  1. Create a Report project in Business Intelligence Design Studio.
  2. Associate one or more datasets with the report.
  3. Create a query from the dataset.
  4. Build the report layout.
Try It!
To create a fresh report in Report Designer, follow these steps:
  1. Select File > Close Solution to close the existing report.
  2. Select File > New > Project.
  3. Select the Business Intelligence Projects project type.
  4. Select the Report Server Project template.
  5. Name the new report ProductReport2 and pick a convenient location to save it in.
  6. Right-click on the Reports node in Solution Explorer and select Add „ New Item.
  7. Select the Report template.
  8. Name the new report ProductReport2.rdl and click Add.
  9. Select the Data tab in the Report Designer.
  10. Click the Datasets dropdown and select <New Dataset> to open the Data Source dialog box.
  11. Name the new Data Source AdventureWorksDS.
  12. Click the Edit button.
  13. Connect to your test server and choose the AdventureWorks database.
  14. Click OK.
  15. Click OK again to create the data source.
  16. Click the Query Designer toolbar button inside the Data tab to display the full query designer user interface.
  17. Click the Add Table button.
  18. Select the Location table.
  19. Click Add.
  20. Click Close.
  21. Check the boxes for the Name and CostRate columns.
  22. Sort the dataset in ascending order by Name.
  23. Click the Layout tab to show the blank report layout.
  24. Hover your mouse over the toolbox tab to display the available controls for the report.
  25. Double-click the List control.
  26. Expand the List control to the width of the report.
  27. Expand the dataset in the Datasets window to show the column names.
  28. Drag the Name and CostRate columns from the Datasets window and drop them in the List control. Expand them horizontally until each takes up about half of the List control. Figure 18-6 shows the report in layout view. Figure 18-6: Designing a report from scratch
    Figure 18-6: Designing a report from scratch
  29. Select the Preview tab to see the report with data.

SSRS Tutorial: Publishing a Report

Creating reports in Business Intelligence Development Studio is good for developers, but it doesn't help users at all. In order for the reports you build to be available to others, you must publish them to your Reporting Services server. To publish a report, you can use the Build and Deploy menu items in Business Intelligence Development Studio. Before you do this, you need to check the project's configuration to make sure that you've selected an appropriate server for the deployment.
Try It!
To publish a report, follow these steps:
  1. Close the ProductReport2 project.
  2. Open the ProductReport1 project.
  3. Select Project > ProductReport1 Properties.
  4. Click the Configuration Manager button.
  5. Set the Active Solution Configuration to Production.
  6. Make sure the Configuration is set to Production and both the Build and Deploy checkboxes are checked. Figure 18-7 shows the Configuration Manager.
    Figure 18-7: Setting the active configuration
    Figure 18-7: Setting the active configuration
  7. Click Close.
  8. Fill in the URL for your Report Server. If you're developing on the same computer where Reporting Services is installed, and you installed in the default configuration, this will be http://localhost/ReportServer. Figure 18-8 shows the completed Property Pages.
    Figure 18-8: Setting report project properties
    Figure 18-8: Setting report project properties
  9. Click OK.
  10. Select Build > Deploy ProductReport1. The Output Window will track the progress of BIDS in deploying your report, as shown in Figure 18-9. Depending on the speed of your computer, building the report may take some time.
    Figure 18-9: Deploying a report
    Figure 18-9: Deploying a report
  11. Launch SQL Server Management Studio.
  12. Click the Connect button in Object Explorer and select Reporting Services.
  13. Connect to your test server.
  14. Expand the Home node in the Object Explorer tree to find the ProductReport1 project.
  15. Expand the ProductReport1 project to find the ProductReport1 report.
  16. Right-click on the report and select View Report.
  17. If prompted, supply your username and password. The report will open in your Web browser.

SSRS Tutorial: Using Report Builder

Report Designer gives you one way to create reports for Reporting Services, but it's not the only way. SQL Server 2005 also includes a tool directed at end users named Report Builder. Unlike Report Designer, which is aimed at Developers, Report Builder presents a simplified view of the report-building process and is intended for business analysts and other end users.
Building a Data Model
Report Builder doesn't let end users explore all of a SQL Server database. Instead, it depends on a data model: a preselected group of tables and relationships that a developer has identified as suitable for end-user reporting. To build a data model, you use Business Intelligence Development Studio. Data models contain three things:
  • Data Sources connect the data model to actual data.
  • Data Source Views draw data from data sources.
  • Report Models contain entities that end users can use on reports.
Try It!
To create a data model, follow these steps:
  1. If it's not already open, launch Business Intelligence Development Studio
  2. Select File > New > Project.
  3. Select the Business Intelligence Projects project type.
  4. Select the Report Model Project template.
  5. Name the new project AWSales and save it in a convenient location.
  6. Click OK.
  7. Right-click on Data Sources in Solution Explorer and select Add New Data Source.
  8. Read the first page of the Add New Data Source Wizard and click Next.
  9. Click New.
  10. In the Connection Manager dialog box connect to the AdventureWorks database on your test server and click OK.
  11. Click Next.
  12. Name the new data source AdventureWorks and click Finish.
  13. Right-click on Data Source Views in Solution Explorer and select Add New Data Source View.
  14. Read the first page of the Add New Data Source View Wizard and click Next.
  15. Select the AdventureWorks data source and click Next.
  16. Select the Production.Product table and click the > button to move it to the Included Objects listbox.
  17. Select the Sales.SalesOrderDetail table and click the > button to move it to the Included Objects listbox.
  18. Click the Add Related Tables button.
  19. Click Next.
  20. Click Finish.
  21. Right-click on Report Models in Solution Explorer and select Add New Report Model.
  22. Read the first page of the Report Model Wizard and click Next.
  23. Select the Adventure Works data source view and click Next.
  24. Keep the default rules selection, as shown in Figure 18-10, and click Next.
    Figure 18-10: Creating entities for end-user reporting
    Figure 18-10: Creating entities for end-user reporting
  25. Choose the Update Statistics option and click Next.
  26. Click Run to complete the wizard.
  27. Click Finish. If you get a warning that a file was modified outside the source editor, click Yes.
  28. Select Build „ Deploy AWSales to deploy the report model to the local Reporting Services server.
Building a Report Report Builder itself is a ClickOnce Windows Forms application. That means that end users install it from the browser, but once installed it's not a browser-based application. To get started with Report Builder, browse to your Reporting Services home page. Typically, this will have a URL such as http://ServerName/Reports (or http://localhost/Reports if you're running the browser on the same box with SQL Server 2005 itself). Figure 18-11 shows the Reporting Services home page.
Figure 18-11: Reporting Services home page
Figure 18-11: Reporting Services home page
To install Report Builder, click the Report Builder link in the home page menu bar. Report Builder will automatically load up all of the available report models and wait for you to choose one to build a report from.
Try It!
  1. Open a browser window and navigate to http://localhost/Reports (or to the appropriate Report Server URL if you're not working on the report server).
  2. Click the Report Builder link.
  3. Depending on your operating system, you may have to confirm that you want to run the application.
  4. After Report Builder is installed, select the AdventureWorks report model and the table report layout. Click OK. Figure 18-12 shows the new blank report that Report Builder will create. Figure 18-12: New report in Report Builder
    Figure 18-12: New report in Report Builder
    The Explorer window to the left of the design surface shows all of the tables in the report model. Beneath that, the Fields window shows the entities in the currently-selected table. Note that not everything in this window is a column in the table: the report model also contains aggregate entities such as Total Safety Stock Level and automatically calculated fields.

  5. Select the Product table.
  6. Drag the Name field and drop it in the area labeled Drag and Drop Column Fields.
  7. Click on Special Offer Products in the Explorer window to show related child tables.
  8. Click on Sales Order Details.
  9. Drag the Total Order Qty field and drop it to the right of the Name field.
  10. Click where it says Click to Add Title and type Product Sales.
  11. Click the Run Report button to produce the report shown in Figure 12-13.
    Figure 18-13: Report in Report Builder
    Figure 18-13: Report in Report Builder 
  12. Click the Sort and Group toolbar button.
  13. Select to sort by Total Order Qty descending.
  14. Click OK.
  15. Select File > Save.
  16. Name the new report Product Sales.
  17. Click Save. This will publish the report back to the Reporting Services server that you originally downloaded Report Builder from.

SSRS Tutorial: Using Report Manager

The Web home page for Reporting Services provides a complete interface for managing reports (as well as other objects such as data sources and models) after they are created. This interface, known as Report Manager, is intended primarily for database administrators, but as a developer you should know about its capabilities for managing and modifying reports.
When you click on a report in Report Manager, you'll see the report's data, as shown in Figure 18-14.
Figure 18-14: Report in Report Manager
Figure 18-14: Report in Report Manager
Note that reports in Report Manager open in a tabbed interface. The four tabs allow you to perform various functions:
  • View allows you to see the current data in the report.
  • Properties lets you adjust such things as the report's name, data source, security credentials, caching, and end-user security.
  • History shows you saved snapshots of the report.
  • Subscriptions lets you create subscriptions to the report. Subscriptions allow you to set up periodic delivery of reports to end users by e-mail or file share.

SSRS Tutorial: Exercises

Use Report Builder to create a report from the AdventureWorks data model showing the minimum and maximum order quantity for orders taken by each salesperson in the company. You'll find the necessary data in the SalesOrderHeader and SalesOrderDetail tables.
Solutions to Exercises
  1. Open a browser window and navigate to http://localhost/Reports (or to the appropriate Report Server URL if you're not working on the report server).
  2. Click the Report Builder link.
  3. Select the AdventureWorks report model and the table report layout.
  4. Click OK.
  5. Select the Sales Order Header table.
  6. Drag the Sales Person ID field and drop it in the area labeled Drag and Drop Column Fields.
  7. Click on Sales Order Details in the Explorer window.
  8. Expand the Total Order Qty field in the Fields window to show the alternative fields beneath it.
  9. Drag the Min Order Qty field and drop it to the right of the Name field.
  10. Drag the Max Order Qty field and drop it to the right of the Min Order Qty field.
  11. Click where it says Click to Add Title and type Sales Performance.
  12. Click the Run Report button to produce the report shown in Figure 18-15.
Figure 18-15: Sales performance report
Figure 18-15: Sales performance report
Posted by at No comments:
Labels:

Installing and Configuring SQL Server 2005 Reporting Services

For the last one year I was working on reporting services and as project is closed, now its time to do some documentation and knowledge sharing :). So I started to prepare a doument which can be used as a starting point for future projects. In this post I will be posting its first part - Installing and Configuring SQL Server 2005 Reporting Services.
Its my first technical post and your valuable feedback will surely be very helpful and appreciated.

1       System Requirements

 
    1. Windows Server 2003 / Windows 2000 Server/ Windows vista / Windows XP/ Windows Server 2008
    2. IIS 5.0 or later is required for Microsoft SQL Server 2005 Reporting Services (SSRS) installations.
    3. ASP.NET 2.0 is required for Reporting Services. When installing Reporting Services, SQL Server Setup will enable ASP.NET if it is not already enabled.
    4. SQL server 2005 with SP1(In case you need to reinstall reporting services its advised to reinstall full SQL server rather then just reporting services).
    5. SQL Server Setup requires Microsoft Windows Installer 3.1 or later and Microsoft Data Access Components (MDAC) 2.8 SP1 or later. You can download MDAC 2.8 SP1 from this Microsoft Web site.
For detailed requirements see: Hardware and Software Requirements for Installing SQL Server 2005 -
http://msdn.microsoft.com/en-us/library/ms143506.aspx

2       Install the SQL server reporting services

http://msdn.microsoft.com/en-us/library/aa545330.aspx

3       Post Installation Configuration

On the report server computer, follow these steps after setup is finished to complete the deployment:
  1. Open port 80 in Microsoft Windows Firewall to enable incoming requests over port 80. If you installed Reporting Services on Microsoft Windows XP with Service Pack 2 or Windows Server 2003 with Service Pack, HTTP requests over port 80 are blocked by default. To open port 80, do the following:
    1. Click Start, point to Control Panel, click Windows Firewall, click Exceptions, and then click Add Port.
    2. In Name, type Web Server (TCP 80).
    3. In Port number, type 80.
    4. For the protocol, select TCP.
    5. Click OK.
  2. Modify Windows Firewall settings to enable remote administration.
a.    Log on as a local administrator to the computer for which you want to enable remote administration.b.    Open a command line window, and then run the following command: netsh.exe firewall set service type=REMOTEADMIN mode=ENABLE scope=ALL c.    Verify that remote administration is enabled. You can run the following command to show the status: netsh.exe firewall show state 
  1. Add InetInfo.exe to the Windows Firewall Exception List
    1. Click Start, point to Control Panel, and click Windows Firewall.
    2. Click Exceptions.
    3. Click Add Program.
    4. Click Browse.
    5. Select %windir%\system32\inetsrv\inetinfo.exe
    6. Click Change Scope to set the scope.
    7. Click OK.
    8. Reboot the computer.
  2. Enable remote connections to the SQL Server instance that hosts the report server database
    1. Click Start, point to Programs, point to Microsoft SQL Server 2005, point to Configuration Tools, and click SQL Server Surface Area Configuration Tool.
    2. Click Surface Area Configuration for Services and Connections.
    3. Open the folder for the SQL Server instance that hosts the report server databases.
    4. Click Remote Connections.
    5. Click Local and Remote Connections.
    6. Click Using both TCP/IP and named pipes.
    7. Click OK, and then restart the service.
  3. Run the Reporting Services Configuration tool, connect to the report server instance you just installed, and review the status indicator for each setting to verify that it is configured. Make sure that it’s all green ticks.
  4. Assign write permissions to the temporary ASP.NET folder to reporting service account (<domain or computer name>\reportingsvc).

4       Verify Reporting Services Installation

4.1     Verify that the report server is installed and running

  1. Run the Reporting Services Configuration tool, connect to the report server instance you just installed, and review the status indicator for each setting to verify that it is configured.
  2. Open the Services window and verify that the Report Server Windows service is running. To view the status of the Report Server Windows service, click Start, point to Control Panel, double-click Administrative Tools, and then double-click Services. When the list of services appears, scroll to Report Server (MSSQLSERVER). The status should be Started.
  3. On the instance of SQL Server that is hosting the report server database, verify that the SQL Server Agent service is running. SQL Server Agent must be running before users define subscriptions and other scheduled operations. Use the SQL Server Surface Area Configuration tool to enable SQL Server Agent.
  4. In a browser window, type http://localhost/reportserver (http://<computer name>/ReportServer<instance name>).The URL will be different if you installed the report server as a named instance.  You can also go and try running report server directly through IIS. 
  5. Run reports to test report server operations. For this step, you can install and publish the sample reports if you do not have any reports available. For more information, see AdventureWorks Report Samples in SQL Server Books Online.

4.2     Verify that Report Manager is installed and running  

  1. In a browser window, type http://localhost/reports  (http://<computer name>/Reports<instance name>) this is the virtual directory for Report Manager. 
You can also go and try browsing report manager directly through IIS. 
  1. Use Report Manager to create a new folder or upload a file to test whether definitions are passed back to the report server database. If these operations are successful, the connection is functional.
Posted by at No comments:
Labels:
Subscribe to: Posts (Atom)