Anyway to create Dictionary database in SQLserver that consist word and definition and word type (Verb,Noun,etc.)?
如何在SQLserver中创建包含单词、定义和单词类型(动词、名词等)的字典数据库?
Just contain all data in one table or do something like hash-table
只需在一个表中包含所有数据，或者执行哈希表之类的操作
table A contain only word that start with 'A'
table B contain only word that start with 'B'
表A只包含以A开头的单词表B只包含以B开头的单词
I'm very new in Databases.
我对数据库很陌生。
1 个解决方案
#1
2
All in one table, always. Never ever design a database where one needs to dynamically name objects ('to lookup key 'foo', use 'table6522'). Dynamic naming is a recipe for disaster, performance wise and development wise, and you'll just self-inflict a lot of pain when it comes to use tools.
总是在一张桌子上。永远不要设计一个需要动态命名对象的数据库('to lookup key 'foo'，使用'table6522')。动态命名是灾难、性能和开发的诀窍，当使用工具时，您将会自己造成很多痛苦。
If you must partition the table, SQL Server already has partitioning, but this does not apply to you case (hint, unless you are a DBA designing an ETL pipeline with fast partition switching, partitioning is never an answer). See SQL Server Partitioning: Not the Best Practices for Everything for more details.
如果必须对表进行分区，那么SQL Server已经有了分区，但这并不适用于您的情况(提示，除非您是一名设计ETL管道并进行快速分区切换的DBA，否则分区从来都不是答案)。请参阅SQL Server分区:不是所有细节的最佳实践。
A good way to design any table in SQL Server is to choose a correct clustered index and add appropriate indexes for you specific workload. The design is driven by how you are going to query the table. Read carefully SQL Server Index Design Guide. When you're done, read it again. Then again. Repeat this for the next 4-5 days until you really grok what's being said there.
在SQL Server中设计任何表的一个好方法是选择正确的聚集索引并为特定的工作负载添加适当的索引。设计是由如何查询表驱动的。仔细阅读SQL Server索引设计指南。当你完成后，再读一遍。然后再一次。在接下来的4-5天里重复这句话，直到你真正领会其中的含义。
#1
2
All in one table, always. Never ever design a database where one needs to dynamically name objects ('to lookup key 'foo', use 'table6522'). Dynamic naming is a recipe for disaster, performance wise and development wise, and you'll just self-inflict a lot of pain when it comes to use tools.
总是在一张桌子上。永远不要设计一个需要动态命名对象的数据库('to lookup key 'foo'，使用'table6522')。动态命名是灾难、性能和开发的诀窍，当使用工具时，您将会自己造成很多痛苦。
If you must partition the table, SQL Server already has partitioning, but this does not apply to you case (hint, unless you are a DBA designing an ETL pipeline with fast partition switching, partitioning is never an answer). See SQL Server Partitioning: Not the Best Practices for Everything for more details.
如果必须对表进行分区，那么SQL Server已经有了分区，但这并不适用于您的情况(提示，除非您是一名设计ETL管道并进行快速分区切换的DBA，否则分区从来都不是答案)。请参阅SQL Server分区:不是所有细节的最佳实践。
A good way to design any table in SQL Server is to choose a correct clustered index and add appropriate indexes for you specific workload. The design is driven by how you are going to query the table. Read carefully SQL Server Index Design Guide. When you're done, read it again. Then again. Repeat this for the next 4-5 days until you really grok what's being said there.
在SQL Server中设计任何表的一个好方法是选择正确的聚集索引并为特定的工作负载添加适当的索引。设计是由如何查询表驱动的。仔细阅读SQL Server索引设计指南。当你完成后，再读一遍。然后再一次。在接下来的4-5天里重复这句话，直到你真正领会其中的含义。