Can you explain what exactly it is that makes it a lot harder? (And isn't a DBA paid to do his job?)
Most real world business applications use partitionning in order to cope with very big tables. An auto-increment key is not a good candidate for splitting a table, as it will prevent spreading the data across the partitions for parallel processing,
so you have to play with an application key (the auto-increment) and a partitionning key that the application has to set anyway when creating rows, which is far from optimal...
Anyway, good developpers understand the implication of what they do for the underlying database... DBAs and DBMS won't fix your bad design decisions.
Slashdot Mirror
Can you explain what exactly it is that makes it a lot harder? (And isn't a DBA paid to do his job?) Most real world business applications use partitionning in order to cope with very big tables. An auto-increment key is not a good candidate for splitting a table, as it will prevent spreading the data across the partitions for parallel processing, so you have to play with an application key (the auto-increment) and a partitionning key that the application has to set anyway when creating rows, which is far from optimal ...
Anyway, good developpers understand the implication of what they do for the underlying database ... DBAs and DBMS won't fix your bad design decisions.