<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-8313371909933476764</id><updated>2011-12-29T20:48:36.140Z</updated><title type='text'>Database Performance Tuning</title><subtitle type='html'>Sharing real world experiences on database tuning. A place to think about and discuss database performance tuning. Have fun.</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>51</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-7522242403770985686</id><published>2011-12-29T20:48:00.001Z</published><updated>2011-12-29T20:48:31.024Z</updated><title type='text'>2012 predictions</title><summary type='text'>Unlike other years, where I wrote my "predictions" entry at the end of the year, this time I'm going to try to predict what is going to happen in a few technology areas in 2012. Oh yes, another not so database centric post. Well, it does have some database content. Read on.

First, I don't believe in the "the year of...." idea. At least applied to technology, it does not make much sense. There </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/7522242403770985686/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2011/12/2012-predictions.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/7522242403770985686'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/7522242403770985686'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2011/12/2012-predictions.html' title='2012 predictions'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-7114317562696234780</id><published>2011-11-16T08:09:00.001Z</published><updated>2011-11-16T13:49:04.090Z</updated><title type='text'>Unity and the mismatch of user interfaces, or how I learned to hate the overlay scrollbars</title><summary type='text'>
During my first years of Linux, I switched between KDE and GNOME at the same time as I switched distributions, or more exactly, as each distro had a different default desktop environment. Later on, I began switching when each desktop environment leapfrogged others with new fancy functionality.



Then, some time ago, I settled on KUbuntu, and keep using it for my day to day desktop users. I'm </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/7114317562696234780/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2011/11/unity-and-mismatch-of-user-interfaces.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/7114317562696234780'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/7114317562696234780'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2011/11/unity-and-mismatch-of-user-interfaces.html' title='Unity and the mismatch of user interfaces, or how I learned to hate the overlay scrollbars'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-7577758701835275575</id><published>2011-10-15T23:19:00.000+01:00</published><updated>2011-10-15T23:19:49.191+01:00</updated><title type='text'>iOS5 is here</title><summary type='text'>
iOS5 update is here. I applied to my iPad. The process is more or less the following (PC version):

- iTunes version update, of course after the update you need to reboot Windows. Why on earth you need to reboot Windows to update iTunes is beyond me. This is a mere 70MB download that installs pretty quickly, and thankfully Windows 7 boots fast.
- After the iOS5 release, lots of apps have been </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/7577758701835275575/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2011/10/ios5-is-here.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/7577758701835275575'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/7577758701835275575'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2011/10/ios5-is-here.html' title='iOS5 is here'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-4074637793990335625</id><published>2011-09-29T08:27:00.000+01:00</published><updated>2011-09-29T09:32:21.073+01:00</updated><title type='text'>[Programming Language] is great because non technical people can understand it</title><summary type='text'>
(follow up to the VBScript from hell)

It was a popular marketing motto for pushing new programming languages a while ago. "BASIC/COBOL/xxxx is great because I (or my boss) can understand it".

And you are probably be able to understand it because it is full of global variables, pieces of code that repeat over and over, simple operations that can be resolved with library calls reinvented again </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/4074637793990335625/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2011/09/language-is-great-because-non-technical.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/4074637793990335625'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/4074637793990335625'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2011/09/language-is-great-because-non-technical.html' title='[Programming Language] is great because non technical people can understand it'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-9122934293431623034</id><published>2011-09-20T16:34:00.000+01:00</published><updated>2011-09-20T16:45:51.358+01:00</updated><title type='text'>The VBScript from hell: typed vs. typeless languages</title><summary type='text'>

I grew up on structured programming. After introducing myself into the wonderful world of programming by ways of old school, line-numbered, GOTO and GOSUB BASIC, peppered with assembly for obvious performance reasons, I started to learn Pascal using Turbo Pascal (thanks, Borland!) and from there jumped to other structured languages (C and its cousins) and to a few non structured ones: hello to </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/9122934293431623034/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2011/09/vscript-from-hell-typed-vs-typeless.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/9122934293431623034'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/9122934293431623034'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2011/09/vscript-from-hell-typed-vs-typeless.html' title='The VBScript from hell: typed vs. typeless languages'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-5089286703943778203</id><published>2011-09-08T12:42:00.000+01:00</published><updated>2011-09-09T00:46:29.790+01:00</updated><title type='text'>iPad: the sad state of the art</title><summary type='text'>
(Note before assuming I'm an Apple hater: I own a few Apple devices, none of them a Mac. I've been -and plan to continue using- an iPad for eight months, and recently purchased another one for a family member)

