I'm asking for a new table that might be 200K rows. I want to make sure that this table queryists are efficiant
In the past I had always given a specific ID in a row this assumption that it would result in an index.
CREATE TABLE [dbo]. [EquipID] [nchar] (20) Combination SQL_Latin1_General_CP1_CI_AS zero, [EquipDescription] [nchar] (100) Combination SQL_Latin1_General_CP1_CI_AS zero, [range] [nchar] (100) Combination SQL_Latin1_General_CP1_CI_AS zero, [id] [int] detection (1,1) not at NULL [primary] is this enough?
T-SQL, SQL 2000,
If there is any suggestion, please set them a primary key.
You only get an index if you create the primary key or make a clear indices that you require by your queries It is determined that there is an index on a single column fast as long as you want to know or to join that column that the query is not there.
The indices are not too cost-effective, they increase their databases, and they increase the cost of modifying the table.
It seems to give a good overview of the old index, though.
If you are going to do a group, then reading the database like a database textbook and reading it will prove invaluable, it is difficult to find the index and the most systematic arrangement of questions, and test and error queries There is not a good way to try to optimize.
Comments
Post a Comment