polsoul

A really good resource is the following book http://www.apress.com/us/book/9781484207611

Oracle Database Transactions and Locking Revealed Authors: Kyte, Thomas, Kuhn, Darl

It's Oracle-specific though, because of one of the authors(Tom Kyte , the Tom behind asktom.oracle.com not so long ago ) I highly recommend it.

Hi,

have you tried to verify that it's dead end. Oracle and SQL Server databases are pretty interesting technologies ... unfortunately, it all comes down to how these products are used. There are companies that use advanced features of these products and your input there might be invaluable, exploring and etc. might be challenging and fulfilliong work, helping others with database-related problems ... And there are other companies where the databases are just stopped/patched/started and nothing else. A DBA there could commit suicide out of nowhere :) I bet you know what I mean.

I'm just trying to say that being a DBA in another company could be a completely different story from being a DBA at the company you're currently in.

Wish you all the best and being happy with the changes you're going to make in the near future.

Not a particular link but openworld presentation of how Bank of America do it using Golden Gate, there was also Pythian blog post about it, I believe.

yep, sure, but a good programmer deserves such amount of money compared to other professions.

Way too many managers are to blame nowadays - I love when they say "No, no, no , I do not handle technical things , I manage people!". The IT industry is flooded with clueless(from technology perspective, I'm not talking about team tech leaders) managers who have no idea about the technology being used.

When one has no idea how to do a thing(in this case develop software) and has money, and needs it done, he's willing to pay way more to get it.

Update: even better - instead of "I manage people!" they say "I manage resources!".

Fully agree with you - there are problems and problems, and 'use the right tool for the right job' should always be the way to go.

hashtalbe or flat files,huh, hard to believe this is going to be useful for a non-trivial app as 'data storage engine'(so to say). You will have to implement everything yourself: - concurrency - several users updating one and the same entry - data consistency - to return the data as of the start of the 'select' for the user,what about others who updated the entry but still didn't commit. - security - fine grain access to specific data entries - what can be extracted by whom, what about auditing(who did what at what time and etc.) - backup/recovery and etc.

More code most of the time means more bugs. Not everyone is Google , Amazon or Facebook to have the resources to create good custom solutions and support, improve them.

For most cases, a simple rdbms database will provide you with enough 'standard' functionality to not reinvent the wheel(think security,concurrency,consistency and etc.) = to code these on your own from scratch.

But in the end, it's again the nature of the problem(whether at all you'll need security, concurrency or consistency and etc.). It's nice to know what the database as a tool gives you , and I don't think this is the case nowadays - too many java/.net, and many other developers , have no idea what they can get out of a database. And I really hate when one spent several weeks to write something that could be done in several hours by using a specific database feature.

Being a dba for a decade already, resolving issues similar to the ones you described, are the sweatest I've experienced in my professional career. Unfortunately, I don't believe that fixing the problem in the database by understanding and resolving it in a logical manner is the way things will be in the near future. You know, RDBMSs aren't sexy ... developers developers developers , web developers web developers web developers :) the newest API and/or language are much more important nowadays for the newcomers. I cannot believe it, it's out of my mind, but that's the reality. Noone wants to utilize the database at its fullness anymore, everything needs to be done at the gazilion of app servers by using java/.net or the trendy 3rd/4th generation language of the day.

My only hope is that the data is the thing that is not going away, and this forces us to think in a logical way about it(eventually devs/web devs will start doing the data maniplation and etc the right way, I guess you're pretty familiar with the approach in mind).

Thanks

Pretty easy to test it using:

http://sqlfiddle.com/ (just select Oracle 11g R2 instead of MySQL from the drop down -> press Build Schema -> paste the SQL statment into the right window -> Run SQL )

The great thing about it is that it's just one SQL statement.

One SQL statement with recursion ughhh, arghhhh ... a bit older but still quite complicated to me - I've spent many hours on it and still cannot fully understand how it works(this recursion thingy with all the university variables memories - i,k,j , do you remember them :)). Definitely a good brain teaser, good luck.