Pulse » Recent Items from 6/28/2011

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.

June

  1. 19
  2. 217
  3. 310
  4. 41
  5. 512
  6. 615
  7. 718
  8. 827
  9. 942
  10. 1041
  11. 116
  12. 1213
  13. 1350
  14. 1451
  15. 1535
  16. 1643
  17. 1740
  18. 189
  19. 197
  20. 2064
  21. 2143
  22. 2236
  23. 2339
  24. 2441
  25. 2512
  26. 268
  27. 2739
  28. 2853
  29. 2938
  30. 3064

28

  1. 12 A0
  2. 12
  3. 21
  4. 30
  5. 42
  6. 52
  7. 60
  8. 71
  9. 82
  10. 93
  11. 100
  12. 110
  13. 12 P3
  14. 16
  15. 26
  16. 33
  17. 42
  18. 52
  19. 61
Home

  1. Let’s Get Registered! Registered!

    The PASS Summit is only a few short months away.  But before that happens there is an important deadline fast approaching… the end of the pre-June 30th discount.  For the last few months, you could save $600 off the cost of the regular entry fee.  But on Thursday it all ...

  2. Instead Of Trigger and OUTPUT clause headache

    It is known that you cannot get inserted identity values using OUTPUT clause when inserting to view which has instead of trigger on it. I would like to offer another workaround I was used recently. I am talking about fact that you will not succeed with this: -- inserting records ...

  3. Instead Of Trigger and OUTPUT clause headache

    It is known that you cannot get inserted identity values using OUTPUT clause when inserting to view which has instead of trigger on it. I would like to offer another workaround I was used recently. I am talking about fact that you will not succeed with this: -- inserting records ...

Home

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