Multi-tenant database performance test manual

In the installation package jointly released with litwarehr2.0, a multi-tenant database performance testing tool is released to help customers test the database performance expansion under multi-tenant conditions.
We have selected five available data extension methods for comparison:

1.Extended table mode extension table: Multiple tenants use the same database and share all tables. A standalone table stores tenant-specific columns as rows. Use the SQL view to convert rows in a table into columns. Litwarehr uses this method to build applications. This tool supports three different solutions to create this view:

A. onejoinperfield (for each extended domain, the tenant view will have a left join)

B. onejoinpertable (a separate left join)

C. Functions (new functions of SQL Server 2005)

2.Tenant-specific schema: Multiple tenants are in the same database, but each tenant has its own customized schema. However, this tool does not support this design.

3.Fixed column fixed columns: Fixed columns are provided to store tenant extended data.

4.Hybrid:Fixed ColumnsCombined with an extended table, if you need more extended fields than a fixed number of columns, these extended tables will be used for the added fields.

5.XMLColumn: The Tenant's extended data is stored in a separate XML column.
And according to the user choose not to access the data expansion method using performance testing tools for testing, get the corresponding data icon for analysis. I have translated the document, you can go to the http://www.cnsaas.com/DownLoadFile.aspx? Filetype = 2.

One of the results may be of interest to you, that is, the extension table and XML storage efficiency will be higher. The test results show that the extension table is more efficient, therefore, we recommend that you use XML for scalable processing in the future, especially for multi-tenant performance problems.