Sybase :: essays research papers

Table of contentsTypes of mightinesses2Clustered baron2Non-clustered Index2Selection of kinges by Optimizer2Search Arguments2Index Selection3Index Distribution Stats3Index Density4Index Covering4Optimization of Cursors5Optimization of temp tables6 virtually general rules for optimization7Some useful commands10Types of indexesClustered Index (CI)     The info in this case is physically stored in the order of the index. The leaf level of the index is the same as the data pages. There evict be unaccompanied one(a) CI on a table as the data can physically be sorted in only one order. The select is extremely efficient with CI. The CI is extremely efficient in the adjacent casesa) where fname like "Ram%"b) where author_id between 1 and 7c) where cost > 345.34d) group by author_ide) order by author_nameNon-clustered index (NI)     The data in this case is not stored in the order an index is stored. The leaf-level of the index conta ins the different index keys and a pointer to the course of study as rowID (page no. + row offset). There can be 249 NI on a table. The NI should be used whena) The number of rows returned is small.b) When where clause limits the number of rows (usually = operator)c) When the query can be covered.Selection of indexes by OptimizerSEARCH ARGUMENTS (SARG)     These ar the expressions on the RHS of the where clause. They actuate as a kind of (dis)incentive to the optimizer to use the index on the column. Some search arguments are     where author_id = 13     where fname like "Ram%"     where Price > 2347.32Some expressions that are not valid SARGs are     Invalid                    ValidPrice*1.5 = kelvin          Price = 1000/1.5Qty + 10 = 200  &n bsp            Qty = 200 - 10fname + + lname          fname = buns     = "John Gray"               and lname = GraySubstring(1,3,fname) = KIR     Name like "KIR%"is goose egg(lname,"N") = "N"          lname is null          The index might not be used in the case of following SARGs1) No start point for the index.     where lname like "%abc"2) Non-matching data-types     In SQL server, null and not null are held differently.Char null is same as varchar. So when char null and char not null is compared, the optimizer has to implicitly convert the data type, which it does not at the planning time.      In some(prenominal) the above cases, distribution statistics arenot used.INDEX SELECTION     The optimizer primary looks at the query if the columnscontained in the where clause match with the columns specified in any of the index. If yes, then it proceeds further.     The optimizer then looks if the where clause contains any SARG. If thither is a valid SARG, the optimizer then looks for the distribution statistics of the index as