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
“I think you need a doctor, Idera SQL Doctor !!”
That’s why i was suggesting to Hire Pinal Dave.
Now first Analyze the Queries then make a strategies to overcome the problem with in given time/resources
Check the below listed reasons for slow-running
* Slow network communication.
* Inadequate memory in the server computer, or not enough memory available for SQL Server.
* Lack of useful statistics
* Lack of useful indexes.
* Lack of useful indexed views.
* Lack of useful data striping.
* Lack of useful partitioning.
“if any of reason makes your query works slow work on it ,Otherwise problem in your query – check your query”
-Give Large size to Database at the time of creation instead of default size 2 mb give it few GB so that at the time of insert it need not to take time to allocate new space
-Normalize your tables
-Use cursors wisely
-Index frequently used Columns, don’t use to much indexing
-Increase timeouts
-Always qualify the full list of columns in SELECT Query.
-Go through Pinal Dave’s Guidline for SQL.
Go to the nearest “SQL DOCTOR”and said him that you are suffering from Lack of Index Optimization.He will prescribe you the right medicine for that.
“geeee, let me see, have you tried to google it?”
or
“lets call Kenneth, the sql wizard”
Profile it, PerfMon it or better Diag’Man it
Optimize your query, Check Database (mirror, replication etc.), SQL Server, Hardware and Network configuration, Other processes.
hi,
1. Use Apply while using nested queries.
2. Index the ORDER-BY / GROUP-BY / DISTINCT Columns for Better Response Time
3. Use Subqueries instead of joins.
4. Change OR to UNion
My answer is the same as answer of the winner :)
Need To Rethink On Database Design 70% Issues Are There.
That’s not what Idera SQLdm says, it says you need an index!
SELECT TOP 1 Name
FROM tools
WHERE Vendor = ‘Idera’
AND Type = ‘Performance’
ORDER BY Rating DESC
Obviously you must swap out SQL Server for NoSQL. Tell me how long that will take.
I may have an Idera that can help
Then why don’t you send your queries to Idera Hospital to check by the Idera doctors? What an Idera Sirji…
slow query can be due to any of the issues..
– check processes related to the query, blocks if any
– see execution plan of the query
– see sql server performance wrt memory, cpu,io. run performance monitor if needed
– if you have tool like idera DM or sql sentry check thru the tools
-see waittype of the spid, and proceed further if that is a IO related issue or network related issue etc
– if the query was fine all the days, and its slow today see if the indexes are fragmented due to some data DMLs done recently, do update statistics of the related tables in an highly OLTP environment without blocking the system for other queries
Try to limit the usage of outer joins.Always keep your indexes as narrow as possible.Also don’t index small tables.So go and Get IDERA.. :)
Not for award but for fun, the reply should be…
“Yeah, I have heard MS SQL Server is better than other RDBMS and it has various options available to get optimum performance. Looks it time to upgrade to MS SQL Server. Developers have done great job so far but now we should also hire some DBAs.” :-)
“…. Also, Idera has various tools for MS SQL Server troubleshoting”
Use following products
1 SQL Defrag Manager
2 SQL Doctor
3 SQL diagnostic manager
4 SQL Check
Google each product to know more.