Jaish.
On the surface it looks like it's ok (not sure what the asterisks are).
However, if you're using Enterprise library 6 then none of that code is necessary.
You would want to configure your project to use a custom database using the Enterprise Library Configuration editor (in Visual Studio: right-click app.config or web.config/Edit configuration file v6).
Once you have your database provider configured the code would look something like this:
var db = new DatabaseProviderFactory().Create("the_name_you_gave_your_connection_string");
using (var cmd = db.GetStoredProcCommand("sp_name"))
{
db.DiscoverParameters(cmd);
// Set the parameter values either directly or through an IParameterMapper or an accessor.
// Here's an example of setting them directly:
cmd.Parameters["@P1"].Value = "some value";
// if you want to retrieve a DataSet:
using (var ds = db.ExecuteDataSet(cmd))
{
// ... do something with the returned data.
}
// If you just want to call the stored procedure:
db.ExecuteNonQuery(cmd);
}
Hope this helps,
Mike