As you said we have to drop the clustered index and then do insert. But you also said non clustered index is faster when dealing with bluk dml statements so can't we do one thing that after dropping the clustered index as it makes bulk insert slow we can create non clustered imdex on the same column where primary key is created and after that if we do insert then I think it will be more faster than normal insert what you say on this
One thing you have not mention that non clustered index root node will internally search the cluster index then find the record . Without sorting how can a query be faster
Subscribe My Vlog Channel: www.youtube.com/@pandeygurujivlog
Subscribe Technical Channel: th-cam.com/users/studyiteducation
Facebook: facebook.com/pandeygurujivlog
Excellent video Pandey.
Your all videos are ossum sir
Thanks a lot
Please make more videos on performance tunning and 2. purge and archive activity.In hindi 🙏 Please
As you said we have to drop the clustered index and then do insert. But you also said non clustered index is faster when dealing with bluk dml statements so can't we do one thing that after dropping the clustered index as it makes bulk insert slow we can create non clustered imdex on the same column where primary key is created and after that if we do insert then I think it will be more faster than normal insert what you say on this
You're doing great job bro love you please upload more
Thank you, I will
Thank you sir
Welcome
Instead of drop can we Disable the index and enable??
One thing you have not mention that non clustered index root node will internally search the cluster index then find the record . Without sorting how can a query be faster