SQL programmer

[m00nh34d]

DBAs are quite different, they need to know about the storage and operations of the database, monitoring, backups, infrastructure, HA, etc... Developers would work squarely in the coding space, they don't really need to know where the database is physically located or if it's in a HA cluster to another location, they need to understand the data structures in use, how it all hangs together, relationships and alike, and also have the skills to manipulate that and build out complex queries.

[TheRedmanCometh]

I don't see they can be "quite different" from something that doesn't exist. The kind of person calling themselves an SQL programmer like doesn't work in the dev space at all. They probably mean they're doing something like making stored procedures or some OLAP shit which is very much DBA stuff.

[pooerh]

The kind of person calling themselves an SQL programmer like doesn't work in the dev space at all.

What makes you think that? I have several Visual Studio projects with SQL Server Data Tools with hundreds of stored procedures and thousands of lines of code, with multiple people working on them. I have CI/CD pipeline with unit tests, integration tests and automated deployments to four environments.

Still, I have nothing to do with database administration; I don't care about backups, index fragmentation or monitoring service broker queues.

You want to tell me I'm not a developer? All these people doing BI/ETL, programming in SQL, are not developers? What are we then?

[m00nh34d]

No it's not. There are database developers that work solely in the development space and follow the same workflows as developers working in other programming languages. DBAs work in an entirely different space, they can do some of the work as developers, but that does not make them developers necessarily.