• yuvipoy (3/6/2014)


    Thanks Sean!

    I got it we should not go with cluster index for guid since this will cause physical ordering of the data on the disk which is pointless one.

    It is the logical order not the physical storage order. Using a guid for a clustered index produces a very high frequency of page splits which is why the index gets so fragmented.

    One more thing

    how about Selecting the statement

    Select <set of columns> from table where Col_uniqueidentifier={uniqueidentifier}

    say now if the column is with py key non cluster index with 10 million record will the query will be faster to return data ?

    or the query with col_bigint column instead of col_uniqueidentifier

    Select <set of columns> from table where col_bigint ={bigint }

    say now if the column is with py key (non) cluster index with 10 million record will the query will be faster to return data ?

    Can you suggest on this

    In general it will be a bit faster because a guid is 16 bytes where a bigint is only 8 bytes. It is not likely to make a huge difference.

    _______________________________________________________________

    Need help? Help us help you.

    Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.

    Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.

    Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
    Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
    Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
    Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/