there is no absolute maximum number of rows, as they are stored in a database table like any other data. However, currently the whole data of a module needs to be read in memory when querying the table, therefore we do not recommend to use it for hundred thousands of records.

UDT uses a serialized storage format and needs to deserialize it on load. This attitude has advantages - and disadvantages:

+ multiple module instances with different format can share 3 common tables
+ a single row can exceed the maximum row size of SQL server
+ easy search in all fields of a records
+ more efficient storage, if tables are less populated (many fields are empty)
+ very flexibel and efficient up to a hardware determined number of records

- transformation needed
- SQL queries are more difficult and less efficient
- easy search in single columns
- less efficient storage, if tables are heavily populated
- less optimal for large number of records

Eck Two has created a solution, that allows him, to overcome the last limitation mentioned above. But he also states, that this narrows his options, to use all the options offered by UDT, to display and manage (i.e. sort, filter) all records according to user's needs. Now it is up to you to choose the best option for your requirements. Good luck.