This is just a short article (more of a blog-ette than a full blog) about some things we as developers need to consider when sending queries to Microsoftโs SQL Server. While some of this information may also be true for other flavors of database servers, these things are known to be true for SQL Server.
Every long-term project will outlive at least some of the technologies it was originally built with. For example, a project I have been involved with recently ran into this situation. The app is hosted on Heroku, and over the years, the available MongoDB add-ons have changed and dwindled until now, there is only one.
Several migrations between MongoDB add-ons have already happened because of shutdowns. So, it was decided that rather than migrating to the last one still in existence, the project would switch to using PostgreSQL, which is supported directly by the Heroku team.
In between projects here at Keyhole, Iโve been tasked with applying a relational database access and mapping framework in the Go language.
In this post, I go step by step to create a Postgres relational database, then perform CRUD operations against it in the Go language.
I wonโt get into the specifics of configuring Go in this blog, but you can check it out yourself here – https://golang.org/. Additionally, Keyholeโs very own David Pitt wrote an excellent primer on the subject here – https://keyholesoftware.com/2019/09/26/go-on-the-fly/.
I am working on a project that leverages both Azure Functions as well as Cosmos DB. In trying to get both of these components wired together, I found that there are very few examples that work with the most recent versions of these components. I also saw examples that could work at a small scale, but donโt show industry-standard best practices, and would lead to performance issues if deployed in an environment with any meaningful traffic.
To that end, I put together this blog post showing how to set up an Azure Functions project in .NET Core 2.2 to integrate with Cosmos DBโs SQL API using its native tooling.
When working with SQL Server, you might run across a situation where it is just not running fast enough. While there could be many reasons for this, there are tools that can help you track down just what is going on behind the scenes. SQL Server Management Studioโs SQL Server Profiler or just (Profiler) is a tool that can be used to monitor queries run on your database.
In this blog post Iโll give a brief demonstration of the SQL Server Profiler tool. Iโll show you how to keep an eye on all the queries that are being run against your database, as well as how to use a filter to narrow your search to just slower-running queries…