using soap arrangement gunk operations

is exposing gunk operations by soap web services bad idea? instinct tells me slightest since over doing database calls over huge. i'm struggling support for/against (anti)pattern i wondering anyone indicate me support an opinion matter.

also, anyone knows best practises (and/or support effect) conceptualizing soap services, great.

here's an instance web use look:

• create


• delete


• execute


• fetch


• update

and here's doing feeling like:

[webmethod]
public byte[] fetch(byte[] requestdata)
{
    selectrequest ask = (selectrequest)deserialize(requestdata);

    dbmanager crudmanager = new dbmanager();
    vigilant outcome = crudmanager.select(request.objecttype, request.criteria);

    relapse serialize(result);
}