We are dealing with the split of work which, in the old process, would have all been one big task; Now, (under Scrum) that work is split into stories and refined. We are using BDD to define those stories...
For one particular set of stories - those involved with a particular system - the changes to the system have always been defined in a particular manner. The team members are familiar with it and I am finding it difficult to convert those definitions into BDD. (Also, I do not understand the work they do as it is not in "my wheelhouse".)
I have discussed the BDD approach which the project is now taking with the person (as it happens, a technical BA) responsible for writing/refining those stories and while they are happy with BDD for most of our stories, informs me that it is difficult to do what I am asking; Converting to BDD for this particular system.
The task definitions, generally, involve defining the storage of database-like data and schemas, the nature of requests and responses into and out of the system to get that data and changes to the existing setup.
To be fair, if this were work defining changes to an existing MS T-SQL database I would also find it difficult to provide BDD stories.
TL;DR: How should one define BDD stories which specify technical changes to systems such as databases using gherkin? Is this even the appropriate approach?