Welcome to the Sioux Falls Developer's Group!

Initial Import for DbUp I’m looking into using DbUp for it’s migration approach to databases. I’ve found that the initial import process isn’t documented so I did some research. Organization I like his approach of having a Migrations folder and different folders for StoredProcs and Functions. This allows for code review of the changed StoredProcs and Functions which are replaced everytime. We can’t do this with Views as that would have a major re-indexing performance hit on the database.

Main Options for Database DevOps I’ve recently started a new contract that have goal to get their database structure into Git. This is laudable!👏 (you have your code in Git, right?!?) At Omnitech we have a long running Teams chat going on the difference between State and Migration based versioning of Databases (we are MS SQL centric thinkers). I’ve compiled the feedback and created 2 small demos for my own learning to share with you.

For a number of years, I was using Disqus to provide comments on my blog. However, I was increasingly unhappy with how bloated the solution was, how many additional entries I was having to put into my Content Security Policy, and unsure how comfortable I was with having a third party own comments to my own site. So last year, I removed comments from my site entirely. This worked fine, and I didn’t really think about it much, until somebody reached out to me via email recently, with what was essentially a comment on a blog post, and I realized that nobody else but me was going to benefit from it.

The Shared State Monster The Shared State Monster got me again. I had a .AddTransient class with a singleton/lazy loaded property called Updater. I was thinking that class got re-created each time so I added a lazy property similar to this public int UserId { get { return _queue?.UserId ?? 0; } } private Queue _queue; private async Task<Queue> GetQueue(int queueId) { if (_queue != null) return _queue; _queue = await _queueFacade.