Using triggers to protect your database from developers – still not a good idea

A long time ago I mentioned that triggers is rarely a good option in your database. I recently read this article (requires free registration) that shows you a solution to prevent developers from updating a full table (or deleting it all) by mistake because they failed to ad a WHERE clause to their query. Is this a good…

0

SQL server backup myths

Any kind of backups other than straight file copies have Always been magic to me. Mostly because in the early years of my career it was so rare that the backups actually worked when needed because nobody evern tried the backups to see if they were actually working… This post (free registration needed to read)…

0

Azure Websites and logs that are no longer updated

Last weekend I helped my father-in-law (who is hosting his company web site on azure websites) troubleshoot why he was no longer getting any more data in the web server logs. Logs that he uses to analyze what content is popular. Well it turned out that you should read the FAQ… Once your logs reach…

0

Asynchronous enumerations – summary

So what did we end up to do after the discussion two months ago? Well we ended up using option #1 mostly because it simplified things to have all items available during processing. technically not needed, but it simplified things. My generic advice would be to use option #1 or #2 and to favor option…

0

Asynchronous enumerations – Part 5: MyEnumerationAsync

For background, read the introduction. If you have no need for filtering using LINQ (or Rx) and you do not want to expose an IEnumerable you can create tour own “IEnumeratorAsync” that asynchronously fetches the next item. Again this is something I would advice against. First of all you are loosing the option to use…

0