Game List


Game List



All games here are
powered by : DynamicDrive

Benefits of Replication

Replication offers various benefits depending on the type of replication and the options you choose, but the common benefit of SQL Server 2000 replication is the availability of data when and where it is needed.

Other benefits include:

Allowing multiple sites to keep copies of the same data. This is useful when multiple sites need to read the same data or need separate servers for reporting applications.


Separating OLTP applications from read-intensive applications such as online analytical processing (OLAP) databases, data marts, or data warehouses.


Allowing greater autonomy. Users can work with copies of data while disconnected and then propagate changes they make to other databases when they are connected.


Scale out of data to be browsed, such as browsing data using Web-based applications.


Increasing aggregate read performance.


Bringing data closer to individuals or groups. This helps to reduce conflicts based on multiple user data modifications and queries because data can be distributed throughout the network, and you can partition data based on the needs of different business units or users.


Using replication as part of a customized standby server strategy. Replication is one choice for standby server strategy. Other choices in SQL Server 2000 include log shipping and failover clustering, which provide copies of data in case of server failure.

How to use WinControl in ASP.Net

//Create Windows User Control with this Code//

using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Drawing;
using System.Data;
using System.Text;
using System.Windows.Forms;
namespace BEST
{
public partial class Main : UserControl
{
string _Title = "";
public Main()
{
InitializeComponent();
}

private void button1_Click(object sender, EventArgs e)
{
MessageBox.Show(this.Title, "Msg", MessageBoxButtons.OK, MessageBoxIcon.Information);
}
public string Title
{
get { return _Title; }
set { _Title = value; }
}
}
}

//Designer Code//*************************************************

namespace BEST
{
partial class Main
{
///
/// Required designer variable.
///

private System.ComponentModel.IContainer components = null;
///
/// Clean up any resources being used.
///

/// true if managed resources should be disposed; otherwise, false.
protected override void Dispose(bool disposing)
{
if (disposing && (components != null))
{
components.Dispose();
}
base.Dispose(disposing);
}
#region Component Designer generated code
///
/// Required method for Designer support - do not modify
/// the contents of this method with the code editor.
///

private void InitializeComponent()
{
this.test = new System.Windows.Forms.Button();
this.SuspendLayout();
//
// test
//
this.test.Location = new System.Drawing.Point(64, 65);
this.test.Name = "test";
this.test.Size = new System.Drawing.Size(75, 23);
this.test.TabIndex = 0;
this.test.Text = "button1";
this.test.UseVisualStyleBackColor = true;
this.test.Click += new System.EventHandler(this.button1_Click);
//
// Main
//
this.AutoScaleDimensions = new System.Drawing.SizeF(6F, 13F);
this.AutoScaleMode = System.Windows.Forms.AutoScaleMode.Font;
this.Controls.Add(this.test);
this.Name = "Main";
this.Size = new System.Drawing.Size(206, 132);
this.Load += new System.EventHandler(this.UserControl1_Load);
this.Click += new System.EventHandler(this.Main_Click);
this.Paint += new System.Windows.Forms.PaintEventHandler(this.Main_Paint);
this.ResumeLayout(false);
}
#endregion
private System.Windows.Forms.Button test;
}
}

//Add below code under body tag of Your web page//

//Remember in the classid section after # is Namespace and your control name is the case sensative//

<object classid="BEST.dll#BEST.Main" style="width: 352px; height: 224px">
<param name="Title" value="Deepak Jain" />
</object>


//Also you can use this object in any td of page table and alsoe param is the parameter that send from your page//

//Also you can use this

RAID

RAID (redundant array of independent disks) is a disk system that comprises multiple disk drives (an array) to provide higher performance, reliability, storage capacity, and lower cost. Fault-tolerant arrays are categorized in six RAID levels, 0 through 5. Each level uses a different algorithm to implement fault tolerance.
Although RAID is not a part of Microsoft® SQL Server™ 2000, its implementation can directly affect the way SQL Server performs. RAID levels 0, 1, and 5 are typically used with SQL Server.

Note RAID is available only on Microsoft Windows NT 4.0 and Microsoft Windows 2000.
A hardware disk array improves I/O performance because I/O functions, such as striping and mirroring, are handled efficiently in firmware. Conversely, an operating system–based RAID offers lower cost but consumes processor cycles. When cost is a consideration and redundancy and high performance are required, Microsoft Windows® NT® stripe sets with parity or Windows 2000 RAID-5 volumes are a good solution.
Data striping (RAID 0) is the RAID configuration with the highest performance, but if one disk fails, all the data on the stripe set becomes inaccessible. A common installation technique for relational database management systems is to configure the database on a RAID 0 drive and then place the transaction log on a mirrored drive (RAID 1). You can get the best disk I/O performance for the database and maintain data recoverability (assuming you perform regular database backups) through a mirrored transaction log.
If data must be quickly recoverable, consider mirroring the transaction log and placing the database on a RAID 5 disk. RAID 5 provides redundancy of all data on the array, allowing a single disk to fail and be replaced in most cases without system downtime. RAID 5 offers lower performance than RAID 0 or RAID 1 but higher reliability and faster recovery.