SQL SERVER - Rules for Optimizining Any Query

home
database
view story

25 Kicks

SQL SERVER - Rules for Optimizining Any Query - Best Practices(blog.sqlauthority.com)

submitted by pinaldave(9662) 3 years, 4 months ago

This subject is very deep subject but today we will see it very quickly and most important points. May be following up on few of the points of this point will help users to right away improve the performance of query. In this article I am not focusing on in depth analysis of database but simple tricks which DBA can apply to gain immediate performance gain.

4 comments |category: Database |Views: 646
Tweet

tags: BUT CAT ABIT pinaldave WANK another

Everyones tags:

Your Tags:

Please login or signup.

Add a live kick counter to your blog >> liveImage

You can even customize the image by choosing your own colors, and then clicking the button below to update the preview and the html code:

"Kick It" text
"Kick It" background
kick count text
kick count background
border

Simply copy and paste this HTML into your blog post.

Users who kicked this story:

More who kicked this story...

Comments:

posted by cdbh(0) 3 years, 4 months ago 0

As usually I love it.

I kind of doubt your opinions sometime but this time... good.

posted by pinaldave(9662) 3 years, 4 months ago 0

It will be really good that if you guys would share your own opinion at original blog post.

Regards,
Pinal

posted by wisemx(8074) 3 years, 4 months ago 0

...Several things you mentioned in the article are controversial at best.
Makes me wonder if you are simply fishing for comments/input with this one.

posted by bartczernicki(503) 3 years, 4 months ago 0

SqlAuthority is a nice blog for beginner/intermediate info on SQL. There isn't much original content there.

Specifically to this article, I agree with the post above...these "rules" really depend on the type of databases you create and maintain. Databases with complex business process, read-only databases, high write/read databases, 64/32 bit and enterprise/standard versions, sql that is multi platform (Oracle, SQL), data warehouses etc all has different best practicses and rules.

Saying that you need to put an clustered index on a table is a beginner tip. Explaining why you shoul do it with specific examples on how this effects storage, wide tables, nonclustered indexes, seperating in different storage groups would be a nice advanced tip.

Most Active Users

What's this?