August 31, 2006 at 9:40 am
A nice topic but it needs to explain what does the statistics is all about so that the execution plan can say the sql statement is optimized.
October 9, 2006 at 5:43 am
Good article. Used the exact names of the index methods many times(so it should be easy to find in the future).
However, who really needs help in tuning a simple (select somecolumn1, somecolumn2, somecolumn3 from sometable) query? Don't get me wrong, the article had value, but I never have perfomance troubles with the simple queries. The ones with 4 or more joins involved cause troubles for us to tune.
It's not just this article... I'd love to see more exaples that are closer to real world usage of a SQL server using realtional data...
I'd love to see a follow up article on this that would give us a deeper understanding of SQL tuning.
October 9, 2006 at 10:41 pm
Excellent article. It is really well explained.
Pankaj Khanna
Database Administrator - SQL Server 2000
Keep hope to keep you intact...
October 10, 2006 at 4:32 am
Goodone.Even Beginner can Understand from his explanation.Thanks Vijay!!!
October 26, 2006 at 3:37 am
Good Thumbs UP. Must read for beginner.
November 15, 2006 at 7:07 pm
As long as one understand what author is trying to explain, what language or for that matter grammer do not matter. One needs to understand, he is not teaching English. Great work VijayKumar.
April 12, 2007 at 9:19 am
Vijay,
Good Explain and i like the way of explaining.
April 21, 2007 at 2:29 am
November 14, 2007 at 4:32 am
Date: 14th November 2007
Hi Vijay!
I am Chandrajit Samanta, working in a product based s/w org (Metrica Systems Pvt. Ltd.) in Bangalore. We are using SQL Server 2000, C#, ASP.NET for our product. My work is mainly database intensive. Frequently I have to deal with heterogeneous database environment like Informix, Oracle, Sql Server simultaniously.
I have to fetch records from Informix, oracle database to our SQL Server Database. For which I have to create several DTS.
But the problem is, original tables (Informix,Oracle) has billions of records. For that to run one simple query like (Select * from Table_name where dtDate > '2007-11-01 17:00:00.000') in DTS it tooks 25min - 35min time.
We have only "Read Only " access i.e. select priviledge to all those (Informix,Oracle) database.
Please tell me how to improve such query so that this query running time is minimized.
I am waiting for your response.
Regards,
Chandrajit Samanta
MBM(Systems),B.E.(Electrical)
9986044300, Bangalore
May 15, 2008 at 8:35 am
Good Job Vijay & appreciate your sharing attitude.
Please continue posting such in future too.
November 7, 2008 at 7:15 am
Very good article for a beginner who does not have any idea about the execution plan. Thank you:)
January 27, 2009 at 5:16 pm
When giving examples, there is no need to blunder through every possible case of Table Scans before "realizing" MS SQL will only use the index scan on the column that has been indexed.
Although this is the way a beginner would do it while playing with MS SQL, there is no need to write it in your article. This only distracts the reader. It's nice to hear a different flavour of english but in many cases the meaning of your sentences was actually incorrect.
January 27, 2009 at 8:30 pm
phoqueme (1/27/2009)
When giving examples, there is no need to blunder through every possible case of Table Scans before "realizing" MS SQL will only use the index scan on the column that has been indexed.Although this is the way a beginner would do it while playing with MS SQL, there is no need to write it in your article. This only distracts the reader. It's nice to hear a different flavour of english but in many cases the meaning of your sentences was actually incorrect.
Heh... all that from someone with a handle like "phoqueme". Grow up.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2009 at 12:52 pm
Excellent article, I really like your logical approach and elegant examples. Even I did the same kind of research as you have domne on this. Both are very matching. But i lerant few more points from this article.
August 11, 2009 at 5:15 pm
Very wordy verbose article that could have been summed up in a quarter of the space. The broken English made it less fluid to read although generally understandable. Some key points missed regarding the basics of the internals of the optimiser and why some methods are more favourable than others.
Viewing 15 posts - 31 through 45 (of 53 total)
You must be logged in to reply to this topic. Login to reply