| Author: Hari 01 Nov 2009 | Member Level: Gold | Rating:  Points: 2 |
Hi,
The following articles will help you
http://msdn.microsoft.com/en-us/library/ms998577.aspx
|
| Author: Rajesh.Dharmakkan 01 Nov 2009 | Member Level: Gold | Rating: Points: 2 |
http://www.dotnetspider.com/resources/28616-Optimizing-sql-server-queries.aspx
Plz Rate My Response
Regards
Rajesh.Dharmakkan
|
| Author: Melchior 01 Nov 2009 | Member Level: Gold | Rating: Points: 2 |
The SQL Server Performance depends on two factors. They are
Creation of Execution plan and
Execution of SQL queries based on the execution plan
So you need to pay attention on both factors.
Regarding Execution plan:
http://www.codeproject.com/KB/database/sql-tuning-tutorial-1.aspx
Regarding Query:
http://www.devshed.com/c/a/MySQL/SQL-Performance-and-Tuning-Considerations/3/
|
| Author: Sridhar 01 Nov 2009 | Member Level: Silver | Rating: Points: 2 |
Every index increases the time takes to perform INSERTS, UPDATES and
DELETES, so the number of indexes should not be too much. Try to use
maximum 4-5 indexes on one table, not more. If you have read-only table,
then the number of indexes may be increased.
279
v Keep your indexes as narrow as possible. This reduces the size of the index
and reduces the number of reads required to read the index.
v Try to create indexes on columns that have integer values rather than character
values.
v If you create a composite (multi-column) index, the order of the columns in
the key are very important. Try to order the columns in the key as to enhance
selectivity, with the most selective columns to the leftmost of the key.
v If you want to join several tables, try to create surrogate integer keys for this
purpose and create indexes on their columns.
v Create surrogate integer primary key (identity for example) if your table will
not have many insert operations.
v Clustered indexes are more preferable than nonclustered, if you need to select
by a range of values or you need to sort results set with GROUP BY or ORDER
BY.
v If your application will be performing the same query over and over on the
same table, consider creating a covering index on the table.
v You can use the SQL Server Profiler Create Trace Wizard with "Identify Scans
of Large Tables" trace to determine which tables in your database may need
indexes. This trace will show which tables are being scanned by queries instead
of using an index.
|