What github did was not table partitioning but schema separation. Splitting tables between separate disk partitions works well when the storage is local to the

What github did was not table partitioning but schema separation. Splitting tables between separate disk partitions works well when the storage is local to the engine and historically got around the size/io limits of hard disks but not necessarily suited to modern scaling problems. What github did instead was to separate out whole sub-systems from the main db cluster to separate clusters so that requests could hit completely separate engines so that the number of connections to each would be reduced and the chance of breaking something by a mistake in a cross-schema query is reduced by physical separation. I think you could still do this with SQL Server but why bother if you already use MySQL and the tools exist there.