• sol (unregistered) in reply to martin
    martin:
    humm yeah, i wonder why would one use the already hashed/indexed/cached sorting indexes of the database when you can just try to it by hand for 4 million records ... no .. really why would you ? :p

    if databases would suck at sorting/caching/indexing, why would we use them in the first place ? we could just mount a nfs driver amongts our clustered machine and ignorantly live on the back of a textfile :p

    speaking of which ...

    1. bandwidth
    2. bandwidth
    3. speed
    4. compiled sorts are faster... ah n/m I don't like it either I was forced at an old job. it was stated never use order by never use top if you read about how these work you'll see that the amount of data pulled and worked with is everything meaning this happens before the where clause... thus some say performance hit
    5. bandwidth 6)see 1,2,3,5
  • GrouchyAdmin (unregistered) in reply to mdk

    Much as with the article, MySQL eats everything, and shits out three times the amount of troubles.

  • Old Ygg (unregistered) in reply to Ultimape

    Actually, my company does this pretty religiously as well. But we can actually keep the e-mails on our local machines, not that it would do much good...

  • Old Ygg (unregistered) in reply to Dazed

    In all the modules I have worked in - Date is contained in two (not one) character fields. A series of characters for the date, and a series of characters for the time.

    But I mean, if you want to start in on SAP's database design, this isn't the first or the most grevious aspect I'd start at....

    Old Ygg

  • Old Ygg (unregistered) in reply to Peter

    I'm assuming at the moment that he couldn't do that for at least one reason: The developers used parameterized queries or stored procedures (good) but didn't know enough to do all the different data types they were using (all, you know 5 of them probably).

    So, if he changed the database and not their code, it seems likely that performance issues would be moot and exception handling would come to the forefront.

    Old Ygg

  • Old Ygg (unregistered) in reply to violentEd

    I don't know - how many months can he afford unemployed - or most of the rest of us?

    You gotta do, what you gotta do. And sometimes that means being quiet when people do stupid things and having an up-to-date resume.

    Old Ygg

  • Old Ygg (unregistered) in reply to Hognoxious

    It isn't really a matter of it not working. I know SAP is Enterprise, but it is pretty basic, that to decrease the size in storage of a date and time field... You should store them as numeric/decimal values instead of a crapload of characters.

    Not only that, but it makes it really easy to sort by these numeric values than character ones - I should think that would be a performance gain as well.

    Old Ygg

Leave a comment on “We'll Optimize Later”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article