Java and Database Question Career

[mmt4331]

I'm learning java currently for a career change down the road. I do know SQL very well. My question is, do most Java positions require you to have Oracle or SQL Server experience? I have experience writing ad-hoc queries against DB2...but I don't think that is going to cut it.

Most positions in Java that I looked at (ex. Monster) don't require you to know databases. Is this true?

Also, since I am VERY NEW at Java, I know it is used for web applications (for example - applets). Anything else? I know I'm showing my ignorance here. Thx.

 

[palbano]

>> I know I'm showing my ignorance here

I think those are very reasonable questions for this forum.

If your just starting Java I would not worry about Database specific knowledge. Actually JDBC is relatively simple once you have a good grasp of java and have even minimal knowledge of how SQL and databases work.

As far as requirements for a specific job, sure that could happen, but I would think even mild experience such as yours with databases would prove enough given the right level of Java knowledge.

As far as what Java is used for besides Applets in web pages. Applets in web pages are probably one of the least used areas in Java. Most of the momentum is in developing server side code. Middleware in Application Servers for things like web development (Servlets, JSP), legacy application integration, workflow, messaging, e-commerce etc. There is also some activity in the mobile/wireless application space but that is probably minor in comparison.

I have not been looking much recently but I think you will find lots of mention of J2EE experience in job postings. Sometimes even a specific Application Server is requested. Since J2EE is a standard one should not need a lot of specific product experience but the App Server products tend to, ummm… do their own thing, yeah same complaint about Microsoft… ssshhhhh don’t say that to loud, oh boy now I’m in trouble! LOL

One thing to keep in mind is that XML is fairly pervasive in server side development these days so experience with XML and the XML DOM and Parsers in Java might also prove useful.

I don’t know if that helps but there it is.

Good luck
-pete

 

[TWillard]

There are no stupid questions!
However, there are stupid answers!

If you can right ad hoc sql queries, you are on the right path. I think you could quickly adapt to either Oracle or SQL Server. Your DB2 experience could be benificial as a core Java developer. DB2 which is an IBM product and IBM is fully behind the java language.

I think it would be very tough to be the only sql administrator in a company. SQL is something that is simple to get started in. To become a SQL expert, you can gain alot more knowledge by working with someone. So when looking for a job, I would make sure that you would not have to be the only sql administrator. However, most shops of any size that are currently using databases will already have someone in place working with them.

As far as learning Java, I think it is best to look at it as a middleware product. So know your Java API, but also learn other operating systems, features functions, databases and think of how Java can tie all of these together.

 

[dilettante]

I'm not even sure J2EE environments use JDBC for most database access. Since J2EE is an incomplete specification, and not a product (and certainly not a standard), I wouldn't be surprised to find that proprietary database interfaces are used in most real J2EE applications.

Since SQL isn't SQL either (more extensions, different for each database vendor) but will continue to be important for some time, you might want to focus in there a bit too. IBM is one of the big J2EE players now, and DB2 figures prominently in their vision.

I'd guess that anybody specifiying J2EE jobs in an IBM shop is assuming WebSphere/DB2. When their J2EE product vendor is BEA the assumed target is probably Oracle or SQL Server, and for Sun probably Oracle most of the time. This may be one of the few areas where a J2EE shop has a choice however: when you buy one J2EE you have bought into a lot of vendor-lock, but you may have some choice in databases.

Your SQL and especially DB2 experience ought to be worth a lot, but you need more than ad hoc query background. Look into the full range of DDL and DML SQL commands DB2 supports. Java isn't a middleware product, that's where stuff like WebSphere or WebLogic come in. Where Java fits in is that it is the only programming language you'll ever need. Better hope so, 'cause it's the only one you can use with J2EE.

I don't think there are too many jobs out there for people writing client-side Java applets anymore though. Are you sure these job postings aren't implying a specific J2EE implementation? That's the tough part. Think of J2EE as a whole ball of stuff on the order of CICS and other environmental software.

 

[Polu]

Hello mmt4331.

Windows/IE(client) + J2EE/Weblogic/Solaris(app server) + Bea Tuxedo/HP-UX(Middleware) + Oracle/Compaq Tru64(DB) is an example of a common macro architecture. So, think in J2EE as an app server level tool, not as a whole solution tool.

If you want to be more "employable", learn about J2EE/Middleware (Tuxedo, Tibco, MQ, etc) interfacing, and not only about J2EE/DB interfacing.

I hope it helps!

Regards.

Polu.