With the latest failed attempt of HP to at least establish some presence in the tablet market, and the subsequent hugely successful sale after the price drop, I did a cursory examination </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/5089286703943778203/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2011/09/ipad-sad-state-of-art.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/5089286703943778203'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/5089286703943778203'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2011/09/ipad-sad-state-of-art.html' title='iPad: the sad state of the art'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-3939859762412268800</id><published>2011-06-09T09:21:00.000+01:00</published><updated>2011-06-09T09:21:16.839+01:00</updated><title type='text'>SELECT * is bad for performance</title><summary type='text'>

And I thought that this discussion was forgotten a long time ago. But yes, at some point in the distant past, I wasted some time reading the different arguments for using an attribute list versus using the wildcard in a SELECT statement.

At the time, those discussions about the performance differences did not made sense to me. In the grand scheme of things, the difference was so small at the </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/3939859762412268800/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2011/06/select-is-bad-for-performance.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/3939859762412268800'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/3939859762412268800'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2011/06/select-is-bad-for-performance.html' title='SELECT * is bad for performance'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-3294660890137373767</id><published>2011-06-04T22:25:00.000+01:00</published><updated>2011-06-04T22:25:37.813+01:00</updated><title type='text'>XSLT Transformation to analyze MSSQL Server 2005 traces</title><summary type='text'>
During the final user validation of a new packaged application, we were getting complaints of bad performance, and the usual suspect, the database, was apparently perfectly well. This is where the SQL Server 2005 trace facilities shine. You can trace what is going on inside the database engine with quite a high level of accuracy, including filtering the "noise" generated by other users, other </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/3294660890137373767/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2011/06/xslt-transformation-to-analyze-mssql.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/3294660890137373767'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/3294660890137373767'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2011/06/xslt-transformation-to-analyze-mssql.html' title='XSLT Transformation to analyze MSSQL Server 2005 traces'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-1959474145260782638</id><published>2011-04-05T00:25:00.002+01:00</published><updated>2011-04-05T00:29:43.179+01:00</updated><title type='text'>Advice for spammers</title><summary type='text'>
I must confess: I don't know how most of the internet based business works. But from what I read, it seems that "pagerank" plus "traffic" is all you need to earn tons of money without actually doing much of value. There seems to be whole operations, called search engine optimizers(*) (or SEOs) devoted to changing a site or a set of sites so that they appear in the top Google search results.

How</summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/1959474145260782638/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2011/04/advice-for-spammers.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/1959474145260782638'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/1959474145260782638'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2011/04/advice-for-spammers.html' title='Advice for spammers'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-3402264823623989116</id><published>2011-02-27T20:32:00.001Z</published><updated>2011-02-27T22:41:25.971Z</updated><title type='text'>Anything not scripted is a risk</title><summary type='text'>
From time to time, I've encountered a few situations that left me thinking about their root causes. Here are a few examples:

People joining the development team needs weeks to be able to build the application, install their development environment or both. Worst cases I've seen take months for someone to be productive.
Staging environment is terribly out of date. Nobody dares to propose to </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/3402264823623989116/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2011/02/anything-not-scripted-is-risk.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/3402264823623989116'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/3402264823623989116'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2011/02/anything-not-scripted-is-risk.html' title='Anything not scripted is a risk'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-2627025963908722085</id><published>2011-02-23T00:55:00.000Z</published><updated>2011-02-23T00:55:42.141Z</updated><title type='text'>Is your privacy worth 100$?</title><summary type='text'>Suppose you come across some nice guy on the street that makes you the following offer:

Hey, man, you really look like a nice person. Can you give me your list of friends, tell me where you are during the day, tell me what your opinions are in related to topics of my choice and generally tell me what/when/if you like or not things I ask about? I’ll get this information from you during your </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/2627025963908722085/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2011/02/is-your-privacy-worth-100.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/2627025963908722085'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/2627025963908722085'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2011/02/is-your-privacy-worth-100.html' title='Is your privacy worth 100$?'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-6530655986819996926</id><published>2010-12-18T17:38:00.002Z</published><updated>2010-12-18T17:40:08.221Z</updated><title type='text'>The Japanese Daimyo and the Ninja School</title><summary type='text'>About three hundred years ago, Japan was a country fragmented into many small kingdoms or clans, whose leaders were constantly battling among themselves.

Wars were constantly going on between different clans, with each one having to depend on an increasingly sophisticated system that provided the manpower and resources necessary to keep their territories safe and at the same time take advantage </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/6530655986819996926/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2010/12/japanese-daimyo-and-ninja-school.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/6530655986819996926'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/6530655986819996926'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2010/12/japanese-daimyo-and-ninja-school.html' title='The Japanese Daimyo and the Ninja School'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-3466487959704912344</id><published>2010-11-17T15:06:00.000Z</published><updated>2010-11-17T15:06:53.274Z</updated><title type='text'>CAB and TAB: a waste of time for everyone</title><summary type='text'>
I've been trying for weeks to write a piece on ITIL that did not sounded vindictive or bitter. I really wanted to be fair on ITIL, or to be more precise, I'm all in favor of having some kind of change control and IT management in place.

