This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(275.2, 61%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESS%3C/text%3E%3C/svg%3E)
Hi Team,
I am working on to improve the performance of a Stored Procedure in SQL Server Database. Table scan is happening on a table on which there is no primary key defined. Structure of table is as such that primary key could not be defined on the table. This table is getting joined with another table.
Based on columns in Join and Where clause, I have defined Non Clustered Index on the table. Please let me know if this will help improve the performance or not OR still table scan will happen. In Dev, my table is having less data, even after applying above Index, still Table scan us getting show in query execution plan. I am hoping in upper environments where there is large data, Non clustered index will be used and performance will get improved.
Please let me know if above understanding is correct OR if there is any other way I could improve the performance and avoid table scan.
Thanks,
Salil
Does the query include a WHERE clause? How many rows in the joined table? A table scan might be more efficient than using the index but there are many other details that will help us better answer your question. Add the DDL (create statements, including indexes and constraints) for the tables involved and query (with WHERE clause if used). Consider creating the index on the heap as clustered if it's the only index on the table.