"DB Performance Killers: Share Your Worst Migration Stories"

susligg

New member
Joined
Dec 23, 2010
Messages
3
Reaction score
0
"Hey everyone, I'm still salty about my last migration disaster. I was moving a large MySQL DB to a new hosting platform and somehow managed to kill the performance by 90%. The kicker was when I realized the new servers didn't support InnoDB storage engines, causing a bunch of my queries to fail."
 

IDios

New member
Joined
Feb 9, 2007
Messages
4
Reaction score
0
"Yikes, I feel your pain, OP. We had a migration nightmare with our MySQL DB a while back. Had to rewrite our queries from scratch and optimize our indexes, which ended up doubling our throughput."
 

esobko

New member
Joined
Oct 20, 2010
Messages
3
Reaction score
0
"Dude, I had a nightmare when migrating from MySQL to PostgreSQL. Our query times went from ~50ms to ~5 seconds because of a wonky indexing scheme. Had to rebuild the entire table to get it sorted"
 

yuryazarov

New member
Joined
Mar 26, 2006
Messages
1
Reaction score
0
"Yikes, I feel your pain OP. I once migrated to a sharded DB setup and forgot to update the schema, causing a massive slow down. Took me 2 weeks and a sleepless night to realize I'd accidentally set 2 identical fields as primary keys".
 

Roverdark

Member
Joined
Jul 1, 2017
Messages
9
Reaction score
0
"Ugh, I've been there too. Migrating to a new DB schema, I forgot to add indexing on a critical table and saw a 90% slowdown in queries. Lesson learned: double-check your schema before the big switch"
 

toha17_92

New member
Joined
Apr 13, 2011
Messages
4
Reaction score
0
"Yikes, I feel your pain. Did a migration from MySQL to PostgreSQL a few months back and it was a total nightmare. Our query performance tanked for a solid week before we could get it sorted out."
 
Top