But having to go through the ITIL recommended change management processes a couple of times has revealed me the true costs and overhead of ITIL. I'm currently </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/3466487959704912344/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2010/11/cab-and-tab-waste-of-time-for-everyone.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/3466487959704912344'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/3466487959704912344'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2010/11/cab-and-tab-waste-of-time-for-everyone.html' title='CAB and TAB: a waste of time for everyone'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-7515241195256289994</id><published>2010-10-31T10:09:00.000Z</published><updated>2010-10-31T10:09:50.667Z</updated><title type='text'>Unicode explained to the younger developers</title><summary type='text'>
I had recently a question from one developer about the different ways that Oracle has to declare a string column. He was specifically confused between VARCHAR2(xx), VARCHAR(xx) and finally VARCHAR2(CHAR xx).

Short answer: forget about VARCHAR, use always VARCHAR2. The difference is related to how it handles Unicode characters. VARCHAR2(xx) will have room for xx bytes, where VARCHAR2(CHAR xx) </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/7515241195256289994/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2010/10/unicode-explained-to-younger-developers.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/7515241195256289994'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/7515241195256289994'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2010/10/unicode-explained-to-younger-developers.html' title='Unicode explained to the younger developers'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-1932401193732611527</id><published>2010-10-15T00:28:00.000+01:00</published><updated>2010-10-15T00:28:26.403+01:00</updated><title type='text'>This code is crap</title><summary type='text'>
Helping customers get the most out of their systems is good and interesting job. One gets to know a lot of industry sectors, processes and ways of working, as well as some good people.

Invariably, the job involves reading code. And writing code, usually a tiny fraction of the whole body, because you focus on the parts that provide most benefit to your customer. Whenever I wrote code, I always </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/1932401193732611527/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2010/10/this-code-is-crap.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/1932401193732611527'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/1932401193732611527'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2010/10/this-code-is-crap.html' title='This code is crap'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-1838888069995218087</id><published>2010-06-16T22:02:00.000+01:00</published><updated>2010-06-16T22:02:22.503+01:00</updated><title type='text'>The huge gap between geeks and business types</title><summary type='text'>I've never been on the buying side of some work for hire sites, but I'm sure that they offer the potential buyer the option of  targeting to a single person a concrete job offer, because sometimes I get job offers that are not visible to the rest of the pool. Forgive me for the self promotion, I only can say in my defence that (a) I'm not making this up and (b) customer loyalty is one of the </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/1838888069995218087/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2010/06/huge-gap-between-geeks-and-business.html#comment-form' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/1838888069995218087'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/1838888069995218087'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2010/06/huge-gap-between-geeks-and-business.html' title='The huge gap between geeks and business types'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>4</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-76005060564020555</id><published>2010-05-10T08:32:00.000+01:00</published><updated>2010-05-10T08:32:52.101+01:00</updated><title type='text'>Customer constraints may affect your ability to tune</title><summary type='text'>
Any tuning effort will touch parts of a system. Some of them touch the database, others the client application, others the middleware layer, and some change them all. One element thus that measures the effort required for tuning is the number of system elements that have been changed. It is reasonable to assume that the more components you touch, the more complex the tuning is.

But I've </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/76005060564020555/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2010/05/customer-constraints-may-affect-your.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/76005060564020555'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/76005060564020555'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2010/05/customer-constraints-may-affect-your.html' title='Customer constraints may affect your ability to tune'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-7403224830649316116</id><published>2010-05-01T01:00:00.001+01:00</published><updated>2010-05-01T01:01:24.388+01:00</updated><title type='text'>Blog anniversary</title><summary type='text'>
In case you've not noticed, this blog is entering its third year. Just like many other things you do in life, I had more than one reason to start putting my thoughts in writing. I've already forgotten some of the reasons, and some new ones will also appear over time. But I keep posting. Nevertheless, here are some of them, in no particular order.

I wanted to have a means to vent my frustration </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/7403224830649316116/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2010/05/blog-anniversary.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/7403224830649316116'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/7403224830649316116'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2010/05/blog-anniversary.html' title='Blog anniversary'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-3054077018344143601</id><published>2010-04-20T10:11:00.000+01:00</published><updated>2010-04-20T10:11:07.431+01:00</updated><title type='text'>The great NoSQL debate - what NoSQL is NOT good for</title><summary type='text'>
Hey, after a long pause, and after having glossed over how nice NoSQL databases are, we finally arrive to the blood and tears part. The one that generates controversy. Even passion. Which is a lot to say and gives the debate a new twist outside of the usual rational (some even are relational) database folks. That's why I'm using as a headline for each point some of the more passional statements </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/3054077018344143601/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2010/04/great-nosql-debate-what-nosql-is-not.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/3054077018344143601'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/3054077018344143601'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2010/04/great-nosql-debate-what-nosql-is-not.html' title='The great NoSQL debate - what NoSQL is NOT good for'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-1580975994394650279</id><published>2010-04-05T22:27:00.002+01:00</published><updated>2010-04-05T22:31:19.511+01:00</updated><title type='text'>The great NoSQL debate - what NoSQL is good for</title><summary type='text'>
After some background, we can now dissect the reasons that have created the sudden interest for NoSQL data stores.

