It’s extremely simple class with 1 constructor and 2 properties for reading data. Now let’s rewrite LoadSetting function.

public static ArrayList LoadSetting(string settingId)
{
 SqlConnection connection = new SqlConnection(ConnectionString.Text);
 string selectCommand = "SELECT * FROM Settings1 WHERE SettingId = @SettingId";
 SqlCommand sqlCommand = new SqlCommand(selectCommand, connection);
 sqlCommand.Parameters.Add(new SqlParameter("@SettingId", SqlDbType.Int, 4));
 sqlCommand.Parameters["@SettingId"].Value = settingId;
 connection.Open();
 SqlDataReader dr = sqlCommand.ExecuteReader(CommandBehavior.CloseConnection);
 ArrayList settings = new ArrayList();
 while(dr.Read())
  settings.Add(new DataBroker(dr["SettingName"].ToString(), dr["ValueId"].ToString()));
 dr.Close();
 return settings;
}

       And btnLoad_Click function.

private void btnLoad_Click(object sender, System.EventArgs e)
{
 ArrayList settings = DAL.LoadSetting(txtNumber.Text);
 DataBroker db = (DataBroker)settings[0];
 txtSetting.Text = db.SettingName;
 ddlValue.SelectedValue = db.SettingValue;
}

       The most important thing is that using System.Data.SqlClient clause disappeared from code-behind again and using System.Collection clause appeared, but from porting point of view it doesn’t matter. Loading arise from creating ArrayList can be omitted.
       On the end I’ve to mention that code presented in LoadSetting function is not what I use in development; it was only for presentation reason. For everyday work I use Microsoft.ApplicationBlocks.Data component and I invite to become familiar with this solution.