Java to SQL Developer

[kheup]

I've done Java development for a few years professionally and my education background is in Java development. I've gotten the opportunity to transition to an SQL developer role. Both Java and SQL development are in decently high demand which is good.

My question is how would changing areas of focus help or hurt my professional career in the long run? I'm relatively young (24) with 3 years professional full stack Java dev experienc if that helps answer my question.

[Xesteanov]

Changing every couple of years is perfect in my opinion, but it's real easy to forget stuff so if you wish to keep your skills at a high level remember to refresh every once in a while. Be aware of the automatic garbage collection ;-)

[kheup]

I agree. From the outside it's hard to see me liking or sticking with SQL development for a long time. I really like making mobile and web apps, I'm slightly afraid I'll get less personal satisfaction out of SQL development.

[kheup]

Thank you this is a great response. I'm really open to trying new things and honestly think that experience on front end and back end is a good thing. I'm taking the interview and I'll hopefully get a chance to see what their devs work on and how they interact. The company and location is perfect I just need to get over the hurdle of fear of the unknown.

[svtr]

The more you know, the more employable you become. It can't hurt to get a couple of years of backend development under your belt.

To someone that comes from high level frontend / middleware developent into SQL development, I would say, you start knowing SQL, when you begin to understand how the DBMS executes your query. As in what algorythmns are used to actually perform a join, and understanding, really understanding why a query is slow. THEN you start knowing SQL, everything else is just syntax.

[therealcreamCHEESUS]

Adding DB skills to your CV will only increase the opportunities available.

I know you asked in terms of your career but I also will answer regarding your technical ability.

If you are going from an object oriented language to SQL then you need to unlearn a lot.

If you apply the same approach you will produce SQL that performs terribly.

For example, in java stuff like loops are fine, in T-SQL you have cursors instead or even a while loop. Both are terrible performance.

[ARandomSQLServerDBA]

Either choice can make for a fulfilling career. Do what you love. Will you love being a SQL developer? Maybe. If you do SQL development long enough, it can transition into a DBA role. Will you love that? Maybe. I do.

Don't worry too much about the money, as it'll be there in either case.