30 November 2016

TFS Installation Steps

How to: Install Team Foundation Server Using the Advanced Configuration
If you want to change the default installation options for Team Foundation Server, use the advanced configuration, which lets you configure Team Foundation Server on multiple servers and change many other options.
Why use advanced? The standard installation might not fit your needs. You might want to customize a single server installation or install Team Foundation Server and its configuration database on different servers. Perhaps you already have SQL Server or SharePoint Products running in your organization and you'd like to use one of these installations to host team projects or the data for Team Foundation Server. If you use the optional features that require prerequisite server software, these installations can also be hosted on different servers. If you use multiple servers, you can distribute the load between Team Foundation Server and the configuration database, or you can ensure that prerequisite server software for features such as reporting or the portal site is running on capable hardware.
System Requirement
You can install Team Foundation Server on a server that is running one of the following operating systems:
Server operating systems:
  • 64-bit version of Windows Server 2008   with SP2
  • 64-bit versions of Windows Server 2008 R2 ¹ with SP1
  • 64-bit versions of Windows Server 2012
IIS Requirement
IIS should be configured on Windows Server machine
SQL Server Requirements for Team Foundation Server
Supported editions
  • SQL Server 2008, R2 Express¹
  • SQL Server 2008, R2 Standard Edition¹
  • SQL Server 2008, R2 Enterprise Edition with SP 1 CU1 (Aug 25, 2011)²
  • SQL Server 2012, Express¹
  • SQL Server 2012, Standard Edition¹
  • SQL Server 2012, Enterprise Edition
Required for Team Foundation Server
  • Database Engine Services
  • Full-Text Search (or Full-Text and Semantic Extractions for Search in SQL Server 2012)
Accounts Required for Installation of Team Foundation Server
Component
Sample user logon name
Requirements
Team Foundation Server
TFSSERVICE
You can specify a built-in account or a user account. If you specify a user account, it must have the Log on as service permission.
You must not use the account that you use to install Team Foundation Server as the account for TFSSERVICE.
Team Foundation Build
TFSBUILD
You can specify a built-in account or a user account. If you use a user account, it must have the Log on as a service permission.
Team Foundation Server Proxy
TFSPROXY
You can specify a built-in account or a user account. If you use a user account, it must have the Log on as a service permission.
Reporting
TFSREPORTS
You must specify a user account that has the Allow log on locally permission.
Default: You are prompted for this account. You cannot use a built-in account for the report reader account.
SharePoint Products
WSSSERVICE
You must specify a user account.
Default: If you install Team Foundation Server with the default options, the account that you specified as the report reader account is also used for this account.
The Steps for IIS are for understanding. In Reality starting with TFS 2012 you dont need to configure IIS manually. TFS installation takes care of this step
Configure IIS 7.0 on Windows Server 2008 R2
Select Server manager and Web Server Role to Configure IIS

clip_image002[4]
clip_image004
Select asp.net and IIS 6 Management compatibility from the Role services Option
clip_image006
clip_image008
clip_image009
clip_image010

SQL Server 2008 R2 Installation with SP2

clip_image012
clip_image014
clip_image015[4]
clip_image016[4]
We need Database Engine Services and Full Text Search Feature for TFS installation
For Reporting Services We could select Report service and Analysis Service. Client Connecting tools Connectivity with SQL Management tools are important for tool like SQL Management Studio.
clip_image018[4]
clip_image019[4]clip_image021[4]
  
Important: If SQL administrator is not specified below than SQL will get looked and had to be used with SA login to update information.
clip_image022clip_image024[4]
clip_image026clip_image028clip_image030[4]
 
For TFS 2012 with SQL Server 2008 R2 SP1 with Cumulative update 1 is mandatory, I have installed 
SQL SP2 to meet TFS requirement
clip_image032clip_image034
Follow the wizard and complete the SQL server 2008 R2 SP1 Installation.

TFS 2012 Installation and Configuration

clip_image037clip_image039
  1. In the Team Foundation Server Configuration tool, choose Advanced, and then choose Start Wizard.
clip_image041
The Advanced Configuration wizard appears.
2. Read the Welcome screen, and then choose Next.
  1. In SQL Server Instance, type the name of the server that is running SQL Server or the named instance that will host the configuration databases, and choose Next.
clip_image043
clip_image044
4. Under Service Account, choose Use a system account to use a built-in account or Use a user account to use a domain or local account. If you are using a user account, you must type the password. To test the user account and password combination, you can optionally choose Test.
  1. Under Authentication Method, choose NTLM or Negotiate (Kerberos), and then choose Next.
    • If you choose NTLM, NTLM authentication is used. This option is the default setting.
    • If you choose Negotiate (Kerberos), Kerberos authentication is attempted first. If that attempt fails, NTLM authentication is used.
clip_image046[4]
  1. Under Web Site, type a name in Web Site Name and a port number in Port. This is the name that appears in Internet Information Services (IIS) and the port number used to connect to Team Foundation Server.
The default values for Web Site are Team Foundation Server and 8080.
  1. Under IIS Virtual Directory, you can use the default value of tfs or optionally type a virtual directory name.
Under Web Site, note the Team Foundation Server site URL, which is dynamically assembled based on your input in Web Site and IIS Virtual Directory. Clients use this URL to connect to Team Foundation Server. Choose Next
clip_image047[4]
  1. Use the Configure Reporting for Team Foundation Server page to opt in or out of using reporting. Select the Configure Reporting for use with Team Foundation Server check box to use reporting, or clear the check box to skip reporting, and then choose Next.
clip_image049
clip_image050
If you specified a user account for the service account of Team Foundation Server in step 4, you must select the Use a different account than the Team Foundation Server service account for the report reader account check box to use a different account
clip_image051
  1. Use the Configure SharePoint for Team Foundation Server page to opt in or out of using SharePoint Products. Clear the check box to skip SharePoint Products. Choose Next.
clip_image053
If you selected the check box to configure SharePoint Products, perform one of the following procedures:
    • Install and configure SharePoint on this machine.
      1. Choose Install and configure SharePoint on this machine and choose Next.
      2. Choose the big Install SharePoint Foundation 2010 button. Once the install completes, choose Next.
      3. Type a user account and password for the service account forSharePoint Foundation 2010 (WSSSERVICE). If you specified a user account for the service account of Team Foundation Server in step 4, you must select the Use a different account than the Team Foundation Server service account for the SharePoint farm check box to use a different account.
      4. Choose Next.
  1. Select the Create a new team project collection check box to create a collection, or clear that check box to skip that step.
clip_image055
  1. On the Review page, review the settings, and choose Next.
The wizard validates your configuration.
13. Choose Configure.
The wizard applies configuration settings. This process might take several minutes
clip_image057

For Configuring Build Service with TFS


clip_image058
clip_image060
clip_image062
clip_image064[4]

Contact me

Your Name :
Your Email: (required)
Your Message: (required)

3 November 2015

SQL SERVER – Find Currently Running Query – T-SQL

This is the script which I always had in my archive. Following script find out 
which are the queries running currently on your server.
SELECT 
sqltext.TEXT,
req.session_id,
req.status,
req.command,
req.cpu_time,req.total_elapsed_time
FROM sys.dm_exec_requests req CROSS APPLY sys.dm_exec_sql_text(sql_handle) AS sqltext
While running above query if you find any query which is running for long time 
it can be killed using following command.
KILL [session_id]

3 June 2015

6 March 2015

Find Column Names From Table in SQL Server

Select Column_Name
From INFORMATION_SCHEMA.COLUMNS
Where TABLE_NAME='CustomerOrderDetails'


Id
ExportLicenseNumber
CustomerOrderId
RepairSerialNumber
IsInitialQuote
Revision
CODate
COReceiptDate
PriorityCodeOfCustomer
CustomerRefNumber
CustomerRefDefinition
OrderFromCustomerId
DeliverToCustomerId
ResponsibleLocationId
DeliveryPoint
DeliveryTerms
PaymentTerms
ShipmentViaSupplierId
OtherCommentsAndSpecialInstructions
CurrencyId
LeadTime
LeadTimeUOM
QuoteTypeId
QuotePriceType
ExpectedDeliveryDate
EstimatedDeliveryDate
PartialShipmentAllowed
ShippingAndHandlingPrice
ShippingAndHandlingPriceUSD
OtherChargesType
OtherCharges
OtherChargesUSD
OtherCharges1
OtherCharges1USD
OtherCharges1Type
IncountryTransportation
IncountryTransportationUSD
Insurance
TaxPercentage
DiscountUSD
Discount
ItemReferenceNumber
ReferenceNumber
PartId
PartConditionId
SupplierPartNumber
Quantity
Price
PriceUSD
IsItemClosed
CustomerOrderNotes
OrderFromCustomerAddressId
OrderFromcustomerPOCId
CustomerAddressId
CustomerPOCId
DeliverToAddressId
DeliverToPOCId
SalesExportLicenceRequired
RepairExportLicenceRequired
ExportLicenseTypeId
ItemDecremented
DSP
ExportLicenseCategoriesId
ExportToCountryId
EndUserCountryId
EndUserCustomerId
CFR1234a
CFR1234b
DSP61
WarrantyRequirement
CustomerRefOrderNumber
IsArchived
COCreationDate
CustomerOrderItemNote
DeclaredCustomsValueoftheGoodbyCustomer