First, let's separate interest from hype. Hype is the part that says that NoSQL is good for everything, that everyone not using it has no future. The phenomenon of hype in technology is so interesting and complex that it deserves its own post. Well, a collection of them, really.

</summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/1580975994394650279/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2010/04/great-nosql-debate-what-nosql-is-good.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/1580975994394650279'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/1580975994394650279'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2010/04/great-nosql-debate-what-nosql-is-good.html' title='The great NoSQL debate - what NoSQL is good for'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-3702696423932929086</id><published>2010-04-03T18:23:00.002+01:00</published><updated>2010-04-03T19:01:03.351+01:00</updated><title type='text'>The great NoSQL debate - History</title><summary type='text'>
It had to happen. Apparently, it all started with a post from Ted Dzuiba provocatively titled "I can't wait for NoSQL to die"

The Internet is a wonderful thing. Twenty years ago, someone expressing these kind of ideas would hardly go noticed, unless he was on a very influential position. But people in such positions tend to try to not angry anyone. Thanks to the Internet, the ensuing </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/3702696423932929086/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2010/04/great-nosql-debate-history.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/3702696423932929086'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/3702696423932929086'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2010/04/great-nosql-debate-history.html' title='The great NoSQL debate - History'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-887366936176411922</id><published>2010-02-19T10:20:00.004Z</published><updated>2010-03-01T19:44:38.791Z</updated><title type='text'>Security errors and overmitigation</title><summary type='text'>
The last version of the SANS Top 25 is out. This is a list of the top 25 most dangerous security errors committed in programming. It's an interesting read for anyone who cares about security, and if you're like me, you'll recognize in the list some sins from the past perpetrated by yourself.

There is however one that caught my attention. Number 11 is the use of hard coded credentials.

</summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/887366936176411922/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2010/02/security-errors-and-overmitigation.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/887366936176411922'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/887366936176411922'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2010/02/security-errors-and-overmitigation.html' title='Security errors and overmitigation'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-7601249024226579002</id><published>2010-01-22T10:06:00.002Z</published><updated>2010-01-22T11:13:20.912Z</updated><title type='text'>2009 Database Tuning Predictions</title><summary type='text'>Astrology. Those in the prediction business have a rare ability to come up year after year each December giving predictions on what is going to happen in the next 12 months.

Astrology is always trying to appear insightful, while being as generic as possible in their predictions, just in case anyone remembers their predictions and try to verify any facts along the way.

But I've found a much </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/7601249024226579002/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2010/01/2009-database-tuning-predictions.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/7601249024226579002'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/7601249024226579002'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2010/01/2009-database-tuning-predictions.html' title='2009 Database Tuning Predictions'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-8953688486361074179</id><published>2010-01-03T20:28:00.001Z</published><updated>2010-01-03T20:29:41.565Z</updated><title type='text'>Vista patching, or how to miscalculate the costs of owning an OS</title><summary type='text'>Warning: post completely unrelated to database optimization. In a sense, it is related to process performance analysis.

You may find a lot of disadvantages of being the "never appointed but acting as" family computer technician. Oh yes, other family members reading this probably are remembering the day that they did this or that on dad's computer and thinking that I'm exaggerating and being </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/8953688486361074179/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2010/01/vista-patching-or-how-to-miscalculate.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/8953688486361074179'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/8953688486361074179'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2010/01/vista-patching-or-how-to-miscalculate.html' title='Vista patching, or how to miscalculate the costs of owning an OS'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-8133379868740971253</id><published>2009-11-15T12:13:00.002Z</published><updated>2009-11-15T20:34:36.932Z</updated><title type='text'>Indexes cost money</title><summary type='text'>All this industry talk about cloud computing is, more than ever, placing under the spotlight the true cost of IT infrastructure. Combined with the current economic climate, this is sparkling an interesting and refreshing debate on what is the actual cost of supporting and growing an IT infrastructure. And more and more, a realistic cost breakdown of how much each piece of the infrastructure is </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/8133379868740971253/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2009/11/indexes-cost-money.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/8133379868740971253'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/8133379868740971253'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2009/11/indexes-cost-money.html' title='Indexes cost money'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-4870363602377425339</id><published>2009-11-07T17:16:00.006Z</published><updated>2009-11-07T17:25:32.160Z</updated><title type='text'>The tragedy of tactical vs. strategic solutions</title><summary type='text'>I've noticed lately an increased tendency for the so-called "Tactical Solutions" in big organizations. Those are usually focusing their IS efforts around a few key systems, termed the "Strategic" ones. Strategic is synonym of big, complex and ambitious. 

