Load Data From Excel To Grid View in Asp.net C# This is very easy to load data from excel sheet to grid view in asp.net web page using c#. In this tutorial you can learn how to Load excel sheet data to Grid View easily using asp.net C# code. This tutorial also covers how to get data from any excel file to Grid View dynamically in c# using file Upload control. Follow this steps 1. Create an asp.net project. 2. design asp.net page with file Upload, button control and a Grid View control. 3. create an excel connection string in the web config file. 4. Write code to load data from excel sheet to Grid View asp.net using C#. code:- using System; using System.Collections.Generic; using System.Linq; using System.Web; using System.Web.UI; using System.Web.UI.WebControls; using System.IO; using System.Collections; using System.Configuration; using System.Data.OleDb; using System.Data; public partial class _Default : System.Web.UI.Page {     protected void Page_Load(object se

11.5. Service Load Balancing Architecture The service load balancing architecture can be considered a specialized variation of the workload distribution architecture that is geared specifically for scaling cloud service implementations. Redundant deployments of cloud services are created, with a load balancing system added to dynamically distribute workloads. The duplicate cloud service implementations are organized into a resource pool, while the load balancer is positioned as either an external or built-in component to allow the host servers to balance the workloads themselves. Depending on the anticipated workload and processing capacity of host server environments, multiple instances of each cloud service implementation can be generated as part of a resource pool that responds to fluctuating request volumes more efficiently. The load balancer can be positioned either independent of the cloud services and their host servers (Figure 11.10), or built-in as part of the appli

11.4. Elastic Resource Capacity Architecture The elastic resource capacity architecture is primarily related to the dynamic provisioning of virtual servers, using a system that allocates and reclaims CPUs and RAM in immediate response to the fluctuating processing requirements of hosted IT resources (Figures 11.8 and 11.9). Figure 11.8. 1.Cloud service consumers are actively sending requests to a cloud service, 2. which are monitored by an automated scaling listener . 3.An intelligent automation engine script is deployed with workflow logic 4. that is capable of notifying the resource pool using allocation requests Figure 11.9. 5. Cloud service consumer requests increase , 6. causing the automated scaling listener to signal the intelligent automation engine to execute the script . 7. The script runs the workflow logic that signals the hypervisor to allocate more IT resources from the resource pools . 8. The hypervisor allocates additional CPU and RAM to the virtual

11.3. Dynamic Scalability Architecture The dynamic scalability architecture is an architectural model based on a system of predefined scaling conditions that trigger the dynamic allocation of IT resources from resource pools. Dynamic allocation enables variable utilization as dictated by usage demand fluctuations, since unnecessary IT resources are efficiently reclaimed without requiring manual interaction. The automated scaling listener is configured with workload thresholds that dictate when new IT resources need to be added to the workload processing. This mechanism can be provided with logic that determines how many additional IT resources can be dynamically provided, based on the terms of a given cloud consumer’s provisioning contract. The following types of dynamic scaling are commonly used: • Dynamic Horizontal Scaling – IT resource instances are scaled out and in to handle fluctuating workloads. The automatic scaling listener monitors requests and signals resource replic

11.2. Resource Pooling Architecture A resource pooling architecture is based on the use of one or more resource pools, in which identical IT resources are grouped and maintained by a system that automatically ensures that they remain synchronized. Provided here are common examples of resource pools: Physical server pools are composed of networked servers that have been installed with operating systems and other necessary programs and/or applications and are ready for immediate use. Virtual server pools are usually configured using one of several available templates chosen by the cloud consumer during provisioning. For example, a cloud consumer can set up a pool of mid-tier Windows servers with 4 GB of RAM or a pool of low-tier Ubuntu servers with 2 GB of RAM. Storage pools, or cloud storage device pools, consist of file-based or block-based storage structures that contain empty and/or filled cloud storage devices. Network pools (or interconnect pools) are composed of diffe

11.1. Workload Distribution Architecture IT resources can be horizontally scaled via the addition of one or more identical IT resources, and a load balancer that provides runtime logic capable of evenly distributing the workload among the available IT resources (Figure 11.1). The resulting workload distribution architecture reduces both IT resource over-utilization and under-utilization to an extent dependent upon the sophistication of the load balancing algorithms and runtime logic. Figure 11.1. A redundant copy of Cloud Service A is implemented on Virtual Server B. The load balancer intercepts cloud service consumer requests and directs them to both Virtual Servers A and B to ensure even workload distribution. This fundamental architectural model can be applied to any IT resource, with workload distribution commonly carried out in support of distributed virtual servers, cloud storage devices, and cloud services. Load balancing systems applied to specific IT resources usual

10.8. Hardened Virtual Server Images A virtual server is created from a template configuration called a virtual server image (or virtual machine image). Hardening is the process of stripping unnecessary software from a system to limit potential vulnerabilities that can be exploited by attackers. Removing redundant programs, closing unnecessary server ports, and disabling unused services, internal root accounts, and guest access are all examples of hardening. A hardened virtual server image is a template for virtual service instancecreation that has been subjected to a hardening process (Figure 10.13). This generally results in a virtual server template that is significantly more secure than the original standard image. Figure 10.13 . A cloud provider applies its security policies to harden its standard virtual server images. The hardened image template is saved in the VM images repository as part of a resource management system. Hardened virtual server images help count

