You can not have more than one cluster index because the data in the table gets changed directly, hence you can not able to create/ have second cluster index in a table.
Hi Sir, Can you provide individual videos on below topics if you have Indexes Statistics Query Processing Understanding Execution Plans Identifying Query Issues Query Performance Hints and Plan Guide SQL Profiler
Hello Everyone, I added another new course called “ SQL Server 2012 : Performance Tuning in Action with 100 million + rows”. It is going to be started very soon. For complete course description and other details, please contact me at kranthi.sqlserver@gmail.com. Technical Highlights: • Analyze performance bottlenecks • Analyze the SQL query Performance • Design an effective index strategy • Database Engine Tuning Advisor • Analyze Dynamic Management Views (DMVs) • Analyze Statistics and Fragmentation levels • Diagnose and avoid blocking and deadlocks • Analyze execution plans • Develop efficient queries and stored procedures • Analyze and Design the effective query to INSERT a large volume of data ( 100 Million + rows) • Analyze and Design the query to UPDATE the large volume of data ( 100 Million + rows) • Cursor Cost Analysis vs SET based Analysis • Limitations on MERGE statement • How to manage and deal with Enterprise Production server issues Thanks, Kranthi Microsoft Certified Professional Kranthi.sqlserver@gmail.com
Sir i Have one question why do we have only one Primary Key per table Please correct me if i am wrong that Pk uses unique index(clustered or nonclustered) to enforce uniqueness but we can create multiple unique indexes per table i want to get the logic is it as per relational db guidelines that a table can only have one Pk or is there any other technical reason ?
This video is clear about my very long unclarity concept. Awesome explanation... Thanks.
Awesome Video. Thanks for sharing . It really simplifies the concept of Clustered Index and Non clustered Index .
You have depth knowledge in Index Structure.Good thank you shring this vedieo.
Thank You very much!!! for sharing the knowledge. First time I exactly understood the functionality of Index and their Architecure.
Nice explanation . Thanks
Your Explanation is amazing sir......Thank you very much.......
You're just too Good, This video really helped me a lot....
Thanx for Solving my doubt
Good Video to understand indexing concept.
I love your videos morethan anything ...........
I like your videos a lot.on this chapter, it would more understandable if you have picked a ID for example. Please keep posting.
Thanks cleary understand index concept
Yes. You have to calculate based on the datatype.
You can not have more than one cluster index because the data in the table gets changed directly, hence you can not able to create/ have second cluster index in a table.
Hi Sir,
Can you provide individual videos on below topics if you have
Indexes
Statistics
Query Processing
Understanding Execution Plans
Identifying Query Issues
Query Performance
Hints and Plan Guide
SQL Profiler
Good video , but i found change in value in leaf level and middle level page last table value is differing 410, 411, why is it so?
Hello Everyone,
I added another new course called “ SQL Server 2012 : Performance Tuning in Action with 100 million + rows”.
It is going to be started very soon. For complete course description and other details, please contact me at kranthi.sqlserver@gmail.com.
Technical Highlights:
• Analyze performance bottlenecks
• Analyze the SQL query Performance
• Design an effective index strategy
• Database Engine Tuning Advisor
• Analyze Dynamic Management Views (DMVs)
• Analyze Statistics and Fragmentation levels
• Diagnose and avoid blocking and deadlocks
• Analyze execution plans
• Develop efficient queries and stored procedures
• Analyze and Design the effective query to INSERT a large volume of data ( 100 Million + rows)
• Analyze and Design the query to UPDATE the large volume of data ( 100 Million + rows)
• Cursor Cost Analysis vs SET based Analysis
• Limitations on MERGE statement
• How to manage and deal with Enterprise Production server issues
Thanks,
Kranthi
Microsoft Certified Professional
Kranthi.sqlserver@gmail.com
Sir i Have one question why do we have only one Primary Key per table Please correct me if i am wrong that Pk uses unique index(clustered or nonclustered) to enforce uniqueness but we can create multiple unique indexes per table i want to get the logic is it as per relational db guidelines that a table can only have one Pk or is there any other technical reason ?
if you might explained about fillfactor also it would be good
Please can u explain page splitting after 4060226 rows with intermediate pages
nice explained
Good One.................
thank you very much
Thank you
thank you.