I personally have Windows Phone and I love it. The user friendliness and integration with social media is remarkable. My wife Nupur is big fan of Windows Live tools and Windows Phone as well. Well, this blog post is not about our preference of Windows Phone but about YOU a unlocked Windows Phone. The Windows Phone will be directly sponsored by Idera.
If you want to win Windows Phone. Just do one thing, complete following cartoon. Every day queries go slow and we think it is SQL Server but the reality is that it is us who need to know the right technology. Idera provides tools for Microsoft SQL Server, SharePoint and PowerShell management and administration.
Contest Rules:
- Answer must be of maximum 140 character.
- Winner will get Windows Phone or USD 500 Gift Card from Idera.
- No purchase is required.
- This contest is open to all SQL enthusiasts in the world.
- Recipient will be responsible for local taxes.
- Idera has all the rights to alter, or modify the competition.
- To participate please a comment to this blog post.
- One person can participate multiple times.
- The contest is open till April 20th, 2011.
- Winner will be announced on April 25st, 2011.
- Phone image is for illustration purpose.
Note:
- Promote at one more social media place the answer to the question.
- Comments are moderated for spams and SEO marketers, if your comment does not appear, please send me email.
- Mentioning Idera in answer is encouraged but not necessary.
Reference: Pinal Dave (https://blog.sqlauthority.com)
209 Comments. Leave new
You may not be a reason for that! Do a review on Query level, Database level, Server level and Network level. Performance is a joint effort.
You should hire @pinaldave, he know what to do!!!
Lets use this
1) Optimize your queries , if it has joins
2) Use DBCC commands, CHECKDB
can list out all the errors with DB
and reindexing can make the Query Run faster
Use DBCC DBREINDEX
– Optimize your queries , if it has joins
– Use DBCC commands, CHECKDB
can list out all the errors with DB and reindexing can make the Query Run faster Use DBCC DBREINDEX
Let me see those queries first, then decide!
1)Manage Indexing in every respect.
2)Reduce the unnecessary Columns return,avoid select *,OR,Like Plague,Specify Table Qualifiers,Joins
3) Inadequate Memory in server
4)use Useful partitioning.
1. Investigate the SQL Server Environment & H/w configuration
2. Identify & tune the worst performing queries
Hi Pinal,
My View over “My Quries Running Slow”
1. The sys.dm_db_index_usage_stats DMV will be introduced as a tool to identify existing indexes which your queries may not be using. Indexes that are not being used will provide no benefit to your databases, but will use valuable disk space and slow your update operations, and so they should be considered for removal.
2. After creating an index, make sure you verify that the index is, in fact, used in a plan
3. SQL Queries must be write in manner so they can reuse plans.
Example:
Use sp_executesql instead of Exec .
4. SQL Server does not maintain statistics for XML and spatial data types. That’s just a fact, not a problem. So, don’t try to find statistics for these columns, as they’re simply not there.
Solution:
If you experience performance problems with queries that have to search through XML data, or filter spatial columns e.g., XML or spatial indexes may help. But that’s another story and beyond the scope of this article.
5. Perform Reindexing on a table which is altered recently so that it can use index’s in optimized way.
6. If possible, re-write your SQL Code so that comparisons are only done with “pure” columns. So e.g. instead of specifying
where sqrt(c1) = 100
You would do better to write:
where c1 = 10000
7. If you are going to create a index on a table then FillFactor is most important thing if your table rarely have insert and updates then fillfactor can be 0 or 100 if your table can have insert and updates frequently then it should be 80,90…or whatever perfact.
8. Carefully inspect, if your queries can make use of multi-column statistics. If so, create them manually. You may utilize the Database Engine Tuning Advisor (DTA) for regarding analysis.
9. Improve your TSQL Code. Avoid using local variables in TSQL Scripts or overwriting parameter values inside stored procedures. Don’t use expressions in search arguments, joins, or comparisons.
10.Avoid NOT IN, instead use a left outer join – even though it’s often easier to visualize the NOT IN.
Thanks For this Great Competition
Thanks Idera Too.
NOTE:This Article Refers many SQL Web Sites.
Sorry… “Fast queries” have ended already… Try to repeat it tomorrow.
• Rebuilt index if they are defragemented
• use proper joins
• remove index hints if any
• minimize the use of string operation, use computed columns instead
• avoid the use of functions
“Ohhh!! This is a serious problem which can be treated only at Idera. Get to Idera and ask for SQL doctor v2.0. He is an expert in treatment of such diseases”
Let me analyze those queries!
Tools such as Idera, are available in the market to make things faster & easier. If needed we will go for it.
commonly
Slow network communication.
Inadequate memory in the server computer or for SQL Server.
Lack of useful statistics,indexes,indexed views,data striping,partitioning.
Check for AUTO_CREATE_STATISTICS,AUTO_UPDATE_STATISTICS are ON
Use of Database Engine Tuning Advisor
implement Disc Striping via RAID.
Consult pinal and and your problem will be solved poor chap!!
Cheers
Hi,
as per the expression the person who has to answer doesn’t care for why it is happening ,
Therefore my answer is
” so what can i do? “
Oh you have the “Common App Person Syndrome”. Take Specificity test for Query, Recent app changes, index, Query plan, Stats and see DBA Doc.
Sh! I will tell you a MS Certified affordable diagnosis secret! Idera Dignostic Manager! Top Notch
“I have a great IDERA!”
just log on to
Analyze and Get Idea!
What an Ide(r)a Setji!!!