Attention: This article was published over 6 years ago, and the information provided may be aged or outdated. While some topics are evergreen, technology moves fast, so please keep that in mind as you read the post.I was recently tasked with summarizing the data of a several-million-row table, and the task proved to be a bit grueling at first. Eventually, …
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/.
TL;DR
– Spoiler alert! Graph databases are a great option for storing complex and highly connected data.
– In this post, I compare the benefits and risks of graph databases ArangoDB, Neo4j, and OrientDB for a client project.
– Due to the combination of performance and cost, I chose ArangoDB for my client’s needs.
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…