5 March 2015

12 December 2014

5 Ways to send data between ASP.NET Pages

How many ways do you know to send the data between ASP.NET Pages? In this post I’m going to list 5 different ways. First 2-3 ways are very well-known and last 2-3 ways are not much popular. You will find here mostly inline methods to receive the data on different pages. You can download the complete code.

So, let’s start with the very well-known one.

1. Using Session State or Application Variable

Using this technique I will store the data in session variable on the client machine and on the next page will grab it. Using Application Variable instead of Session Variable is recommend by experts.

ASPX Page:

<asp:TextBox ID="txtData" runat="server"></asp:TextBox>
<br /><br />
<asp:Button ID="btnSessionState" runat="server" Text="Session State" OnClick="btnSessionState_Click"/>

Code-Behind:

protected void btnSessionState_Click(object sender, EventArgs e)
{
    Session["Data"] = txtData.Text;
    Response.Redirect("SessionState.aspx");
}

Receiver ASPX Page:

<div>
<h1>Session State</h1>
    Data is: <%=Session["Data"%>
And you all set, run it test it.

2. Using Query String

Using this technique I will add my data with URL and on the next page will grab it.

ASPX Page:

<asp:TextBox ID="txtData" runat="server"></asp:TextBox>
<br /><br />
<asp:Button ID="btnQueryString" runat="server" Text="Query String" OnClick="btnQueryString_Click" />

Code-Behind:

protected void btnQueryString_Click(object sender, EventArgs e)
{
    Response.Redirect("QueryString.aspx?Data=" + Server.UrlEncode(txtData.Text));
}

Receiver ASPX Page:

<h1>Query String</h1>
        Data is: <%=Server.UrlDecode(Request.QueryString["Data"]) %>
And you all set, run it test it.

3. Using HttpPost

Using this technique I will call a post back url and the on next page using Request.From I will grab it.

ASPX Page:

<asp:TextBox ID="txtData" runat="server"></asp:TextBox>
<br /><br />
<asp:Button ID="btnHttpPost" runat="server" Text="HTTPPost" PostBackUrl="~/HttpPost.aspx" />

Note: There is no any code-behind method call instead of a postbackurl in button attribute.

Receiver ASPX Page:

<h1>HttpPost</h1>
        Data is: <%=Request.Form["txtData"%>

And you all set, run it test it.

4. Using Public Properties

Using this technique I will send the using a public method and on the next page will grab it using PreviousPage.MethodName.

ASPX Page:

<asp:TextBox ID="txtData" runat="server"></asp:TextBox>
<br /><br />
<asp:Button ID="btnPublicProperties" runat="server" Text="Public Properties"OnClick="btnPublicProperties_Click" />

Code-Behind:

protected void btnPublicProperties_Click(object sender, EventArgs e)
{
    Server.Transfer("PublicProperties.aspx");
}
public string PublicData
{
    get
    {
        return txtData.Text;
    }
}

Receiver ASPX Page:

<h1>Public Properties</h1>
        Data is: <%=PreviousPage.PublicData %>

And you all set, run it test it.

5. Using Controls

Using this technique I will just redirect the user on next page and on the next page will use PreviousPage.FindControl to grab the data.

ASPX Page:

<asp:TextBox ID="txtData" runat="server"></asp:TextBox>
<br /><br />
<asp:Button ID="btnControl" runat="server" Text="Control" OnClick="btnControl_Click" />

Code-Behind:

protected void btnControl_Click(object sender, EventArgs e)
{
    Server.Transfer("Control.aspx");
}

Receiver ASPX Page:

<h1>Control</h1>
        Data is: <asp:Label ID="Label1" runat="server" Text="Label" />

Receiver Code-Behind Page:

protected void Page_Load(object sender, EventArgs e)
{
    var textbox = PreviousPage.FindControl("txtData"as TextBox;
    if (textbox != null)
    {
        Label1.Text = textbox.Text;
    }
}

And you all set, run it test it.

You can use any technique given above depending upon your business requirement.