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
Analyze Query,Using SQl Profiler, Actual and Estimated Execution Plan. After then try to determine the cause of slowness.It can be any of the below mentioned reasons.
(A) Joins,Indexes,Locking Methods
(B) Cursors – If it is what affecting query performance, try to replace it with GROUP BY ..HAVING, CASE statements, SUB-QUERY
(C)Complex Stored Procedures that makes a combined use of DML and DDL statments
(D) If, there are many complex queries executed on server or if there is high activity on server, may be adding more memory, can improve performance.
(E)Schema Changes, related to any object – i.e is adding and dropping indexes, constraints etc
(F)Try to determine Logical Read Write Value,Application Name, I/O Consumption etc.
There are may tools available in market, that can be used to determine query performance. Apart from this, “It Always DEPENDS”, on how and where Queries are used.
Pinal, Today is the last day, Where is your entry?
Of course you too eligible for this prize!
Read the rules, It is for all SQL enthusiasts!
Think about optimization!
or
So, optimize it!
I’m sure you are not using Sqlserver!
After doing the obvious like checking for index fragmentation and query tuning,
Just Idera the database and you will be fine.
1. Check for blockings, if yes, find the culprit spid
2. If no blockings, check errorlog for network or I/O errors
3. If above issues not found then dissect the query and check for indexes on the columns used in query. If indexes are there, check for fragmentation. If needed reorganize/reindex the indexes based on the percentage of fragmentation followed by update statistics. If indexes are not there, we need to create them.
4. If the above conditions are not found, we need to check for waits using DMVs.
Thanks,
Amit
Well mine too…lets get some Idera tools and visit Pinal’s blog :)
“Even House isn’t doctor enough for this,… we need Idera’s SQL doctor. STAT!”
1) Analyze missing indexes with high Avg_Estimated_Impact using DMV. Key lookups, Sorts and table merge reduce the performance.
2) Determine unused indexes using DMV as they reduce performance of queries involving Insert/Update.
3) Check the fragmentation on existing indexes regularly. Rebuild if the fragmentation is greater than 40% and reorganize if the fragmentation is between 10% and 40%.
4) Do not shrink database/ files after rebuilding or reorganizing indexes. It causes fragmentation again.
5) Turn on AUTO_CREATE_STATISTICS and AUTO_UPDATE_STATISTICS which would automatically update statistics after query optimization.
6) I personally like using Idera SQL diagnostic manager as it effectively helps me in determining bottlenecks evolving from locks, deadlocks, resource Wait Stats & queues, database mirroring and replication.
7) Proper database storage planning based on traffic. I feel RAID 10 is good for faster reads-Writes and RAID 50 for faster reads.
Hi,
To Spped Up your Query Have this in your Query
1) use WITH(NOLOCK) in select statement
2) Use SET NOCOUNT ON and SET NOCOUNT OFF In begining and End of your query Which will reduce the network Band Width.
3) Create Proper Clustered and Non-Clustered Indexes On the table
4) remove Sorting in Query(this Can be handeled in Front End Code Ex : using LINQ in .NET).
5) using “parallellism” featur In sql 2008 R2 gives better performance.
6) Run the Query by Enabling the “Actual Execution plan” in SQL Server, Which will suggest What need to be Done for the Query to Speed Up(Ex : Create Non Clustered Index On table) And Also it will Show Which part of the Query is taking Much Time to Execute.
7) use “client Statics” while running the Query this will give you the “Total Execution Time” by this we can analyse and can write Query in better way.
8) avoiding Complex joins in Query
1.Query Plan that Included Nested Loop for many Rows.
2.Check for Proper Indexes.
3.Update Statistics.
4. Check if theres too many joins.
5.Check for parallelism.
6. Check if the Query is using dynamic sql.
these are few of them, there are so many things which we can look.
I’d definitely start by looking at the indexes, but the general consensus seems to be go with Idera.
You don’t know why? Just get Idera, and it’ll solve ALL of your problems!
Try to power on the server =)
Let’s just switch to NoSQL — I hear it’s always much faster … *snort* sorry, I can’t say it with a straight face!
Here’s an Idera, use SQL Doctor to analyze, diagnose, and fix your queries, all automagically!
A Haiku for you:
I have Idera
SQL Doctor diagnose
fix those slow queries
I would have looked in the following format.
1. sp_who2 to running processes
2. Inefficient query
3. Run the query execution plan
4. Identify the issue according to execution plan
a. Index/Table Scan or SEEK
b. Columns in query vs Columns in index
5. Index fragmentation.
6. Table Statistics
7. Which version of SQL is it ? If 2008 or above maybe resource governor is strangling the resources.
_
I recommended Idera to the boss; he said, “We can create that here, we’re a development shop!” So, I proposed we recruit Idera developers.
_
Check for Joins used.
Identify area slowing it.
Check unused Indexs
check Qry using the indexs.
use tables filetring more data to be placed Ist.