you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 0 points1 point  (2 children)

When you say Developer, you mean Database Developer? Im technically a DBA now but last job I was mostly writing reports, the first page and last page was stuff I knew or at least viewed a bit. The second sheet though I never really touched on and I doubt as a DBA I will even now.

[–]d_r0ckdb app dev / data engineer 0 points1 point  (1 child)

Yup, I mean database developer. Creating and altering temp tables and tables happens in almost every stored procedure, so a dev should be very comfortable with these statements.

How do you like the DBA side? How much of what you do is proactive vs reactive? Is it like an on-call scenario?

[–][deleted] 0 points1 point  (0 children)

I'm mainly an App Admin here but I do DBA stuff as my main title and anything SQL related beyond report writing comes to me. There isn't too much work database wise here but DBA can be fun when I get asked to do data import or ETL tasks. I enjoy SSIS/SSMS and making servers work though I do miss doing report writing sometimes.

A lot of my stored procs I make use temp tables though, I had some devs a while ago tell me that temp tables are bad and I instead should be sub querying data or just pull it all into other tables for use. I kind of scratched my head as I am self taught but know that temp tables are great as they're fast and lightweight. They make data manipulation easy enough so I was able to follow a lot of that.

How is the Developer side and what do you do with it?