My experience is very different and very similar. I came into the DBA role through development and I'm a classic accidental DBA. The struggle is to both define your role and ensure that within that definition you're acting in the best interests of the organization, not simply doing what you've been told (although that's sometimes your only option). To a degree, they're counting on you to be able to bring them the important questions that need asking for a broader strategic understanding of data, protection, privacy, availability, etc. because you're the subject matter expert (whether you consider yourself that or not). Fight through the imposter syndrome that is natural here and do what you can. Just try to avoid getting to stuck in the weeds of "This bloody import has a comma in the wrong place" kind of thing. A lot of that comes with the job, but it shouldn't define the job.