As a system integration engineer you need a broad range of skills. These skills are probably more likely to be defined by a breadth of knowledge rather than a depth of knowledge. Skills must include general software engineering (or plain coding…), knowledge about protocols, but most importantly general problem solving skills. Plus it helps if you can’t stand the words ‘I think that will never work’, because a lot of times it takes a fair bit of tenacity to pull it all together.
Ever wanted to improve a badly performing Oracle 11 database, or parts of it? How would you know for sure the performance improved for end users?
An Oracle database is a complex entity. It has all sorts of mechanisms to improve and optimize performance, like caching results, creating and caching execution plans, caching dictionaries, etc. When measuring query times, often the first attempt will take several seconds, while next attempts only takes a few milliseconds. That is because Oracle caches almost everything during that first attempt. In the real world though, where databases are under heavy use, caches expire. Performance is based upon first and second attempts together. This means, the more diversified the queries, the less advantage you get from caching.