1、Changing cardinality of existing input data structures from mandatory to optional.
將現(xiàn)有輸入數(shù)據(jù)結構的基數(shù)性由強制更改為可選。

2、The cardinality of the relationship between source and destination languages.
源語言和目標語言之間的關系。

3、Changing cardinality of existing output data structures.
變更現(xiàn)有輸出數(shù)據(jù)結構的基數(shù)性。

4、Operators whose cardinality in the plan remains the same can be skipped in the interim.
可以暫時跳過計劃中基數(shù)不變的操作。

5、The table cardinality for CUST_CUSTOMER is about 30000.
CUST_CUSTOMER的表基數(shù)大約是30000。

6、Cardinality affects join orders and join methods to a large extent.
這個基數(shù)會大大影響連接順序和連接方法。

7、Tighten the cardinality for some of the relationships.
對于一些關系加強聯(lián)系(從多對一改為一對一)。

8、The cardinality estimate of 7 does not match the actual result of 12.
基數(shù)估計值7與實際結果12不符。

9、The cardinality of the input schema can determine if multiple values can be selected.
輸入模式中的基數(shù)決定是否可以選擇多個值。

10、No statistical view - Here the cardinality based on the data is off significantly.
不使用統(tǒng)計視圖-在這種情況下，對于數(shù)據(jù)的基數(shù)的估計明顯不準確。

11、Note: The Relational DAS assumes that all containment relationships are cardinality one-to-many.
注意：關系型DAS假定所有包容關系都是一對多的二元關系。

12、Cardinality adherence for element data as well as for required attributes.
元素數(shù)據(jù)以及所需屬性的基數(shù)性。

13、Given that the table cardinality is about 50000; it should not be a performance disaster, either.
假設表基數(shù)大約是50000；這也將會是性能上的災難。

14、The same cardinality estimate is carried up, and no counts are needed for these two operators.
同樣進行基數(shù)估計，但是這兩個操作不需要計數(shù)。

15、With this method, we can collect real cardinality for access plan operators.
通過這種方法，我們就能夠為訪問操作者收集實際基數(shù)。

16、Dealing with HL7 cardinality and optionality.
處理HL7基數(shù)和可選性。

cardinality翻譯