How to analyze SQL statement Performance

Analyze SQL statement performance in three ways. For more information, see

Analyze SQL statement performance in three ways. For more information, see

Method 1:
The Code is as follows:
Code provided by Minimsdn.com:
-- Turn ON [Display IO Info when execute SQL]
SET STATISTICS IO ON
-- Turn OFF [Display IO Info when execute SQL]
SET STATISTICS IO OFF

Link: http://msdn.microsoft.com/zh-cn/library/ms184361.aspx
Method 2:
The Code is as follows:
Code provided by MINIMSDN.com:
-- Turn ON [Display detail info and the request for resources]
SET SHOWPLAN_ALL ON
-- Turn OFF [Display detail info and the request for resources]
SET SHOWPLAN_ALL OFF

Link: http://msdn.microsoft.com/zh-cn/library/ms187735
Method 3:

Links: http://msdn.microsoft.com/zh-cn/library/ff650689.aspx; http://msdn.microsoft.com/zh-cn/library/aa175244 (v = SQL .80). aspx
Demo For three kinds of Method:
For SQL Script:
The Code is as follows:
Select * from dbEBMSStaging. dbo. MSSalesTxlatOrganizationMaster_Corg StagingOMC

VIts Execution plan :()

VIts IO info :()

--You can try one table with 100/10000/1000000 rows but create/don't create Clustered/NONCLUSTERED Index.

VIts Detail info Etc .:()

For SQL Script:

The Code is as follows:
Select top 100 * from dbEBMSStaging. dbo. MSSalesTxlatOrganizationMaster_Corg StagingOMC

VIts Execution plan :()

VIts IO info :()

VIts Detail info Etc .:()

For SQL Script:

The Code is as follows:
Select top 100 * from dbEBMSStaging. dbo. MSSalesTxlatOrganizationMaster_Corg StagingOMC
Order by StagingOMC. COrgTPName

VIts Execution plan :( )

VIts IO info :()

VIts Detail info Etc .:()

For SQL Script:

The Code is as follows:
Select top 100 StagingOMC. COrgTPName, COUNT (CorgID) from dbEBMSStaging. dbo. MSSalesTxlatOrganizationMaster_Corg StagingOMC
Group by StagingOMC. COrgTPName
Order by StagingOMC. COrgTPName

VIts Execution plan :()

VIts IO info :()

VIts Detail info Etc .:()

--By these three kinds of methods, you can try to check those words in the internet web are right or wrong about how to improve SQL Script performance.