sql server - Extended Property Design -


Suppose I have the following table schema:

  id | Name | Width | Height | |  

What are the ideas for thinking about breaking this table into two tables with one-to-one relationship?

Example:

  id | Name and id Width | Height | | Size  

My concern is that I have a lot of columns on the table (not just five, here's the possibility to add new columns in the future only for illustration purposes). I am worried that there may be a negative impact on the performance of large table row size and / or clarity of design. Is it true? And performance hits compared to the included tables.

:

Crossing 8,060-byte can affect line-size limits Because the SQL Server 2005 database engine still maintains a limit of 8 KB per page. When a combination of varchar, nvarchar, varbinary, sql_variant, or CLR user-defined type column exceeds this limit, while maintaining the database 24-byte pointer, the database engine ROW_OVERFLOW_DATA is the largest width of any other page in the allocation unit Transferring the record column with the move to the large page on the original page is dynamically because the record is long on the basis of operation Interpretation is. Update tasks that minimize records can be rolled back into the IN_ROW_DATA allocation unit on the Records original page. In addition, inquiries and execution of other selected operations, such as type or large records, have row overflow data, slow down the processing time, as these records are synchronized instead of asynchronous.

Raj


Comments

Popular posts from this blog

c# - ListView onScroll event -

PHP - get image from byte array -

Linux Terminal Problem with Non-Canonical Terminal I/O app -