SQLAuthority News – Win Windows Phone from Idera in 140 Characters – A Cartoon Challenge of SQL

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.

SQLAuthority News - Win Windows Phone from Idera in 140 Characters - A Cartoon Challenge of SQL wp7

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.

SQLAuthority News - Win Windows Phone from Idera in 140 Characters - A Cartoon Challenge of SQL slowquery3

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)

SQL Index
Previous Post
SQL SERVER – MondayMeme – 11 Words or Less
Next Post
SQLAuthority News – TechED 2011 – Bangalore – An Unforgettable Experience – Day 2

Related Posts

209 Comments. Leave new

  • Queries Slow, Call the SQL Doctor. Queries still slow, call the SQL Server Superhero with his Diagnostic Manager power skills. With his x-ray query vision, he will remedy the situation in no time.

    Reply
  • Lot of reasons for query to run slow. Troubleshoot manually may tak a day bt I hav SQL Doctor, I will fix it Just Like That while u hav a coffee

    Reply
  • The answer would be
    “Bring the Pinal Dave out of you, check Indexes write proper queries”

    Reply
  • Check your index for the columns used in where clause.
    Put only numeric fields in the where clause if possible.
    Create indexes for these.
    If still slow call Pinal to fix the issue.

    Thanks
    Shyam

    Reply
  • Did the query ever run fast? Do you have a base line to compare it? What helped you to identify that?

    Reply
  • EXEC sp_MSforeachtable ‘PRINT ”?” UPDATE STATISTICS ? WITH FULLSCAN’
    EXEC sp_MSforeachtable ‘PRINT ”?” DBCC DBREINDEX (”?”)’

    Reply
  • I have Extended Events to help me understand why it is slow. Let me create a XEVENTS session to see what that query is doing.

    Reply
  • Do you have a baseline?
    What changed recently?
    Is it slow always?
    How do you know it is slow?
    Is it written by following T-SQL best practices?

    Reply
  • ans : Contact to pinal….

    Reply
  • Just start SQL diagnostic manager and you are done.

    Reply
  • -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 partitioning

    Reply
  • Jungchanhsieh
    April 6, 2011 12:14 am

    Slow network,.
    Inadequate memory in the server,
    L of useful stat.,
    L of useful indexed v,
    L of useful data striping, and L of useful partit.

    Reply
  • Jungchanhsieh
    April 6, 2011 12:19 am

    SQL diagnostic manager #idera can get you all the answer #queries_go_slow

    Reply
  • If you have no idea – switch on Idera !!!

    Reply
  • 1. Look for index fragmentation from: sys.dm_db_index_physical_stats.
    Based on the results displayed, reorganize or rebuild indexes

    2. Update your stats

    3. Look at the execution plan and create new indexes & stats if necessary.

    4. Find out the exact reason for your slow query, if its works good today and works slow on the next day, then check if you have any job or process which is populating data into the table and see if you have any fragmentation using the DMV mentioned in setp 1.

    Reply
  • Hi..

    1) reduce use of join and possibly use sub-queryies
    2) Manage indexings
    3) if possible keep most frequent required table data as less as possible,by making archived dataTable. same for “isDeleted” Flagged. it will help to retrieve routine records faster.

    Reply
  • No hablo ingles! Could you please go to Idera website that they do speak english and SQL?

    Reply
  • Adam Poirier
    April 6, 2011 4:33 am

    Well, that’ll make them easier to catch.

    Reply
  • Database design may be good, but queries are not optimized.

    Reply
  • Rohan R Arora
    April 6, 2011 7:52 am

    Let Idera figure it out the exact health/condition of the system. Meanwhile lets discuss taking uour business one step further over a cup of coffee.

    Reply

Leave a Reply