Tuesday, 4 November 2014

How to implement Windows authentication and authorization in ASP.NET

Authentication and authorization

Windows authentication and Windows authorization are two terms that are frequently interchanged. However, they do not have the same meaning. Windows authentication permits the recipient to determine the user's identity. Windows authorization determines the resources to which a user may gain access.

Configure Web application for Windows authentication

To configure your Web application for Windows authentication, follow these steps:

Create an ASP.NET Web Application named ASPNETWinAuth. By default, theWebForm1.aspx file appears.
In the HTML view of WebForm1.aspx, replace the existing code with the following sample code:
<%=User.Identity.Name%>
Click Start, point to Programs, point to Administrative tools, and then click Internet Information Services.
The Internet Information Services MMC appears. Expand Computer, and then expand a Web site that uses Windows authentication.
Click the ASPNETWinAuth Web site application.
On the Action menu, click Properties.
In Properties, click the Directory Security tab.
Under Anonymous access and authentication control, click Edit.
In Authentication Methods, click to select Integrated Windows authentication. Click to clear all other check boxes.
Click OK.
In Properties, click OK. The ASPNETWinAuth Web application is now configured to accept valid user accounts.

Configure the ASP.NET application

After you configure the IIS Web site for Integrated Windows Authentication, you must configure the ASP.NET application to recognize authenticated users. To do this, you must change the Web.config file. In the Web.config file, locate the <authentication> tag, and then set the mode attribute to Windows, as in the following example:

<authentication mode="Windows" />

Test authentication

To test your Windows authentication setting, follow these steps:

In Microsoft Internet Explorer, view the WebForm1.aspx page. This page is located in the Http://Localhost folder. For example:
http://Localhost/ASPNETWinAuth/WebForm1.aspx
Because Integrated Windows Authentication uses the current Windows user information on the client computer for the authentication, it does not immediately prompt the user for a user name and password. However, if the authentication exchange cannot identify the user, a dialog box appears that prompts the user for a Windows user account user name and password.
Type a valid user name and password. When the page loads, your user name appears in the following format:
Domain Name\User Name

Restrict access

In ASP.NET, you set authorization to the application by adding settings in the Web.config file. You can specify which users or groups are permitted to have access to what resources as follows:

To permit all users of an NT Group named Managers to have access to your resources, use the following code:

<configuration>
  <system.web>
    <authorization>
      <allow roles="domainname\Managers" />
      <deny users="*" />
    </authorization>
  </system.web>
</configuration>

To permit only specific users to have access, use the following code:
<configuration> <system.web> <authorization> <allow users="domainname\user1,domainname\user2,domainname\user3" /> <deny users="*" /> </authorization> </system.web> </configuration>
Note You can specify multiple roles or users by using a comma separated list. Verify that you use the correct case when you specify the configuration file element and the associated attribute values. This code is case sensitive.

Monday, 3 November 2014

Windows Authenticated logon configuration for Microsoft IIS7

<configuration>
    <system.web>
        <compilation debug="true" targetFramework="4.0" />
        <authentication mode="Windows" />

    </system.web>
</configuration>

After declaring in web.config... we have to perform certain steps.

Configuration

Step 1. Setup and configure the HelpMaster Active Directory module

Before any Windows-based authentication can take place for any of the HelpMaster modules, including the web interface, you will need to first install, configure and run the HelpMaster Active Directory module to synchronize your HelpMaster users with a valid Active Directory account. See Active Directory Module Overview for the installation and configuration process

Step 2. Create a Windows Authentication 'hmplogin' virtual directory / application on IIS

In order for the Windows Authentication feature of IIS 7 to work, it must first be installed. This component is not installed by default, so you may need to install it. See Installing Microsoft IIS 7 for details. Ensure that you check the "Windows Authentication" checkbox during the install (see picture).

In addition to the creation of the required virtual directory for the web interface, a second directory needs to be created called 'hmplogin'. Unlike the standard HelpMaster web interface virtual directory which accepts anonymous authentication, this virtual directory will be configured to authenticate valid Windows accounts (network accounts) only. Once authentication has been successful, the authenticated Windows user will be automatically re-directed back to the standard HelpMaster web interface application and automatically logged in with their corresponding HelpMaster account.

