I've seen loads of answers to this sort of question on this and other forums. I guess it comes down to what you consider a DBAs role. If you think a DBA is present to create tables, size extents, manage memory allocations, manage rollback and extend datafiles then that role is certainly coming to an end. Those sort of task are either not necessary anymore or can be done by developers.

If on the other hand you think the DBA job involves helping developers and designers understand the best ways to use the technology, along with all the other day-to-day stuff that still remains, then I think that role will be around for some time to come.

In my own case, as well as the "traditional" DBA work I'm also involved in development and design decisions, performance tuning of bad application code, management of the application server layer etc. A few year ago this would never have been considered DBA territory. Now I believe it's standard for alot of people out there.

Why do I have time to do this? Because I don't spend all day worrying about rollback segments anymore

Cheers

Tim...