I do not understand why 18,000 lines of information can lead to too much slowdown, but it is obviously not visible what data you are storing.
If you regularly use the Column_1 field, I would suggest you place a non-clustered index on it ... this will speed up your query.
You can do this by designing your table through Sql Server Management Studio or directly through TSQL ...
CREATE INDEX IX_myTable_Column_1 ON myTable (Column_1 ASC)
Read more about MSDN about creating indexes here.
Update thanks to the @GarethD comments that helped me with this since I didn't know about it.
As an additional part of the above TSQL statement, this will increase the speed of your queries if you include the names of other columns that will be used in the index ....
CREATE INDEX IX_myTable_Column_1 ON myTable (Column_1 ASC) INCLUDE (ID, Name)
As GarethD points out, using this SQLFiddle as evidence , the execution plan is much faster because it avoids the “RID” (or Row Identifier) lookup.
Learn more about MSDN about creating indexes with columns included here.
Thanks @GarethD
source share