To configure the Windows Authentication virtual directory, perform the following steps on your HelpMaster web server. The following steps reflect the steps required for IIS version 7.

Open the IIS Manager by selecting Control Panel > Administrative Tools > Internet Information Services (IIS) Manager
"Right click" on the Default Web Site node/branch and select Add application... from the pop-up menu

The properties for a new application will be displayed.
The "Add Application" screen contains several settings that need to be configured. After each of the settings below have been configured, click OK to create the web application.

Alias : This is the name of your HelpMaster Windows authentication web application. This should be one word without any spaces. This name will be the web page that you will need to access to use the HelpMaster Module. eg. www.machinename.com/virtualdirectoryalias. It is recommended that you call the name of this application "hmplogin". This is the name used throughout this documentation.

Application pool : Select the application pool that the HelpMaster web interface will operate in. Choose the default, or select / create an application pool. For further information about Application pools, refer to

Physical path : Click the "..." button to browse to where you installed HelpMaster. It is vital that you select the [HMP Web Install Path]\WinLogin folder. If you selected default settings during the setup, this location may be "C:/inetpub/wwwroot/HelpMaster Web Interface/WinLogin" or similar. Note: If you moved this folder at any time, or wish to re-locate this folder, please read this first.

Connect as... : Select the connection method. It is vital that this setting is set to "Application user (pass-through authentication)" (Important!)
Once the HelpMaster "hmplogin" application has been created, ensure that it is configured for Windows Authentication.

Click on the "hmplogin" application, then find the "Authentication" icon in the "IIS" group. Right-click and select "Open Feature"

If the Windows Authentication icon is not displayed, it most likely means that it is not installed. See Installing Microsoft IIS 7 for details. Ensure that you check the "Windows Authentication" checkbox during the install (see picture).
Right-click on "Windows Authentication" and select "Enable" from the pop-up menu.

Step 3. Configuring redirect for un-authenticated requests (optional)

Now that you have created a web application to accept Windows authenticated logins, you may like to configure this application to appropriately handle logins that for whatever reason cannot be authenticated. (eg. account has expired, network issues, non-network login etc). When an authentication request fails, you can configure the IIS to re-direct the user back to the standard HelpMaster login page where they can try logging onto the HelpMaster web interface via their HelpMaster account.

To configure un-authenticated request redirection, perform the following steps on your HelpMaster web server.

Click on the "hmplogin" application, then find the "Error Pages" icon in the "IIS" group. Right-click and select "Open Feature"
Edit the properties for '401;1' and '401;2'. These error codes refer to authentication errors. Rather than display the default error page, you can re-direct these errors to point back to your standard HelpMaster web interface application that youconfigured previously.

Disabling Anonymous Access to the Admin Site

Configuring IIS 7 to Force Authentication on the Admin Site

This article describes how to use IIS authentication to further protect and secure your AspDotNetStorefront admin site. The concepts covered here require an understanding of Windows Security, and should be undertaken by a knowledgeable IT professional. Improperly configured security settings on a publicly facing server can potentially make the server vulnerable to attack or prevent legitimate users from accessing the system.

Choosing between Windows Authentication and Basic Authentication

IIS 7 providers administrators with the option of choose three settings for authenticating users.

For the purpose of this article, we will cover the two applicable options.

Windows Authentication in IIS 7 is the most secure option, as it uses hashing technology to prevent sending clear text usernames and passwords over the internet. Many web browsers do not support this however, so if your admin site is accessed by clients using browsers other than Microsoft Internet Explorer, Basic Authentication should be used instead.

Basic Authentication can be used on admin sites that must be accessed by a wide range of browsers and devices. One important thing to keep in mind with Basic Authentication is that usernames and passwords are not hashed, so additional precautions should be taken to ensure that your credentials are safe. Sites using Basic Authentication should always use SSL when connecting to the admin site. This will ensure that credentials are encrypted in transit to and from the website.

