Of course it’s rather simply to find something which is lighter that DataSets and which provides us data from database: data readers. They are light, forward-only, but they have one disadvantage: they’re connected with data provider which are specific to databases. So it means that using System.Data.SqlClient clause will appear in code-behind again.
       We can use one data reader which is common to all databases. It’s OleDbDataReader, but using it bereave us efficiency which comes from specific to database data reader. So it’s not that way.
       Let’s incorporate data readers first. Take a look at changed DAL class (in SaveSetting function we’ve made no changes):

public class DAL
{
 public static SqlDataReader LoadDllValues()
 {
  SqlConnection connection = new SqlConnection(ConnectionString.Text);
  string selectCommand = "SELECT * FROM [Values] ORDER BY ValueName";
  SqlCommand sqlCommand = new SqlCommand(selectCommand, connection);
  connection.Open();
  SqlDataReader dr = sqlCommand.ExecuteReader(CommandBehavior.CloseConnection);
  return dr;
 }

 public static SqlDataReader 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);
  return dr;
 }
}