Re: The Hot Shot Database Team
Databases are great fun, despite the perception that they're all just data black boxes and can all be treated the same they are most certainly not and they all have their own little foibles which you only learn as you crank up the demands.
1. SQL Server developers not used to Oracle. SQL server will auto-commit non-transactional DML, Oracle will not by default. 3 hours of loading data only to find no data has been pushed through.
2. Disabling auto-commit on Oracle processes to speed up the processing, then either blowing the trx undo segments or forgetting the final commit and losing all the inflight data.
3. Developers committing after every single DML operation on Oracle on millions of DML ops and wondering why the process runs like a 2 legged dog against the wind! ( If anyone dosn't know why then I suggest you learn about Oracle's redo log writer mechanism very quickly! )
4. Tripping over their own feet during looped DML code and wondering why something as simple as single update inside a loop with commit will keep failing no matter how huge the database memory, CPU and rollback/undo segsments are made. This one is bloody good fun with developers, they scream and rant about it, demand more resources, more money be spent and all you can do is keep calm and keeping pointing them to the Oracle docs about 1555's as there's absolutely nothing that will fix it other then fixing the code!
Biting the hand that feeds IT