Disabling Anonymous Access to the Admin Site

1. Open the IIS Management Console on the web server

2. Expand the Sites folder

3. Expand your AspDotNetStorefront web site

4. Select the Admin folder

5. Double-Click the IIS - Authentication option

6. Under Authentication, select the Anonymous Authentication and click 'Disable' in the Actions pane on the right

7. For Windows Authentication: Select the Windows Authentication and click 'Enable' in the Actions pane on the right

8. For Basic Authentication: Select the Basic Authentication and click 'Enable' in the Actions pane on the right

NOTE: You can potentially enable both authentication mechanisms on the site. If both Basic and Windows Authentication are enabled, IIS will first try to use Windows Authentication, and then attempt Basic if that fails.

NOTE: If using Basic Authentication, you will receive a warning stating that "...credentials will be sent in clear text over the wire". This warning does not apply to valid SSL connections.

NOTE: With Windows Authentication you will get an Alert stating that "Challenge-based and login redirect-based authentication cannot be used simultaneously." but it can be ignored.

10. If using Windows Authentication only, restart the site. If using Basic Authentication, select Basic Authentication and click "Edit..." in the Actions menu to the right, and enter your site domain (Realm is optional), then click OK

11. If requiring HTTPS for the admin console, double-click the IIS - SSL Settings for the Admin folder, and check the "Require SSL". NOTE that SSL must be in place and valid for this option to be available

12. Restart the site

Giving Users Access to the Admin Site

Once Basic or Windows Authentication is enabled on your admin site, user access to the entire directory is controlled using NTFS permissions. To assign a user permission to access your admin site:

1. Create a new user account in Windows using Computer Management (or Active Directory Users and Computers if your server is a member of an Active Directory domain).

2. Using Windows Explorer, browse to the directory that contains your AspDotNetStorefront web site files.

3. Right click the Admin folder and choose Properties.

4. Click the Security tab and click Add.

5. Enter the name of the user you just created and click OK, or click advanced to view a list of all users you can add.

6. Assign the user Read, List, and Read & Execute permissions to the admin site.

7. Click OK.

Testing Authentication

1. Go to http://yoursite/admin or https://yoursite/admin (depending on whether SSL is required or not).

2. If all steps were done properly, you will be presented with a login prompt.

3. Enter your Windows user account username and password and click OK.

4. You should now be taken to your Admin site’s login page.

Wednesday, 1 October 2014

How to find dictionary duplicate values in C#

For Reference:

//initialize a dictionary with keys and values.    
Dictionary<int, string> plants = new Dictionary<int, string>() {    
    {1,"Speckled Alder"},    
    {2,"Apple of Sodom"},    
    {3,"Hairy Bittercress"},    
    {4,"Pennsylvania Blackberry"},    
    {5,"Apple of Sodom"},    
    {6,"Water Birch"},    
    {7,"Meadow Cabbage"},    
    {8,"Water Birch"}    
};  
  
Response.Write("<b>dictionary elements........</b><br />");
        
//loop dictionary all elements   
foreach (KeyValuePair<int, string> pair in plants)  
{
    Response.Write(pair.Key + "....."+ pair.Value+"<br />");
}  
  
//find dictionary duplicate values.  
var duplicateValues = plants.GroupBy(x => x.Value).Where(x => x.Count() > 1);

Response.Write("<br /><b>dictionary duplicate values..........</b><br />");

//loop dictionary duplicate values only            
foreach(var item in duplicateValues)  
{
    Response.Write(item.Key+"<br />");
}

By using XML

counties = XDocument.Load(HttpContext.Current.Server.MapPath("/data/counties.xml"))

.Descendants("Row")

.GroupBy(i => i.Attribute("Code").Value)

.Where(g => g.Count() == 1)

.Select(g => new { Code = g.Key, Desc = g.First().Attribute("Descrip").Value })

.ToDictionary(x => x.Code, x => x.Desc);

How to Remove Duplicates and Get Distinct records from List using LINQ?

using System;

using System.Collections.Generic;

using System.Data;

using System.Linq;

namespace AbundantCode

