Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Clustered Index Expand / Collapse
Author
Message
Posted Saturday, July 18, 2009 10:03 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Monday, July 26, 2010 12:59 AM
Points: 42, Visits: 108
Dear Friends

Is this true that Update SQL Query is slower because of Clustered index??????

currently i have cluster index on ID columns which have the primary key

How can i indentify the which column should have the Clustered index???

below i m attached my table defination...


  Post Attachments 
table_def.txt (29 views, 3.50 KB)
Post #755310
Posted Saturday, July 18, 2009 10:42 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Yesterday @ 9:44 AM
Points: 42,822, Visits: 35,953
maxyogesh2002 (7/18/2009)
Is this true that Update SQL Query is slower because of Clustered index??????

Unlikely. Nonclustered indexes may slow a data modification down, because the change has to be made in multiple places, but that shouldn't be true of a clustered index because it's not a second copy of the data

currently i have cluster index on ID columns which have the primary key

How can i indentify the which column should have the Clustered index???


An identity's usually a fairly good choice for a cluster. It's narrow, unique and can't be changed plus the values for new rows are always higher than old, reducing fragmentation. I can't say if there's a better choice without knowing something about the data and how the table is used.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #755317
Posted Saturday, July 18, 2009 10:48 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Monday, July 26, 2010 12:59 AM
Points: 42, Visits: 108
i m attached the my table defined above...
Post #755319
Posted Saturday, July 18, 2009 10:52 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Yesterday @ 7:27 PM
Points: 33,204, Visits: 15,351
The decision on what to make a clustered index is more based on the queries made against the table, not the definition. You would want those queries that look for a range of values, usually a date or other range to be considered. Typically I haven't picked the identity as the CI, but that's because I often have a better candidate, not because it's bad.






Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #755320
Posted Saturday, July 18, 2009 12:18 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Yesterday @ 10:11 AM
Points: 36,995, Visits: 31,516
First of all, that table is setup for CDR's (Call Detail Records). Rather I should say it's set up incorrectly for CDR's. Almost all of the columns are setup for VARCHAR(255) and the world of code is going to crawl because of all the implicit and explicit conversions you will need to make to rate, bill, and invoice the CDR's. Step 1 should be to assign the correct datatypes for each column.

Second... How often will you be inserting rows that are out of date order compared to what's at the "end" of the table? If it's a lot and your CI is on the date, you will get a lot of page splits. If it's a lot and your CI in on the autonumbering column, then you're inserts will be fine but your SELECT's may suffer a bit. It's a tradeoff depending on what the table will be used the most for... Inserts or Selects.

Are you going to use the contents of this table for rating and billing or are you just capturing CDR's for long term audits? And what's the source of information for this table? If it's coming directly from one or more switches as the calls occur, then you will definitely want the CI either on the IDENTITY column or on the call date time column.

No matter what, you really should fix the datatypes as previously stated.


--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #755337
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse