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
‘DMVs can help but Diagnostic Manager helps better!’
Hi,
Original reply of this employee in the cartoon was : “Create Index On It” :D
However,as per I have read,I think in performance tuning(along with indexes)–Logical Query Processing, Efficient Join Techniques,Query Tuning etc. can help… :)
Jeet.
Rather than guess at why a given query is performing slow, thousands of scans, putting your I/O through the roof, you can use the execution plan to identify the exact piece of SQL code that is causing the problem……
1) Update Statistics which are out of date.
2) Create missing indexes and drop un-used Indexes.
3) De-Fragment Indexes which have fregmentation > 10 %.
4) Insert appropritate Fill Factor, if it is an OLTP database
5) If feasible remove Joins and use sub-queries instead.
6) Use Wait Types and Queues to Get Quick Performance Bottleneck and resolve accordingly.
“Its time to run Tuning Advisor”
Check the indexed views. Redesign the query if necessary. Update outdated statistics. Check network communication. Do partitioning. Check/Create indexes.
It is ideal case for Query Performance or Server Performance.
1) It can be case that everyday the query is running perfectly but today only it is running slow.
Then in this case, we need to check server Performance with DMVs, perfmon with specific counters, Task manager and others to find out possible issues with Memory, Disk, CPU related congestion.
2) If query is running slow daily, then it can be problem with query, statistics, execution plan, index fragmentation and so on..
Depending on the case, the troubleshooting has to commence.
Look for the execution plan and the flow of execution , query
hints ex: option(force order) might help solve the problem.But be cautious ..
Following reasons may cause to queries slow.
1) sql server,OS, Network and System configuration is not proper.
2) DATABASE DESIGN is poor.
3) Query Planning is poor.
4) Missing Indexes or Wrong Indexes.
5) No proper additional statistics.
6) No Partitioning (for large volume data).
7) No data striping.
1.Look for SQL Server wait stats
2.Find the most expensive queries and try tunning them .
2a.Look for query statistics
3.Look for plan recompilations.
4.Look for update Statistics options if necessary.
5.Check for queries taking parallelism into their work flow
taking the system into account i.e OLTP or OLAP
1) Enable Database indexing
2) Check for the server statistics
3) Check for available hardware resources
4) Try to make your query simple by adding additional computing.
Above steps will surely improve performance
Try the new “SQL doctor” from Idera ! It will identify inefficiencies in your syntax query.
Are queries performing slower then given benchmarks? If you are not adopting a proactive approach and it’s just a random guess that queries are performing slow, then possibly, we have to do lot of RANDOM things to rectify the problem. 99% such problems occurs when you are not prepared and do not watching your database closely. Must set performance benchmarks, must have proper tools and scripts in advance and always adopt proactive approach.
Try following Things:
1. Update statastics
2. Rebuild Indexes and drop not reqired Indexes
3. Check the joins and use effecient Joins.
If Problem is still there then we need to analize the issue using profiler and can suggest the solution.
We can analyze from the below query….
SELECT * FROM sys.dm_os_wait_stats
“You’ve no Idea ?? Get Idera !!”
1. Properly manage indexes.
2. Only usable indexes placed.
3. Remove unwanted indexes which will hold the unnecessary space of server.
4. Use sql server 2008 R2 for use the feature of parallellism for better performance.
nice ans…..
5. Also you can improve query performance by Execution plan, By eliminating Sort, Key Lookup, Table Merge etc. You can improve performance accordingly.
5. Also show the excecution plan and try to remove Sort, Key Lookup, Table merging. Which will help you to improve the performance of query.
Create Proper Index and Join them in your Query!
“heard something called an index?”
or “have you heard of tuning?”