{

internal class Program

{

//How to Remove Duplicates and Get Distinct records from List using LINQ ?

private static void Main(string[] args)

{

List<Employee> employees = new List<Employee>()

{

new Employee { EmpID = 1 , Name ="AC"},

new Employee { EmpID = 2 , Name ="Peter"},

new Employee { EmpID = 3 , Name ="Michael"},

new Employee { EmpID = 3 , Name ="Michael"}

};

//Gets the Distinct List

var DistinctItems = employees.GroupBy(x => x.EmpID).Select(y => y.First());

foreach(var item in DistinctItems)

Console.WriteLine(item.Name);

Console.ReadLine();

}

public class Employee

{

public string Name { get; set; }

public int EmpID { get; set; }

}

How to find the duplicate items in a list?

string[] ss ={ "1","1","1"};
            List<string> myList = new List<string>();

            foreach (String s in ss)
            {
                if (!myList.Contains(s))
                {
                 myList.Add(s);
                }
            }

            foreach (String s in myList)
            {
                Console.WriteLine(s);
            }

Sunday, 28 September 2014

Nested ListView

Sample

Output

----------------------------------

.collapse

{

background-position: left -172px;

height: 14px;

width: 13px;

background-repeat: no-repeat;

background-image: url('DXR1.png');

cursor: pointer;

}

.expand

{

background-position: -14px -187px;

height: 14px;

width: 13px;

background-repeat: no-repeat;

background-image: url('DXR.png');

cursor: pointer;

}

table

{

border: solid 0px black;

}

table td

{

border-right: solid 0px black;

border-bottom: solid 0px black;

}

table th

{

border-bottom: solid opx black;

}

.SUBDIV table

{

border: 0px;

border-left: 0px solid black;

}

</style>

$(document).ready(function () {

// THIS IS FOR HIDE ALL DETAILS ROW

$(".SUBDIV table tr:not(:first-child)").not("tr tr").hide();

$(".SUBDIV .btncolexp").click(function () {

$(this).closest('tr').next('tr').toggle();

//this is for change img of btncolexp button

if ($(this).attr('class').toString() == "btncolexp collapse") {

$(this).addClass('expand');

$(this).removeClass('collapse');

}

else {

$(this).removeClass('expand');

$(this).addClass('collapse');

}

});

</script>

<div>

<asp:ListView ID="ListView1" runat="server" OnItemDataBound="ListView1_ItemDataBound">

</th>

Manager Name

</th>

</th>

</th>

</th>

</th>

</tr>

</table>

</div>

</LayoutTemplate>

</div>

</td>

<asp:HiddenField ID="HdnManagerId" runat="server" Value='<%#Eval("MID") %>' />

<asp:Label ID="PriceDescLabel" runat="server" Text='<%# Eval("ManagerName") %>' />

</td>

<asp:Label ID="ALabel" runat="server" Text='<%# Eval("A") %>' />

</td>

<asp:Label ID="BLabel" runat="server" Text='<%# Eval("B") %>' />

</td>

<asp:Label ID="CLabel" runat="server" Text='<%# Eval("C") %>' />

</td>

<asp:Label ID="DLabel" runat="server" Text='<%# Eval("D") %>' />

</td>

</tr>

<tr>

<asp:ListView ID="ListView2" runat="server">

<table id="itemPlaceholderContainer" runat="server" style="width: 100%;

background-color: #A3F5F3; border-collapse: collapse; border-color: #999999;

border-style: none; border-width: 1px; font-family: Verdana, Arial, Helvetica, sans-serif;">

</tr>

</table>

</td>

</tr>

</table>

</LayoutTemplate>

</td>

<asp:Label ID="PriceDescLabel" runat="server" Text='<%# Eval("PriceDesc") %>' />

</td>

<asp:Label ID="ALabel" runat="server" Text='<%# Eval("A") %>' />

</td>

<asp:Label ID="BLabel" runat="server" Text='<%# Eval("B") %>' />

</td>

<asp:Label ID="CLabel" runat="server" Text='<%# Eval("C") %>' />

</td>

<asp:Label ID="DLabel" runat="server" Text='<%# Eval("D") %>' />

</td>

</tr>

</ItemTemplate>

</asp:ListView>

</td>

</tr>

</table>

</div>

</ItemTemplate>

</asp:ListView>

</div>

---------------------------------------------------------------------

using System;

using System.Collections.Generic;

using System.Linq;

using System.Web;

using System.Web.UI;

using System.Web.UI.WebControls;

using System.Data;

using System.Data.SqlClient;

using System.Configuration;

namespace HierachicalListViewDemo

{

public partial class WebForm1 : System.Web.UI.Page

{

string connection = ConfigurationManager.ConnectionStrings["TestConnectionString"].ConnectionString;

protected void Page_Load(object sender, EventArgs e)

{

if (!IsPostBack)

{

PopulateFirstListData();

}

private void PopulateFirstListData()

{

SqlConnection con = new SqlConnection(connection);

SqlDataAdapter da = new SqlDataAdapter("SELECT MAX(ManagerName) as ManagerName, MAX(PriceDesc) as PriceDesc, Sum(A) as A, SUM(B) as B,SUM(C) as C,SUM(D) as D, MID FROM dbo.ExceptionList excp left join dbo.Manager Mgr on excp.ManagerId = Mgr.MID Group by MID", con);

DataSet ds = new DataSet();

da.Fill(ds);

ListView1.DataSource = ds;

ListView1.DataBind();

}

private DataSet PopulateSecondListData(int ManagerId)

{

SqlConnection con = new SqlConnection(connection);

SqlDataAdapter da = new SqlDataAdapter("SELECT * FROM dbo.ExceptionList where ManagerId=" + ManagerId, con);

DataSet ds = new DataSet();

da.Fill(ds);

return ds;

}

protected void ListView1_ItemDataBound(object sender, ListViewItemEventArgs e)

{

if (e.Item.ItemType == ListViewItemType.DataItem)

{

HiddenField hdnManagerId = (HiddenField)e.Item.FindControl("HdnManagerId");

ListView listview2 = (ListView)e.Item.FindControl("ListView2");

DataSet list2ds = PopulateSecondListData(Convert.ToInt32(hdnManagerId.Value));

listview2.DataSource = list2ds;

listview2.DataBind();

}

--------------------------------------------------------

--------------------------------------------------------

Tables

-------------------------------

CREATE TABLE [dbo].[Region](

[RID] [int] IDENTITY(1,1) NOT NULL,

[RegionName] [varchar](50) NOT NULL,

CONSTRAINT [PK_Region] PRIMARY KEY CLUSTERED

(

[RID] ASC

)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]

) ON [PRIMARY]

SET ANSI_PADDING OFF

SET IDENTITY_INSERT [dbo].[Region] ON

INSERT [dbo].[Region] ([RID], [RegionName]) VALUES (1, N'North')

INSERT [dbo].[Region] ([RID], [RegionName]) VALUES (2, N'South')

INSERT [dbo].[Region] ([RID], [RegionName]) VALUES (3, N'East')

INSERT [dbo].[Region] ([RID], [RegionName]) VALUES (4, N'West')

SET IDENTITY_INSERT [dbo].[Region] OFF

/****** Object: Table [dbo].[Manager] Script Date: 09/28/2014 23:58:23 ******/

SET ANSI_NULLS ON

SET QUOTED_IDENTIFIER ON

SET ANSI_PADDING ON

CREATE TABLE [dbo].[Manager](

[MID] [int] IDENTITY(1,1) NOT NULL,

[ManagerName] [varchar](50) NOT NULL,

[RegionId] [int] NOT NULL,

CONSTRAINT [PK_Manager] PRIMARY KEY CLUSTERED

(

[MID] ASC

)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]

) ON [PRIMARY]

SET ANSI_PADDING OFF

SET IDENTITY_INSERT [dbo].[Manager] ON

INSERT [dbo].[Manager] ([MID], [ManagerName], [RegionId]) VALUES (1, N'Raju', 1)

INSERT [dbo].[Manager] ([MID], [ManagerName], [RegionId]) VALUES (2, N'Raja', 2)

INSERT [dbo].[Manager] ([MID], [ManagerName], [RegionId]) VALUES (3, N'Sai', 3)

INSERT [dbo].[Manager] ([MID], [ManagerName], [RegionId]) VALUES (4, N'Pravin', 4)

INSERT [dbo].[Manager] ([MID], [ManagerName], [RegionId]) VALUES (5, N'Mahesh', 1)

INSERT [dbo].[Manager] ([MID], [ManagerName], [RegionId]) VALUES (6, N'Lakshmi', 2)

INSERT [dbo].[Manager] ([MID], [ManagerName], [RegionId]) VALUES (7, N'Gandharv', 3)

INSERT [dbo].[Manager] ([MID], [ManagerName], [RegionId]) VALUES (8, N'Avinash', 4)

INSERT [dbo].[Manager] ([MID], [ManagerName], [RegionId]) VALUES (9, N'Govind', 1)

INSERT [dbo].[Manager] ([MID], [ManagerName], [RegionId]) VALUES (10, N'Harish', 2)

SET IDENTITY_INSERT [dbo].[Manager] OFF

/****** Object: Table [dbo].[ExceptionList] Script Date: 09/28/2014 23:58:23 ******/

SET ANSI_NULLS ON

SET QUOTED_IDENTIFIER ON

SET ANSI_PADDING ON

CREATE TABLE [dbo].[ExceptionList](

[PriceId] [int] IDENTITY(1,1) NOT NULL,

[PriceDesc] [varchar](500) NOT NULL,

[A] [int] NULL,

[B] [int] NULL,

[C] [int] NULL,

[D] [int] NULL,

[RegionId] [int] NOT NULL,

[ManagerId] [int] NOT NULL,

CONSTRAINT [PK_ExceptionList] PRIMARY KEY CLUSTERED

(

[PriceId] ASC

)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]

) ON [PRIMARY]

SET ANSI_PADDING OFF

SET IDENTITY_INSERT [dbo].[ExceptionList] ON

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (1, N'Testing_1', 6, 8, 5, NULL, 1, 1)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (2, N'Testing_2', 7, NULL, 8, NULL, 2, 2)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (3, N'Testing_3', NULL, NULL, 7, 8, 3, 3)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (4, N'Testing_4', NULL, 7, 7, NULL, 4, 4)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (5, N'Testing_5', 7, 7, 7, NULL, 1, 5)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (6, N'Testing_6', NULL, 7, NULL, 4, 2, 6)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (7, N'Testing_7', 8, NULL, 7, NULL, 3, 7)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (8, N'Testing_8', NULL, 7, NULL, 2, 4, 8)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (9, N'Testing_9', 9, NULL, 7, NULL, 1, 9)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (10, N'Testing_10', NULL, NULL, NULL, 3, 2, 10)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (11, N'Testing_11', NULL, NULL, 7, NULL, 3, 1)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (12, N'Testing_12', 12, 7, NULL, 3, 4, 2)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (13, N'Testing_13', NULL, NULL, NULL, NULL, 3, 3)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (14, N'Testing_14', 22, 7, 7, 6, 2, 4)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (15, N'Testing_15', 6, 8, 5, NULL, 1, 1)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (16, N'Testing_16', 7, NULL, 8, NULL, 2, 2)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (17, N'Testing_32', NULL, NULL, 7, 8, 3, 3)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (18, N'Testing_41', NULL, 7, 7, NULL, 4, 4)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (19, N'Testing_51', 7, 7, 7, NULL, 1, 5)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (20, N'Testing_61', NULL, 7, NULL, 4, 2, 6)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (21, N'Testing_71', 8, NULL, 7, NULL, 3, 7)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (22, N'Testing_81', NULL, 7, NULL, 2, 4, 8)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (23, N'Testing_91', 9, NULL, 7, NULL, 1, 9)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (24, N'Testing_101', NULL, NULL, NULL, 3, 2, 10)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (25, N'Testing_111', NULL, NULL, 7, NULL, 3, 1)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (26, N'Testing_121', 12, 7, NULL, 3, 4, 2)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (27, N'Testing_131', NULL, NULL, NULL, NULL, 3, 3)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (28, N'Testing_141', 22, 7, 7, 6, 2, 4)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (29, N'Testing_12', 6, 8, 5, NULL, 1, 1)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (30, N'Testing_22', 7, NULL, 8, NULL, 2, 2)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (31, N'Testing_32', NULL, NULL, 7, 8, 3, 3)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (32, N'Testing_42', NULL, 7, 7, NULL, 4, 4)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (33, N'Testing_52', 7, 7, 7, NULL, 1, 5)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (34, N'Testing_62', NULL, 7, NULL, 4, 2, 6)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (35, N'Testing_72', 8, NULL, 7, NULL, 3, 7)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (36, N'Testing_82', NULL, 7, NULL, 2, 4, 8)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (37, N'Testing_92', 9, NULL, 7, NULL, 1, 9)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (38, N'Testing_102', NULL, NULL, NULL, 3, 2, 10)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (39, N'Testing_112', NULL, NULL, 7, NULL, 3, 1)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (40, N'Testing_122', 12, 7, NULL, 3, 4, 2)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (41, N'Testing_132', NULL, NULL, NULL, NULL, 3, 3)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (42, N'Testing_142', 22, 7, 7, 6, 2, 4)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (43, N'Testing_152', 6, 8, 5, NULL, 1, 1)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (44, N'Testing_162', 7, NULL, 8, NULL, 2, 2)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (45, N'Testing_322', NULL, NULL, 7, 8, 3, 3)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (46, N'Testing_412', NULL, 7, 7, NULL, 4, 4)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (47, N'Testing_512', 7, 7, 7, NULL, 1, 5)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (48, N'Testing_612', NULL, 7, NULL, 4, 2, 6)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (49, N'Testing_712', 8, NULL, 7, NULL, 3, 7)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (50, N'Testing_812', NULL, 7, NULL, 2, 4, 8)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (51, N'Testing_912', 9, NULL, 7, NULL, 1, 9)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (52, N'Testing_1012', NULL, NULL, NULL, 3, 2, 10)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (53, N'Testing_1112', NULL, NULL, 7, NULL, 3, 1)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (54, N'Testing_1212', 12, 7, NULL, 3, 4, 2)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (55, N'Testing_1312', NULL, NULL, NULL, NULL, 3, 3)

INSERT [dbo].[ExceptionList] ([PriceId], [PriceDesc], [A], [B], [C], [D], [RegionId], [ManagerId]) VALUES (56, N'Testing_142', 22, 7, 7, 6, 2, 4)

SET IDENTITY_INSERT [dbo].[ExceptionList] OFF

/****** Object: ForeignKey [FK_ExceptionList_Manager] Script Date: 09/28/2014 23:58:23 ******/

ALTER TABLE [dbo].[ExceptionList] WITH CHECK ADD CONSTRAINT [FK_ExceptionList_Manager] FOREIGN KEY([ManagerId])

REFERENCES [dbo].[Manager] ([MID])

ALTER TABLE [dbo].[ExceptionList] CHECK CONSTRAINT [FK_ExceptionList_Manager]

/****** Object: ForeignKey [FK_ExceptionList_Region] Script Date: 09/28/2014 23:58:23 ******/

ALTER TABLE [dbo].[ExceptionList] WITH CHECK ADD CONSTRAINT [FK_ExceptionList_Region] FOREIGN KEY([RegionId])

REFERENCES [dbo].[Region] ([RID])

ALTER TABLE [dbo].[ExceptionList] CHECK CONSTRAINT [FK_ExceptionList_Region]

/****** Object: ForeignKey [FK_Manager_Region] Script Date: 09/28/2014 23:58:23 ******/

ALTER TABLE [dbo].[Manager] WITH CHECK ADD CONSTRAINT [FK_Manager_Region] FOREIGN KEY([RegionId])

REFERENCES [dbo].[Region] ([RID])

ALTER TABLE [dbo].[Manager] CHECK CONSTRAINT [FK_Manager_Region]