Skip to main content
WordPress Development

Return to Question

added 114 characters in body
Source Link
Adam
Adam
  • 349
  • 5
  • 13

I am deploying WordPress MultiSite and if I get a decent amount of users, I will have thousands of database tables to support all of these sites. I like the idea of consolidating all of these tables to a single set of tables to make multisite more manageable and also more optimized for SQL Server. Has anyone had experience with a large number of tables issue in multisite?

Edit: Basically I want to understand the performance impact of having thousands of tables added over time?

I am deploying WordPress MultiSite and if I get a decent amount of users, I will have thousands of database tables to support all of these sites. I like the idea of consolidating all of these tables to a single set of tables to make multisite more manageable and also more optimized for SQL Server. Has anyone had experience with a large number of tables issue in multisite?

I am deploying WordPress MultiSite and if I get a decent amount of users, I will have thousands of database tables to support all of these sites. I like the idea of consolidating all of these tables to a single set of tables to make multisite more manageable and also more optimized for SQL Server. Has anyone had experience with a large number of tables issue in multisite?

Edit: Basically I want to understand the performance impact of having thousands of tables added over time?

Source Link
Adam
Adam
  • 349
  • 5
  • 13

Minimize Performance Issues of MultiSite Large Number of Tables Created

I am deploying WordPress MultiSite and if I get a decent amount of users, I will have thousands of database tables to support all of these sites. I like the idea of consolidating all of these tables to a single set of tables to make multisite more manageable and also more optimized for SQL Server. Has anyone had experience with a large number of tables issue in multisite?