Pulse » Popular Items from 4/22/2009

Welcome!

Pulse has a simple goal: to give you a quick view of what's happening in the SQL Server community.

  • Browse

    Finding interesting content on Pulse is easy – you can drill down to a specific time period (by clicking on the bars of the chart), toggle different types of content on and off, and sort the results by popularity or recency.

  • Vote

    Discovered an informative blog post or a hilarious tweet? Tell the rest of the community about it by voting it up or down. Behind the scenes, our popularity algorithm will make sure it rises to the top of the list.

  • Comment

    When a simple up-or-down vote isn't enough, voice your opinions in a comment. Or check out what others are saying about something you posted or tweeted.

April

  1. 17
  2. 26
  3. 316
  4. 41
  5. 53
  6. 64
  7. 79
  8. 87
  9. 96
  10. 105
  11. 113
  12. 122
  13. 138
  14. 149
  15. 1515
  16. 168
  17. 174
  18. 186
  19. 191
  20. 209
  21. 2115
  22. 228
  23. 237
  24. 244
  25. 251
  26. 265
  27. 275
  28. 2813
  29. 2925
  30. 309

22

  1. 12 A0
  2. 11
  3. 21
  4. 30
  5. 40
  6. 50
  7. 60
  8. 70
  9. 80
  10. 90
  11. 100
  12. 110
  13. 12 P1
  14. 11
  15. 20
  16. 31
  17. 41
  18. 50
  19. 61
  1. SQL SERVER – FIX : Error: 18486 Login failed for user ’sa’ because the account is currently locked out. The system administrator can unlock it. – Unlock SA Login

    Today, we will riffle through a very simple, yet common issue – How to unlock a locked “sa” login? It is quite a common practice that SQL Server is hosted on a separate server than application server. In most cases, SQL Server ports or IP are exposed to the web, ...

  2. SSWUG vConference, Day One

    The first day of the SSWUG vConference has come and gone. Despite a handful of technical issues, the day must be considered a rousing success. The quality of the content, the quality of the video, and the quality of the live chat sessions was far above average. Now, since I ...

  3. SQLSaturday #13 - 3 days to go

    Holy cow, I’ve got a lot left to do. I know this is probably boring for most of you, but this post is mainly going to be a list of unfinished business. I’ve to to make the list anyway, and I’m committed to making at least one ...

  4. How Did I Get Started?

    Just when I thought I might be getting my chaste back, I got tagged again, this time by SQLChicken. Just the thought of chicken wrapped in bacon being served on a skewer at the Rodizio Grill was enough to make me want to respond to this latest web chainpost. Honestly ...

  5. Book Reviews

    While looking over the SQL Blogger Rankings a thought crossed my mind: Why not do something similar with books? So, I have decided to create a new page with some widgets that display books related to various topics. Right now, there are two libraries to choose from, a technical library ...

  6. What Causes Deadlocks?

    Application code, that’s what causes deadlocks. And what I mean by that is that the database engine does not suddenly seize up and start deadlocking transactions arbitrarily because it is tired one day. No, certain conditions must exist in order for a deadlock to happen, and all of those ...

  7. Starting the SQL Journey

    Jorge Segarra aka @SQLChicken tagged me in a quiz asking how DBAs got started in the business, and I can’t believe I haven’t blogged about this earlier.  Great question. I Started as a Developer That’s right - I was one of THEM. But wait - it gets better.  I ...

Pulse is a section of SQLServerPedia that gives you a quick view of what's happening in the SQL Server community.