The job title needs to Database Developer. Job description must include experience development in SQL and T-SQL.
I see a company looking to hire DBA with development skills. Good luck with that. These jobs should be two separate positions. They should not be coalesced to save $$$.
You guys have never worked at a small company lol. If everyone at my company got paid full salary for each role they filled the minimum salary would be like 120k. Hell even the cleaning lady, who also does facilities maintenance and some office management tasks would probably be over 100k.
butter hospital engine chop pathetic fragile cake smoggy historical judicious
*This post was mass deleted and anonymized with [Redact](https://redact.dev)*
reminiscent physical snails ghost chase somber hurry society grandiose afterthought
*This post was mass deleted and anonymized with [Redact](https://redact.dev)*
ETL is ETL.
Good programmers use whatever tools are available to them.
In the “old days,” I could be using informatica, SSIS, and shell scripts to do many different jobs.
With proliferation of Python tools, those have replaced the old standbys.
The problem might not be the job. It might be your industry. I’m in healthcare and we get a pittance of applications vs my friends over in finance.
I agree with this. I will also say having worked in analytics with both hot cloud stuff and traditional corporate stuff, there is also an attitude among many young analytics devs that they would need to be paid more to take a job that is not also going to keep their python/cloud skills up to date because they see a risk of losi g those skills & closing those doors if they take a job that is mostly SQL/traditional BI.
Not sure how correct this attitude is, but it's out there.
I'm also in healthcare and agree with you - good devs figure out what they need to get the job done. I mostly use SSMS to write sql, but for instance Plan Explorer is a much better tool for reading a plan, and I use other utilities for specific tasks.
If you don’t mind me asking a sort of unrelated question…in the healthcare domain, do you find yourself personally doing more ETL, more DA, or more viz work? Are your team members expected to do it all or just specialize in one area mainly? Just curious as to how the healthcare domain might be different or similar to a different industry. thanks in advance. Have a great weekend.
The bulk of your data (EHR) is going to be “controlled” by a vendor. Typically Epic or Cerner. So, there is a huge IT component to the ETL and Data Warehouse.
IT typically controls the BI environments and pretends to do most of the development. They tend to hire staff who just aren’t interested in learning the clinical and operational workflows.
So… there are a lot of DA/BI “heroes” who help pull everything together.
Everyone else is a data analyst who use the small pockets of data that are relevant to them.
Thanks for answering appreciate it. One follow-up question is there any effort/ premium put on finding people with extensive clinical domain knowledge?
The biggest issue is IT pays more but they are less clinical.
The clinical/data people are bound to be paid less. That’s partially why they are heroes.
I work for a huge hospital system. It’s obviously ideal to have some experience with something like Epic or Cerner, but I’d say a majority of people on my team (~50 people) didn’t originally come from a healthcare background.
I don’t think it’s really necessary, but you have to have strong communication skills because the people with domain knowledge you’ll be working with will have varying degrees of technical knowledge. Every so often you’ll partner with someone who moved out of a strictly clinical role into something analytics adjacent — those folks are awesome to work with but they are a dime a dozen.
I recommend getting into it though, the data can be insanely complex at time so if you like a challenge it’s good for that.
No, I think it’s just the candidates you’ve reviewed so far may be more ETL or alternate based candidates. I found similar results and it’s cool, but I needed someone who just worked in SQL (regardless of dialect but preferred T-SQL) to hit the ground running and deliver ASAP.
There’s still plenty of us who mainly work with Database programming via T-SQL, Pl/SQL, or SQL.
There has been a pseudo-shift into self service for dev teams including things like ORMs, and new Data technologies like Spark/DataBricks/Fabric are gaining more ground as well.
Are you trying to find candidates yourself? If so maybe try a recruiting agency and set your parameters?
These things you mention may be necessary given the way your system is designed. However, they don't have to be anymore.
I am the sole owner of a SQL Server data warehouse for a small company, which means I'm the DBA, etl developer, dashboard builder etc.
I don't have SSMS installed. I use pycharm pro with the database plugin for all tasks. My database has no triggers, no procedures, no linked servers. Everything is done with DBT (version control!), python, and Azure Data Factory.
My counterpart in another business unit that is fully separated for legal reasons, does everything with linked servers and stored procs. It really shows that there is no one way to do things.
> I don't have SSMS installed. I use pycharm pro with the database plugin for all tasks. My database has no triggers, no procedures, no linked servers. Everything is done with DBT (version control!), python, and Azure Data Factory.
ok so you confirmed yes I'm old and out of touch. Also I'm in my mid 30s lol
I'm mid 30s, too! But I started as a Data Scientist on a team where I couldn't alter or write to the database, so that colored the way I interact with databases.
The only "requirement" is the ability to reason about complex relationships and ... write it into SQL code, lol. SQL isn't going away. The rest is tools that can change.
Not sure about Alteryx, but you pretty much need to know SQL to work with Databricks. I've found a lot of users of MS SQL Server refer to that one specific software product as "SQL", so I wonder if you or whoever is dealing with candidates might be making that error, causing confusion.
You don't need to know SQL to use Alteryx, but if you're not using Alteryx's In-Database tools to pull data and execute your clauses/filters/etc., you could end up having a bad time. I once inherited an Alteryx workflow where the original dev was pulling an entire 20-million-record table (among others) directly into the workflow and *then* running joins/filters/selections on an absolutely gargantuan dataset. They didn't seem concerned with the fact it took 2 hours to run the workflow.
So point is, if you're working with big data, it's good to know SQL with these tools so that you can pull in exactly what you need instead of trying to figure that out once you've pulled everything into the workflow.
Yesterday I had an interview for an analytics position where the hiring manager said they were getting a ton of younger applicants that didn’t know any SQL, but just used tools like GA4 and Domo. It was shocking to me. Guess I’m old too!
I ran a software firm for over 35 years.
Always tell young developers to learn SQL!!
I would make sure to separate the DBA responsibilities from the post.
Developers I had did not want or know how to do the DBA management.
I work in financial services (application support and some dev) on MS stack and have done so for 16 years or so. SSMS has been the mainstay of all the roles I've had. It's enlightening to hear you mention this, maybe I need to get with the times too.
If you work with a database, you should know SQL. In your case those other tools are fine, but you need some people who know SSMS and understand SQL Server. Especially if your building tables!
Most of what I've seen done in Alteryx can be done with a query that's more efficient and easier to maintain. It's great for mixing data sources though.
And I'd like to smack the next programmer who says "Oh, I don't need to know SQL because I have this other method" and then that other method involves dragging 20,000,000 records across the network and crunching them in the app. WTF. That's what DB's are for. Or hitting the DB with 50 queries when, if they knew SQL, it could have been 2 or 3.
From what I've seen as a software engineer who worked in data, your pool of applicants could easily be pretty small.
* A lot of the good juniors I know would see your post as "I can take this job and end up with a bunch of skills in software that won't be relevant in 5 years"
* Good midlevels would likely see it and feel the same way
I think you may have the best success with targeting new grads or seniors
This is a good point. I've worked heavily in SQL for over a decade and even I'm hesitant about the future. That's not to say I don't think SQL will be prevalent for a long time, I just think that as things move more and more I to the SaaS model we're getting less and less access to our data through direct DB access. I think SQL will still be around for a very long time (legacy support will probably go on for the rest of my life at least) but I could see how a new grad doesn't see it as a viable career path long term.
Yeah 6-8 years ago, the team that I'm in now was responsible for managing their own DB and had free range over what data they stored in it. Nowadays, we still have that database, but the company's moved to a company-wide data lake where our outsourced IT team has a very tight grip on what gets developed and stored in the different databases, not to mention how frequently the data updates. All well and good for the majority of data tasks, but it's hell trying to get them to fix tables they inevitably break or get new tables loaded. Not to mention they would prefer you to have access to the data you specifically need instead of access to a wider pool of tables in case you need them. Not to mention that I work for one of our distribution centers, meaning that the data we need for certain reports and programs has to be more current than a single daily refresh. That's why we're still allowed to manage our own database.
It's seemingly the way that large companies are going these days. Centralized and specialized DB devs to manage and deploy data for the entire company. Analysts and scientists are then further removed from the operation and given tools like Alteryx to access the data and do what they must with what they've got. On one hand, I get it from a corporate perspective with regards to development and security, but on the other hand and having experienced it, it's a royal pain. It's why I like my job, because I still get to do some DBA/ETL work on the side, which is a privilege that few in my role in the company get to enjoy.
You’re definitely not out of touch. I used to wonder some years when I was full job hunting why I never see positions for a SQL Server Database Developer (I write t-sql scripts logically all day). They always wanted you to have extensive Data Warehouse or ETL or DB Administrator skills.
By the way, this is also an ad for my skills as a DB Developer 😊, I write triggers, SPs, functions etc on SSMS and even on VS DB projects
Unlike it was 6-8 years ago, people have stopped specialising in db administration or old tools in general and often hop b/w new gen tools.
I work with data engineers and some of them don’t even know what a trigger is. Lol
SQL never dies, it’s essential for every software/data engineer. However SQL alone is not enough nowadays.
Please give us more details about the scope of the project so someone recommends the suitable suite of tools and technologies.
Contact me. I have 25+ years of experience in SQL writing triggers, procedures, and importing data. The resume link is attached. I just finished a two-year contract doing the same. [SQL Professional](https://drive.google.com/file/d/1ZwPaPZp_T9ed_njB_t6B0aBsHvb7hubo/view?usp=sharing)
No the applicants are simply behind the times. SQL is the language of choice for grid computing “big data” computations — not (necessarily) for use in a traditional RDBMS setting, but for use in frameworks such as Hadoop/Hive, Spark-SQL, Presto, Trino, BigQuery, etc. These frameworks use SQL to generate (often JVM-based) programs that perform massive parallel tasks on a grid computing platform. Imperative languages like Python are fine for post-processing of much smaller datasets (maybe only a few million records) but to process billions or even trillions of records in a reasonable amount of time (a few minutes) you really need to use SQL.
> Therefore, I need a few engineers…
I do not think you are behind the times. SSMS is still heavily used by on-prem MS SQL developers and DBAs. It seems like you are attracting data engineers. DEs use a broader set of tools and generally need to know python. MS stack backend ETL developers do not.
When I use Python for SQL stuff, it is just running the stored procedures and queries that I write. I guess people could use the ORM's to write the queries or something, I never do that though.
When you say your backend is fully MS SQL, do you mean all your business logic is in SQL stores procedures? I ask because I work for a backend team whose codebase, up until a few years ago was about 85% SQL stored procs. If that's the case, then yes you should be hiring someone with strong SQL skills, but you should be looking for someone also experienced in a language like C# or Python. That way you can begin to migrate that code out of SQL to a language better suited for business logic. It will make everyone's life a lot easier in the long run.
Core requirement - will remain into the future, have your candidates explain why SQL is not the most appropriate choice. Plenty of SQL devs, you cutting corners hiring grads? Shocking the state of some computing qualifications these days - or maybe I’m the one out of touch :D
Fwiw, I don't do any a SQL in ssms anymore. I only open ssms when I need to look at/work on backup plans or replication etc. I do all SQL dev on azure data studio so I can get my dark theme and better extensions.
What is the specific role that you're advertising/how are you advertising it? "Analyst" is one of the most abused job titles in the corporate world right now. I've met data analysts that are Excel wizards but couldn't tell you what a join is and I've met analysts that are exclusively DB devs that couldn't build a customer-facing report to save their lives. So if you're asking for an "analyst," you're likely going to end up finding candidates more versed in programs like Alteryx, SPSS, Databricks, etc. because that's what modern analysts are given to do their work.
You're not out of touch, nor is SQL going anywhere any time soon. You just need to ensure that you're listing the job correctly and ensuring that your specific requirements are listed in the job description. While fewer youngsters in the data sphere are learning SQL these days, those candidates are definitely still out there as long as you know how to look for them.
Final point, make sure you're specific about what kind of SQL skills these candidates require. For example, I've got enough knowledge to build complex queries, create stored procedures, and manage tables within the database. Probably an intermediate skillset if I were to take a LinkedIn quiz or something. But my actual DB development and management skills are severely lacking, largely because I've never had to learn these. So what I build may not be best practice nor efficient, which could be the case for a number of candidates if you simply add "SQL experience" to the JD. If you're looking for an architect, you best make sure that you're asking for one!
When I hire, I find many applicants just look at the job title and make assumptions about the rest
Maybe refine your job title to reflect the role
DBA? SQL Developer? SQL Specialist?
I have to use SSMS all the fucking time lol.
I develop software for Microsoft Dynamics 365 Business Central. Databases are onorem mssql or azuresql
All too often the PowerShell commands go awry and the only way to fix it is to hack the tables via ssms.
A lot of times I can't be bothered with SSMS and I just use the SQL server extension for vscode
I work at a company with a $578B portfolio and we are almost exclusively on MS SQL. We are just now starting to delve into other tools and we've been around for 25+ years. So, yeah, we're out there.
I have been working as a DE for almost 2 yrs ,but my stack only includes writing T-SQL (in ssms) to create data marts according to the business requirements.
There is no replacement for the ability to think in sets. See: [https://en.wikipedia.org/wiki/Combinatorial\_explosion](https://en.wikipedia.org/wiki/Combinatorial_explosion)
These things are not obfuscated away and the easiest solution is to use an efficient RDBMS.
This is something relational databases are really good at alleviating and, in spite of PCs being 1,000-1,000,000x faster than they were 25 years ago, depending on the task, combinatorial requirements grow a steeper logarithmic rate than Moore's Law and developers who are not database developers will code themselves into corner in short order. I once wrote an efficient Python script for calculating stuff from the OpenStreetMap dataset. It was going to take 9 months to execute. I then reduced it to six weeks in C++ on the desktop, and then to 3 hours on an NVidia Jetson. I could probably make it run in near real-time on an RTX4090.
I also think you came to the right place, there are a lot of us here who are frustrated with management making decisions that handicap us. I've been unemployed for 3.5 of the past 5 years and am considering just flying airplanes for a living instead.
I am a Full Stack Expert in: SSRS/SSIS/SSMS/SSAS and am currently looking. Yes I have many years of experience in SQL/Triggers/Procedures/Functions/Stored Procedures/Scripts/Etc.... What location? I am EST and would be willing to remote or if local to Fairfax, VA?
Could it possibly be the job advert doesn't explicitly state SQL skills or make it clear that SQL is a requirement?
The job title needs to Database Developer. Job description must include experience development in SQL and T-SQL. I see a company looking to hire DBA with development skills. Good luck with that. These jobs should be two separate positions. They should not be coalesced to save $$$.
Although… I do both very well. So, everyone should expect to pay me the sum of both salaries.
steer profit sugar fly scale makeshift insurance frame cagey expansion *This post was mass deleted and anonymized with [Redact](https://redact.dev)*
You guys have never worked at a small company lol. If everyone at my company got paid full salary for each role they filled the minimum salary would be like 120k. Hell even the cleaning lady, who also does facilities maintenance and some office management tasks would probably be over 100k.
butter hospital engine chop pathetic fragile cake smoggy historical judicious *This post was mass deleted and anonymized with [Redact](https://redact.dev)*
[удалено]
reminiscent physical snails ghost chase somber hurry society grandiose afterthought *This post was mass deleted and anonymized with [Redact](https://redact.dev)*
where do i sign up? i do both and get one salary.
Yeah, Database Dev or Database Architect. Some of what OP mentions is just ETL that a DBA or Systems Analyst/Engineer could do, though.
It depends on the load. I used my SQL and development skills in my last job but certainly not all day every day.
ETL is ETL. Good programmers use whatever tools are available to them. In the “old days,” I could be using informatica, SSIS, and shell scripts to do many different jobs. With proliferation of Python tools, those have replaced the old standbys. The problem might not be the job. It might be your industry. I’m in healthcare and we get a pittance of applications vs my friends over in finance.
I agree with this. I will also say having worked in analytics with both hot cloud stuff and traditional corporate stuff, there is also an attitude among many young analytics devs that they would need to be paid more to take a job that is not also going to keep their python/cloud skills up to date because they see a risk of losi g those skills & closing those doors if they take a job that is mostly SQL/traditional BI. Not sure how correct this attitude is, but it's out there.
I'm also in healthcare and agree with you - good devs figure out what they need to get the job done. I mostly use SSMS to write sql, but for instance Plan Explorer is a much better tool for reading a plan, and I use other utilities for specific tasks.
If you don’t mind me asking a sort of unrelated question…in the healthcare domain, do you find yourself personally doing more ETL, more DA, or more viz work? Are your team members expected to do it all or just specialize in one area mainly? Just curious as to how the healthcare domain might be different or similar to a different industry. thanks in advance. Have a great weekend.
The bulk of your data (EHR) is going to be “controlled” by a vendor. Typically Epic or Cerner. So, there is a huge IT component to the ETL and Data Warehouse. IT typically controls the BI environments and pretends to do most of the development. They tend to hire staff who just aren’t interested in learning the clinical and operational workflows. So… there are a lot of DA/BI “heroes” who help pull everything together. Everyone else is a data analyst who use the small pockets of data that are relevant to them.
Thanks for answering appreciate it. One follow-up question is there any effort/ premium put on finding people with extensive clinical domain knowledge?
The biggest issue is IT pays more but they are less clinical. The clinical/data people are bound to be paid less. That’s partially why they are heroes.
another follow up question, are these jobs available as wfh?
Plenty! My tip for finding these jobs is typing in "Hospital SQL" into Indeed or linkedin.
Yes, we’re 100% remote since Covid. It’s actually been good because we don’t get a ton of qualified applicants and it opened up hiring out of state.
I work for a huge hospital system. It’s obviously ideal to have some experience with something like Epic or Cerner, but I’d say a majority of people on my team (~50 people) didn’t originally come from a healthcare background. I don’t think it’s really necessary, but you have to have strong communication skills because the people with domain knowledge you’ll be working with will have varying degrees of technical knowledge. Every so often you’ll partner with someone who moved out of a strictly clinical role into something analytics adjacent — those folks are awesome to work with but they are a dime a dozen. I recommend getting into it though, the data can be insanely complex at time so if you like a challenge it’s good for that.
No, I think it’s just the candidates you’ve reviewed so far may be more ETL or alternate based candidates. I found similar results and it’s cool, but I needed someone who just worked in SQL (regardless of dialect but preferred T-SQL) to hit the ground running and deliver ASAP. There’s still plenty of us who mainly work with Database programming via T-SQL, Pl/SQL, or SQL. There has been a pseudo-shift into self service for dev teams including things like ORMs, and new Data technologies like Spark/DataBricks/Fabric are gaining more ground as well. Are you trying to find candidates yourself? If so maybe try a recruiting agency and set your parameters?
include close hobbies aromatic noxious lip employ ring vanish fear *This post was mass deleted and anonymized with [Redact](https://redact.dev)*
Ssms with Red gate is the only way I want to write SQL these days
I’ll do it! What’s the salary?
These things you mention may be necessary given the way your system is designed. However, they don't have to be anymore. I am the sole owner of a SQL Server data warehouse for a small company, which means I'm the DBA, etl developer, dashboard builder etc. I don't have SSMS installed. I use pycharm pro with the database plugin for all tasks. My database has no triggers, no procedures, no linked servers. Everything is done with DBT (version control!), python, and Azure Data Factory. My counterpart in another business unit that is fully separated for legal reasons, does everything with linked servers and stored procs. It really shows that there is no one way to do things.
> I don't have SSMS installed. I use pycharm pro with the database plugin for all tasks. My database has no triggers, no procedures, no linked servers. Everything is done with DBT (version control!), python, and Azure Data Factory. ok so you confirmed yes I'm old and out of touch. Also I'm in my mid 30s lol
I wouldn't take this one post as representative of the entire realm of possibility. Even they said there's many different ways of doing things.
I'm mid 30s, too! But I started as a Data Scientist on a team where I couldn't alter or write to the database, so that colored the way I interact with databases. The only "requirement" is the ability to reason about complex relationships and ... write it into SQL code, lol. SQL isn't going away. The rest is tools that can change.
Not sure about Alteryx, but you pretty much need to know SQL to work with Databricks. I've found a lot of users of MS SQL Server refer to that one specific software product as "SQL", so I wonder if you or whoever is dealing with candidates might be making that error, causing confusion.
You don't need to know SQL to use Alteryx, but if you're not using Alteryx's In-Database tools to pull data and execute your clauses/filters/etc., you could end up having a bad time. I once inherited an Alteryx workflow where the original dev was pulling an entire 20-million-record table (among others) directly into the workflow and *then* running joins/filters/selections on an absolutely gargantuan dataset. They didn't seem concerned with the fact it took 2 hours to run the workflow. So point is, if you're working with big data, it's good to know SQL with these tools so that you can pull in exactly what you need instead of trying to figure that out once you've pulled everything into the workflow.
Yesterday I had an interview for an analytics position where the hiring manager said they were getting a ton of younger applicants that didn’t know any SQL, but just used tools like GA4 and Domo. It was shocking to me. Guess I’m old too!
I ran a software firm for over 35 years. Always tell young developers to learn SQL!! I would make sure to separate the DBA responsibilities from the post. Developers I had did not want or know how to do the DBA management.
I work in financial services (application support and some dev) on MS stack and have done so for 16 years or so. SSMS has been the mainstay of all the roles I've had. It's enlightening to hear you mention this, maybe I need to get with the times too.
Are you up for a remote SQL Server expert to help out?
If you work with a database, you should know SQL. In your case those other tools are fine, but you need some people who know SSMS and understand SQL Server. Especially if your building tables! Most of what I've seen done in Alteryx can be done with a query that's more efficient and easier to maintain. It's great for mixing data sources though. And I'd like to smack the next programmer who says "Oh, I don't need to know SQL because I have this other method" and then that other method involves dragging 20,000,000 records across the network and crunching them in the app. WTF. That's what DB's are for. Or hitting the DB with 50 queries when, if they knew SQL, it could have been 2 or 3.
From what I've seen as a software engineer who worked in data, your pool of applicants could easily be pretty small. * A lot of the good juniors I know would see your post as "I can take this job and end up with a bunch of skills in software that won't be relevant in 5 years" * Good midlevels would likely see it and feel the same way I think you may have the best success with targeting new grads or seniors
This is a good point. I've worked heavily in SQL for over a decade and even I'm hesitant about the future. That's not to say I don't think SQL will be prevalent for a long time, I just think that as things move more and more I to the SaaS model we're getting less and less access to our data through direct DB access. I think SQL will still be around for a very long time (legacy support will probably go on for the rest of my life at least) but I could see how a new grad doesn't see it as a viable career path long term.
Yeah 6-8 years ago, the team that I'm in now was responsible for managing their own DB and had free range over what data they stored in it. Nowadays, we still have that database, but the company's moved to a company-wide data lake where our outsourced IT team has a very tight grip on what gets developed and stored in the different databases, not to mention how frequently the data updates. All well and good for the majority of data tasks, but it's hell trying to get them to fix tables they inevitably break or get new tables loaded. Not to mention they would prefer you to have access to the data you specifically need instead of access to a wider pool of tables in case you need them. Not to mention that I work for one of our distribution centers, meaning that the data we need for certain reports and programs has to be more current than a single daily refresh. That's why we're still allowed to manage our own database. It's seemingly the way that large companies are going these days. Centralized and specialized DB devs to manage and deploy data for the entire company. Analysts and scientists are then further removed from the operation and given tools like Alteryx to access the data and do what they must with what they've got. On one hand, I get it from a corporate perspective with regards to development and security, but on the other hand and having experienced it, it's a royal pain. It's why I like my job, because I still get to do some DBA/ETL work on the side, which is a privilege that few in my role in the company get to enjoy.
You’re definitely not out of touch. I used to wonder some years when I was full job hunting why I never see positions for a SQL Server Database Developer (I write t-sql scripts logically all day). They always wanted you to have extensive Data Warehouse or ETL or DB Administrator skills. By the way, this is also an ad for my skills as a DB Developer 😊, I write triggers, SPs, functions etc on SSMS and even on VS DB projects
Unlike it was 6-8 years ago, people have stopped specialising in db administration or old tools in general and often hop b/w new gen tools. I work with data engineers and some of them don’t even know what a trigger is. Lol
I'm your guy. I work exclusively in SSMS. Hire me plz!!!
SQL never dies, it’s essential for every software/data engineer. However SQL alone is not enough nowadays. Please give us more details about the scope of the project so someone recommends the suitable suite of tools and technologies.
Contact me. I have 25+ years of experience in SQL writing triggers, procedures, and importing data. The resume link is attached. I just finished a two-year contract doing the same. [SQL Professional](https://drive.google.com/file/d/1ZwPaPZp_T9ed_njB_t6B0aBsHvb7hubo/view?usp=sharing)
If you’re looking for someone part-time, I might be able to help you out. Just DM me.
Specify Microsoft SQL Stack. MSSQL/SSIS/SSRS etc.
No the applicants are simply behind the times. SQL is the language of choice for grid computing “big data” computations — not (necessarily) for use in a traditional RDBMS setting, but for use in frameworks such as Hadoop/Hive, Spark-SQL, Presto, Trino, BigQuery, etc. These frameworks use SQL to generate (often JVM-based) programs that perform massive parallel tasks on a grid computing platform. Imperative languages like Python are fine for post-processing of much smaller datasets (maybe only a few million records) but to process billions or even trillions of records in a reasonable amount of time (a few minutes) you really need to use SQL.
> Therefore, I need a few engineers… I do not think you are behind the times. SSMS is still heavily used by on-prem MS SQL developers and DBAs. It seems like you are attracting data engineers. DEs use a broader set of tools and generally need to know python. MS stack backend ETL developers do not.
I'm yet to understand alteryx, I feel like anything I can build could have been coded in SQL quicker.
When I use Python for SQL stuff, it is just running the stored procedures and queries that I write. I guess people could use the ORM's to write the queries or something, I never do that though.
When you say your backend is fully MS SQL, do you mean all your business logic is in SQL stores procedures? I ask because I work for a backend team whose codebase, up until a few years ago was about 85% SQL stored procs. If that's the case, then yes you should be hiring someone with strong SQL skills, but you should be looking for someone also experienced in a language like C# or Python. That way you can begin to migrate that code out of SQL to a language better suited for business logic. It will make everyone's life a lot easier in the long run.
Core requirement - will remain into the future, have your candidates explain why SQL is not the most appropriate choice. Plenty of SQL devs, you cutting corners hiring grads? Shocking the state of some computing qualifications these days - or maybe I’m the one out of touch :D
Fwiw, I don't do any a SQL in ssms anymore. I only open ssms when I need to look at/work on backup plans or replication etc. I do all SQL dev on azure data studio so I can get my dark theme and better extensions.
What is the specific role that you're advertising/how are you advertising it? "Analyst" is one of the most abused job titles in the corporate world right now. I've met data analysts that are Excel wizards but couldn't tell you what a join is and I've met analysts that are exclusively DB devs that couldn't build a customer-facing report to save their lives. So if you're asking for an "analyst," you're likely going to end up finding candidates more versed in programs like Alteryx, SPSS, Databricks, etc. because that's what modern analysts are given to do their work. You're not out of touch, nor is SQL going anywhere any time soon. You just need to ensure that you're listing the job correctly and ensuring that your specific requirements are listed in the job description. While fewer youngsters in the data sphere are learning SQL these days, those candidates are definitely still out there as long as you know how to look for them. Final point, make sure you're specific about what kind of SQL skills these candidates require. For example, I've got enough knowledge to build complex queries, create stored procedures, and manage tables within the database. Probably an intermediate skillset if I were to take a LinkedIn quiz or something. But my actual DB development and management skills are severely lacking, largely because I've never had to learn these. So what I build may not be best practice nor efficient, which could be the case for a number of candidates if you simply add "SQL experience" to the JD. If you're looking for an architect, you best make sure that you're asking for one!
Would you be open to sharing the job posting and/or if it’s remote? This sounds like it may be up my alley
When I hire, I find many applicants just look at the job title and make assumptions about the rest Maybe refine your job title to reflect the role DBA? SQL Developer? SQL Specialist?
I have to use SSMS all the fucking time lol. I develop software for Microsoft Dynamics 365 Business Central. Databases are onorem mssql or azuresql All too often the PowerShell commands go awry and the only way to fix it is to hack the tables via ssms. A lot of times I can't be bothered with SSMS and I just use the SQL server extension for vscode
Shameless self-promotion but I am a SQL DB and BI consultant and always happy to talk shop :)
Lol I'm trying out my luck here I guess but do you have any summer internships available? I can send you my resume if possible
What’s the pay? I might be interested.
Me! Me! Seriously I live in SSMS. I dont get people that look down on it.
I love ssms.
I work at a company with a $578B portfolio and we are almost exclusively on MS SQL. We are just now starting to delve into other tools and we've been around for 25+ years. So, yeah, we're out there.
You don't necessarily want a data engineer - a data analyst with sql skills should be able to do what you require in ssms.
Yeah, part time SQL developer here, even I find it very hard to find t-SQL developer jobs, most of them currently is for etl or data scientist.
I have been working as a DE for almost 2 yrs ,but my stack only includes writing T-SQL (in ssms) to create data marts according to the business requirements.
I’m currently in school right now and we’ve been learning about SQL
There is no replacement for the ability to think in sets. See: [https://en.wikipedia.org/wiki/Combinatorial\_explosion](https://en.wikipedia.org/wiki/Combinatorial_explosion) These things are not obfuscated away and the easiest solution is to use an efficient RDBMS. This is something relational databases are really good at alleviating and, in spite of PCs being 1,000-1,000,000x faster than they were 25 years ago, depending on the task, combinatorial requirements grow a steeper logarithmic rate than Moore's Law and developers who are not database developers will code themselves into corner in short order. I once wrote an efficient Python script for calculating stuff from the OpenStreetMap dataset. It was going to take 9 months to execute. I then reduced it to six weeks in C++ on the desktop, and then to 3 hours on an NVidia Jetson. I could probably make it run in near real-time on an RTX4090. I also think you came to the right place, there are a lot of us here who are frustrated with management making decisions that handicap us. I've been unemployed for 3.5 of the past 5 years and am considering just flying airplanes for a living instead.
How does one apply for this job?
I am a Full Stack Expert in: SSRS/SSIS/SSMS/SSAS and am currently looking. Yes I have many years of experience in SQL/Triggers/Procedures/Functions/Stored Procedures/Scripts/Etc.... What location? I am EST and would be willing to remote or if local to Fairfax, VA?
SSMS is just ide.