I've always heard the term "tactical solution" used to denote something that was put together quickly, without paying too much attention to the</summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/4870363602377425339/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2009/11/tragedy-of-tactical-vs-strategic.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/4870363602377425339'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/4870363602377425339'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2009/11/tragedy-of-tactical-vs-strategic.html' title='The tragedy of tactical vs. strategic solutions'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-4539120566750942775</id><published>2009-10-29T22:13:00.003Z</published><updated>2009-10-29T22:17:21.548Z</updated><title type='text'>GAE: the good, the bad and the irrelevant</title><summary type='text'>From what I read, the general feeling is that there are two irreconcilable factions in the cloud/no cloud debate: those that go for it and those that do not.

For such a highly technical topic, I'm surprised to see GAE being debated at almost emotional levels. In one side, there are folks that look like Google fanboys and see nothing but advantages for your business to host things in GAE. The </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/4539120566750942775/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2009/10/gae-good-bad-and-irrelevant.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/4539120566750942775'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/4539120566750942775'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2009/10/gae-good-bad-and-irrelevant.html' title='GAE: the good, the bad and the irrelevant'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-1171522726623150930</id><published>2009-09-21T07:56:00.004+01:00</published><updated>2009-09-21T08:14:40.120+01:00</updated><title type='text'>The demise of global software services</title><summary type='text'>I came across this post by no other than Kent Beck. It's no wonder how he has developed the status he has in the industry today: he is a very good communicator. What could take me half a book to describe, Beck can do in three paragraphs. This style of communication is a perfect fit for the eternally busy business people that cannot take away his eyes off the BlackBerry for more than fifteen </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/1171522726623150930/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2009/09/demise-of-global-software-services.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/1171522726623150930'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/1171522726623150930'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2009/09/demise-of-global-software-services.html' title='The demise of global software services'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-3201766540027007362</id><published>2009-07-09T09:00:00.001+01:00</published><updated>2009-07-09T09:02:14.229+01:00</updated><title type='text'>Open Source does not have market share - does not even have a market?</title><summary type='text'>According to the Wikipedia definition:"A market is any one of a variety of different systems, institutions, procedures, social relations and infrastructures whereby persons trade, and goods and services are exchanged, forming part of the economy. It is an arrangement that allows buyers and sellers to exchange things"I'm neither economics nor market expert. But certainly that definition implies </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/3201766540027007362/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2009/07/open-source-does-not-have-market-share.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/3201766540027007362'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/3201766540027007362'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2009/07/open-source-does-not-have-market-share.html' title='Open Source does not have market share - does not even have a market?'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-8902636778890481883</id><published>2009-07-02T14:17:00.007+01:00</published><updated>2009-07-02T22:18:52.087+01:00</updated><title type='text'>Kill the flat text file</title><summary type='text'>Perhaps I'm not lucky and I always end up working with old systems, but I've become increasingly irritated by a practice that should have died years ago: the flat text file interface. In the stone age era, this was the standard way of exchanging data between systems, as the plethora of options that integration technologies have been creating in the last 20 years or so were not available.Probably </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/8902636778890481883/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2009/07/kill-flat-text-file.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/8902636778890481883'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/8902636778890481883'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2009/07/kill-flat-text-file.html' title='Kill the flat text file'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-8314123176487807520</id><published>2009-06-19T16:22:00.004+01:00</published><updated>2009-06-19T16:31:54.891+01:00</updated><title type='text'>Google Appengine (III) – Tuning means code refactoring</title><summary type='text'>One of the last tuning gigs I was involved with was related to a content recommendation system. The original implementation was a one by one translation of a statistics algorithms into SQL sentences. It generated a huge number of precalculations stored in a multi million record table that were later on reused when visitors were looking for content. It was even worse than that, as the result size </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/8314123176487807520/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2009/06/google-appengine-iii-tuning-means-code.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/8314123176487807520'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/8314123176487807520'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2009/06/google-appengine-iii-tuning-means-code.html' title='Google Appengine (III) – Tuning means code refactoring'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-1606133576555219154</id><published>2009-03-23T18:06:00.008Z</published><updated>2009-03-24T10:32:31.452Z</updated><title type='text'>GAE - Abstracting complexity and sharding counters</title><summary type='text'>The history of application development is littered with inventions addressing the problem of filling the conceptual gap between a machine serially executing some instructions acting on data and a business person trying to automate some process. Over the years, layer upon layer of abstractions have been developed, from assemblers, compilers, operating systems to the highly abstracted REST and SOA </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/1606133576555219154/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2009/03/gae-abstracting-complexity-and-sharding.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/1606133576555219154'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/1606133576555219154'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2009/03/gae-abstracting-complexity-and-sharding.html' title='GAE - Abstracting complexity and sharding counters'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-7543838761440701138</id><published>2009-03-23T13:28:00.019Z</published><updated>2009-03-24T10:33:58.575Z</updated><title type='text'>GAE, continued</title><summary type='text'>I've continued exploring Google AppEngine since my last post. Honestly, I've not had much time to devote to self education or blogging lately, so at this moment my opinions are not yet based on real world, live application, experience. And they are mostly opinions, not hard, evidence based, facts.GAE fundamentalsI'm new to Phyton and Django. Both of them have been a pleasant surprise. The Phyton </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/7543838761440701138/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2009/03/gae-continued.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/7543838761440701138'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/7543838761440701138'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2009/03/gae-continued.html' title='GAE, continued'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-8488300695104177049</id><published>2009-02-04T09:50:00.011Z</published><updated>2009-03-02T08:22:00.136Z</updated><title type='text'>Changed beyond recognition and the EAV data model</title><summary type='text'>One of the much maligned performance drags an application can have is its abuse of the so called Entity Attribute-Value (EAV) model for data storage. However, as with many catastrophic events, the performance problem is the result of the failure of multiple elements in the decision chain. Let's examine the motivations behind the EAV on each of the parties involved.The buyer (or designer) </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/8488300695104177049/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2009/02/changed-beyond-recognition-and-eav-data.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/8488300695104177049'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/8488300695104177049'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2009/02/changed-beyond-recognition-and-eav-data.html' title='Changed beyond recognition and the EAV data model'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-8996532343847939649</id><published>2009-01-28T12:21:00.002Z</published><updated>2009-01-28T13:02:52.375Z</updated><title type='text'>SQL Server Express installation</title><summary type='text'>How things have changed, that what I was thinking when I finished the install of SQL Server Express edition.But, as almost always, I've started with the end of the story. A close relative is soon going to change roles at work. She's moving to a system administration position, where, among other tasks, she's going to have to deal with a lot of MS SQL server tasks. I was therefore asked about the </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/8996532343847939649/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2009/01/sql-server-express-installation.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/8996532343847939649'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/8996532343847939649'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2009/01/sql-server-express-installation.html' title='SQL Server Express installation'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-9004092003042566388</id><published>2008-11-27T11:51:00.004Z</published><updated>2008-11-27T12:24:43.592Z</updated><title type='text'>The future of query optimizers</title><summary type='text'>Future performance optimizationsWhile learning about the Oracle 11g invisible index  feature, I really became aware of how complex the modern cost based optimizers have become. Essentially, Oracle has added a feature to its cost based optimizer that allows you to make an index invisible to its optimizer.This brought to me fond memories from when I had to revisit an already tuned statement, as </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/9004092003042566388/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2008/11/future-of-query-optimizers.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/9004092003042566388'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/9004092003042566388'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2008/11/future-of-query-optimizers.html' title='The future of query optimizers'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-3403471034080578516</id><published>2008-11-14T09:15:00.005Z</published><updated>2008-11-14T09:23:01.008Z</updated><title type='text'>More on tuning tools from industry luminaries</title><summary type='text'>It has been a long time ago since my post about tuning tools, but I found a very interesting paper written by some of the best people in the database world. There is a point where they say"... Moreover, at the current time, the automatic tuning aids in the RDBMSs that we are familiar with do not produce systems with anywhere near the performance that a skilled DBA can produce. Until the tuning </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/3403471034080578516/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2008/11/more-on-tuning-tools-from-industry.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/3403471034080578516'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/3403471034080578516'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2008/11/more-on-tuning-tools-from-industry.html' title='More on tuning tools from industry luminaries'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-6044564566119096308</id><published>2008-11-14T08:35:00.004Z</published><updated>2008-11-14T09:30:12.405Z</updated><title type='text'>A missing off-topic post</title><summary type='text'>This post was going to be quite large, and hopefully entertaining. This post took me the good part of an hour to write and was, I supposed, interesting to those upgrading or about to upgrade to Ubuntu 8.10Unfortunately, this post (well, its first version) was written as a mail message to a @blogspot account. Of course, and given the volume of mail that I handle on my day to day job, I usually </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/6044564566119096308/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2008/11/missing-off-topic-post.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/6044564566119096308'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/6044564566119096308'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2008/11/missing-off-topic-post.html' title='A missing off-topic post'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-7920196847635357909</id><published>2008-10-22T23:12:00.000+01:00</published><updated>2008-10-22T23:33:17.984+01:00</updated><title type='text'>Optimizing MySQL data loads</title><summary type='text'>Classic MysterySometimes, performance problems can be like a classic mystery novel. Hey, just a bit of fantasy sometimes help to get the stage. Here we are, surrounded by the usual suspects, and pondering which one is the most likely to blame. And then the underdog detective comes up pointing to the least likely person to have committed the murder. Of course, all the police detectives that have </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/7920196847635357909/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2008/10/optimizing-mysql-data-loads.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/7920196847635357909'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/7920196847635357909'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2008/10/optimizing-mysql-data-loads.html' title='Optimizing MySQL data loads'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-8869787641136736636</id><published>2008-10-15T12:37:00.000+01:00</published><updated>2008-10-15T12:44:58.161+01:00</updated><title type='text'>The Google Application Engine</title><summary type='text'>In the beginning, there was timesharing In the beginning, there was timesharing. This was in the early, early days of computing, before most of us were even born. At the time, computers were big, expensive, complex and extremely difficult to operate. Not to mention underpowered in comparison with, say, a domestic media player. Since most business did not have the resources -read money- or even </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/8869787641136736636/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2008/10/google-application-engine.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/8869787641136736636'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/8869787641136736636'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2008/10/google-application-engine.html' title='The Google Application Engine'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-2176953762113948374</id><published>2008-09-15T15:32:00.000+01:00</published><updated>2008-09-15T15:44:22.935+01:00</updated><title type='text'>Persistence engines</title><summary type='text'>How things came to be this wayAnyone involved long enough in software development ends up discovering a truth that is long ago known by other craftsmen and engineers: each problem is best solved with the tool more appropriate to solve it. Only problem for software is, it is such a young discipline that is all the time trying to tackle new problems not previously solved. Thus, sometimes it's very </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/2176953762113948374/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2008/09/persistence-engines.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/2176953762113948374'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/2176953762113948374'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2008/09/persistence-engines.html' title='Persistence engines'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-1415978916670126088</id><published>2008-07-28T11:36:00.000+01:00</published><updated>2008-07-28T11:45:39.255+01:00</updated><title type='text'>Please don't swap</title><summary type='text'>While browsing the database forums, it has come to my attention that some people are looking closer at their database system memory management and trying to adjust its configuration settings.Of course, the more complex the database the more parameters you can change. RDBMS's like Oracle for example have dozens of different parameters that can alter the memory usage of the database to better fit </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/1415978916670126088/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2008/07/please-dont-swap.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/1415978916670126088'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/1415978916670126088'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2008/07/please-dont-swap.html' title='Please don&apos;t swap'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-1129026239417273983</id><published>2008-07-10T13:18:00.000+01:00</published><updated>2008-07-10T13:26:03.776+01:00</updated><title type='text'>Procedural programming and SQL don't mix well</title><summary type='text'>Some of the biggest performance problems I've seen came from perfectly reasonable decisions made from fairly intelligent people. Specially, good developers coming from procedural programming languages trying to adapt the paradigms they know to the SQL language. I think that there's a strong parallelism between these cases and some of the most cited problems with people new to object oriented </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/1129026239417273983/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2008/07/procedural-programming-and-sql-dont-mix.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/1129026239417273983'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/1129026239417273983'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2008/07/procedural-programming-and-sql-dont-mix.html' title='Procedural programming and SQL don&apos;t mix well'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-632306232015266272</id><published>2008-07-03T08:40:00.000+01:00</published><updated>2008-07-03T08:44:43.998+01:00</updated><title type='text'>Maintenance programmer and performance</title><summary type='text'>It's almost universal. And unavoidable. Yet I'm not sure if it's right. But it's true. At almost any organization whose goal is to develop and maintain software, there is a knowledge based hierarchy. The best and brightest individual tend to take care of the more complex issues with programming and architecture. The juniors and newcomers are assigned lowest value added tasks. Usually, </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/632306232015266272/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2008/07/maintenance-programmer-and-performance.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/632306232015266272'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/632306232015266272'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2008/07/maintenance-programmer-and-performance.html' title='Maintenance programmer and performance'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-723116121656321453</id><published>2008-05-20T14:27:00.000+01:00</published><updated>2008-05-20T14:39:39.166+01:00</updated><title type='text'>Database tuning myths</title><summary type='text'>Businesses are always looking for predictability. From financial plans that span three years to operational plans for next year, to five year strategic plans, there is a good amount of time and resources at any business devoted just to predict what the future is going to look like. Entire business functions are needed to create the plans and track its evolution. And the stock market regularly </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/723116121656321453/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2008/05/database-tuning-myths.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/723116121656321453'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/723116121656321453'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2008/05/database-tuning-myths.html' title='Database tuning myths'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-2034143269894715725</id><published>2008-05-14T15:00:00.000+01:00</published><updated>2008-05-14T15:05:17.642+01:00</updated><title type='text'>Having a baseline</title><summary type='text'>While the technical part of database performance tuning is almost different in each case, on the business side of things I run almost always into the same conversations. My favorite one is the conversation with potential customers. These follows more or less the same structure. And it always begins with the same sentences:-Customer: our application has performance problems, we're looking for </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/2034143269894715725/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2008/05/having-baseline.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/2034143269894715725'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/2034143269894715725'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2008/05/having-baseline.html' title='Having a baseline'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-201108224338933635</id><published>2008-05-07T12:21:00.000+01:00</published><updated>2008-05-07T13:22:53.449+01:00</updated><title type='text'>Sometimes a tenth of a second is important</title><summary type='text'>As any other field where a certain skill level is reached, performance tuning for the uninitiated becomes some kind of magical black art beyond certain point. It's then part of your skill set to try to explain in terms that a non specialist can understand, what you're really doing. (and they are paying for)This is the point where excessive simplification can, and in fact does, give you problems. </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/201108224338933635/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2008/05/sometimes-tenth-of-second-is-important.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/201108224338933635'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/201108224338933635'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2008/05/sometimes-tenth-of-second-is-important.html' title='Sometimes a tenth of a second is important'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-2382428276161414991</id><published>2008-05-07T12:06:00.000+01:00</published><updated>2008-05-07T12:19:38.517+01:00</updated><title type='text'>Over-specify to avoid performance problems</title><summary type='text'>Nobody likes to stop the press, the train or the plane, or the cash collection, or whatever process their business is engaged on, waiting for a computer to finish its task. Nobody likes having to fit the process ("list of deliveries will not be available until 11:30 in the morning") to the timing of a machine. Those are usually the symptoms of a computer system not performing up to the business </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/2382428276161414991/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2008/05/over-specify-to-avoid-performance.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/2382428276161414991'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/2382428276161414991'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2008/05/over-specify-to-avoid-performance.html' title='Over-specify to avoid performance problems'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-7223648791010593337</id><published>2008-04-18T08:19:00.000+01:00</published><updated>2008-04-18T08:24:25.683+01:00</updated><title type='text'>Tuning tools: beware</title><summary type='text'>Older readers may remember the MSDOS extended and expanded memory standards. Back in the pre Windows 95 era, Intel machines were limited in the memory address space they could use. Not only because of the hardware, that until the 386 processor was limited to 16MB (yes, MB, not GB!) of RAM, but also limited by the MS-DOS compatibility constraints. There's a famous quote misattributed to Bill Gates</summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/7223648791010593337/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2008/04/tuning-tools-beware.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/7223648791010593337'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/7223648791010593337'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2008/04/tuning-tools-beware.html' title='Tuning tools: beware'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-6184576538195124573</id><published>2008-04-14T22:42:00.000+01:00</published><updated>2008-04-14T23:13:31.911+01:00</updated><title type='text'>The business case for performance tuning</title><summary type='text'>One of the most difficult parts of the engagement with a potential customer is the time to discuss your rates. Specially in comparison with the rates usually paid for other kind of professional services involving technology. Let's explore some of the reasons and the economies behind database performance tuning efforts.The ratesWith the recent wave of out/off/shoring, rates for services in the IT </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/6184576538195124573/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2008/04/business-case-for-performance-tuning.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/6184576538195124573'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/6184576538195124573'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2008/04/business-case-for-performance-tuning.html' title='The business case for performance tuning'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8313371909933476764.post-6687644330406461010</id><published>2008-04-08T13:36:00.000+01:00</published><updated>2008-04-09T07:45:55.049+01:00</updated><title type='text'>You probably have a performance problem. You'll probably never know that.</title><summary type='text'>Think about it. When was the last time you heard about your application being slow? Every day? week? month? When was the last time you heard from some business manager “we could do X more/better if the system could be more responsive”? Lots of times. How many processes in your business have their schedule and deadlines dictated by machine execution times? I'm sure that you'll find a few, some of </summary><link rel='replies' type='application/atom+xml' href='http://consultuning.blogspot.com/feeds/6687644330406461010/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://consultuning.blogspot.com/2008/04/you-probably-have-performance-problem.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/6687644330406461010'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8313371909933476764/posts/default/6687644330406461010'/><link rel='alternate' type='text/html' href='http://consultuning.blogspot.com/2008/04/you-probably-have-performance-problem.html' title='You probably have a performance problem. You&apos;ll probably never know that.'/><author><name>Consultuning</name><uri>http://www.blogger.com/profile/07362336620660791545</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry></feed>