10.7. Cloud-Based Security Groups Resource segmentation is used to enable virtualization by allocating a variety of physical IT resources to virtual machines. It needs to be optimized for public cloud environments, since organizational trust boundaries from different cloud consumers overlap when sharing the same underlying physical IT resources. The cloud-based resource segmentation process creates cloud-based security group mechanisms that are determined through security policies. Networks are segmented into logical cloud-based security groups that form logical network perimeters. Each cloud-based IT resource is assigned to at least one logical cloud-based security group. Each logical cloud-based security group is assigned specific rules that govern the communication between the security groups. Multiple virtual servers running on the same physical server can become members of different logical cloud-based security groups (Figure 10.11). Virtual servers can further be separated i

10.6. Single Sign-On (SSO) Propagating the authentication and authorization information for a cloud service consumer across multiple cloud services can be a challenge, especially if numerous cloud services or cloud-based IT resources need to be invoked as part of the same overall runtime activity. The single sign-on (SSO) mechanism enables one cloud service consumer to be authenticated by a security broker, which establishes a security context that is persisted while the cloud service consumer accesses other cloud services or cloud-based IT resources. Otherwise, the cloud service consumer would need to re-authenticate itself with every subsequent request. The SSO mechanism essentially enables mutually independent cloud services and IT resources to generate and circulate runtime authentication and authorization credentials. The credentials initially provided by the cloud service consumer remain valid for the duration of a session, while its security context information is

4. INPUT OUTPUT DEVICES ● The CPU and memory are not the only resources that the operating system must manage. ● I/O devices also interact heavily with the operating system. ● I/O devices generally consist of two parts: a controller and the device itself. ● The controller is a chip or a set of chips that physically controls the device. ● It accepts commands from the operating system, for example, to read data FROM the device, and carries them out ● Interrupts are very important in operating systems, so let us examine the idea more closely. ● In Fig.(a) we see a three-step process for I/O. ● In step 1, the driver tells the controller what to do by writing into its device registers. ● The controller then starts the device. When the controller has finished reading or writing the number of bytes it has been told to transfer, it signals the interrupt controller chip using certain bus lines in step 2. ● If the interrupt controller is ready to accept the interrupt

3. DISK ● Next in the hierarchy is magnetic disk (hard disk). A disk consists of one or more metal platters that rotate at 5400, 7200, 10,800 RPM or more. ● A mechanical arm pivots over the platters from the corner, similar to the pickup arm on an old 33-RPM phonograph for playing vinyl records. ● Information is written onto the disk in a series of concentric circles. At any given arm position, each of the heads can read an annular region called a track. Together, all the tracks for a given arm position form a cylinder. Operating System #PLAYLIST. #Subscribe the Channel Link :- IF any Query or Doubt DM on #Instagram :- @Aj Upgrading ( BANSODE TECH SOLUTION ) LinkedIn Profile Link for slides, code samples and text version of the video #blogger #software #linkedin #tech #hardware #video #operatingsystems #management #data #bscit #mumbaiuniv #operatingsystem #characteristics #bansodetechsolution #ajupgrading

2. Memory ● The top layer consists of the registers internal to the CPU. ● The storage capacity available in them is typically 32 × 32 bits on a 32-bit CPU and 64 × 64 bits on a 64-bit CPU. Less than 1 KB in both cases. ● Programs must manage the registers (i.e., decide what to keep in them) themselves, in software. ● Next comes the cache memory, which is mostly controlled by the hardware. ● Main memory is divided up into cache lines, typically 64 bytes, with addresses 0 to 63 in cache line 0, 64 to 127 in cache line 1, and so on. ● Cache memory is limited in size due to its high cost. Caching plays a major role in many areas of computer science, not just caching lines of RAM. Whenever a resource can be divided into pieces, some of which are used much more heavily than others, caching is often used to improve performance. ● Main memory comes next in the hierarchy of Fig. This is the workhorse of the memory system. Main memory is usually called RAM (Random Access Memor

1. Processors ● The ‘‘brain’’ of the computer is the CPU. It fetches instructions from memory and executes them. ● The basic cycle of every CPU is to fetch the first instruction from memory, decode it to determine its type and operands, execute it, and then fetch, decode, and execute subsequent instructions. ● The cycle is repeated until the program finishes. In this way, programs are carried out. ● The program counter, which contains the memory address of the next instruction to be fetched. ● The stack pointer, which points to the top of the current stack in memory. ● The PSW (Program Status Word). This register contains the condition code bits, which are set by comparison instructions, the CPU priority, the mode (user or kernel), and various other control bits. ● To improve performance, CPU designers have long abandoned the simple model of fetching, decoding, and executing one instruction at a time. Many modern CPUs have facilities for executing more than one inst

Characteristics of Operating System Here is a list of some of the most prominent characteristic features of Operating Systems ● Memory Management − Keeps track of the primary memory, i.e. what part of it is in use by whom, what part is not in use, etc. and allocates the memory when a process or program requests it. ● Processor Management − Allocates the processor (CPU) to a process and deallocates the processor when it is no longer required. ● Device Management − Keeps track of all the devices. This is also called I/O controller that decides which process gets the device, when, and for how much time. ● File Management − Allocates and de-allocates the resources and decides who gets the resources. ● Security − Prevents unauthorized access to programs and data by means of passwords and other similar techniques. Operating System #PLAYLIST. #Subscribe the Channel Link :- IF any Query or Doubt DM on #Instagram :- @Aj Upgrading ( BANSODE TECH SOLUTION ) Link