A Fine Slice Of SQL Server
Andrew Pruski changes some shortcuts:
At a recent conference I was asked how I executed code during my presentation.
Running code during a presentation should be as smooth as possible…so in VS Code I have a couple of custom key mappings set up and I thought I’d write a quick blog detailing what they are and what they do.
These are some clever keyboard shortcuts that I may just yoink.
Comments closedIn this video, I show off a not-so-well-known capability in Visual Studio Code and Azure Data Studio: creating profiles.
Profiles are very useful in Visual Studio Code, though probably less useful for Azure Data Studio. I think the primary benefit to that would be handling things like zoom levels and menu layouts when you switch from a laptop on the go to something plugged into a larger monitor.
Comments closedDavid Fowler shares an update:
Full documentation on the Undercover Catalogue can be found HERE
We’ve spotted a bug in the Databases module where an unprintable ASCII character was being inserted at the beginning of the file paths. This has caused a few problems when generating reports on that field.
Click through to grab a copy of the toolbox.
Comments closedMika Sutinen builds some data:
I recently had a project where I needed quickly to generate some realistic looking test data to PostgreSQL database. While I often like to go for ready-made solutions, this felt like a good opportunity to stretch my coding muscles and develop it myself. Moreover, this seemed like a fun puzzle to solve, and I could probably use the same solution later on elsewhere.
Click through for a description of the generator, as well as a link to Mika’s GitHub repo. Taking a quick peek at it, it does appear that you could probably use this for other data platforms like SQL Server with very limited modification.
Comments closedVlad Drumea covers a pair of errors you might run into with mssql-tools version 18:
In this post I cover the 0A000086 and “command not found” errors that you might encounter with the new version of SQL Server command-line tools, namely sqlcmd and bcp, for Linux.
While the latest version of SQL Server command-line tools, based on Microsoft ODBC 18, brings improvements, it also brings some gotchas that can break your automations.
Read on to learn more about each.
Comments closedGrant Fritchey explains a UI oddity:
Let me be extremely clear up front, this is not my original work. I saw this post on DBA.StackExchange.com and I wanted to share and promote it. Nice work FevziKartal.
The rest of this post is just me replicating work already done by others. I just want to see it in action.
Read on for the example and what happens when you don’t have any events in the live data explorer.
Comments closedI have wrapped up another series:
In this video, I discuss some of the things you should consider as you transition a Streamlit application from development to production. We will cover four methods of bringing a Streamlit app to production and some thoughts on performance optimization.
This one doesn’t have much in the way of demos, but I do spend a lot of time at the virtual whiteboard, so it’s got that going for it.
Comments closedGulcin Yildirim Jelinek explains the debate around whether pg_dump is a backup tool or not:
Recently, while writing about the vulnerability affecting
pg_dump, the topic of decommissioningpg_dumpcame up on Twitter. Unlike the nostalgic feelings many had for Pluto, there was less reluctance to seepg_dumpreclassified. In fact, some people were eager to retire it as a backup utility, and I even got a bit of pushback for still referring topg_dumpas oneI was talking to my colleague Simona the other day, and she mentioned that everybody in Postgres circles says, “pg_dump is not a backup tool,” but perhaps it’s not always explained well why it is not.
Read on for that explanation.
Comments closedJeff Iannucci announces a new tool:
Whether you are backing up your SQL Server databases with Ola Hallengren’s scripts, Maintenance Plans, or some third-party software, your backups are your lifeline for recovering your data in case of a disaster.
So…are your databases recoverable? Do you know WHERE your most recent backups were written? Do you know WHEN they were written? Did you verify the backups for recoverability? Have you backed up any encryption certificates associated with your backups?
And if you think know the answers to these questions…are you sure? And can you confirm your Recovery Point Objective (RPO)?
Read on to learn more about the procedure and grab a copy from the GitHub repo.
Comments closedSemab Tariq uses a Postgres extension:
The file_fdw (Foreign Data Wrapper) is a PostgreSQL extension that lets you access data stored in flat files, like CSV files, as if they were regular tables in your PostgreSQL database. This is useful for integrating external data sources without needing to import the data directly into your database.
file_fdw is a contrib module, meaning it’s an additional feature included with PostgreSQL but not part of its core functionality. Contrib modules provide extra capabilities and enhancements beyond the core database system.
At first, I was going to write that the mechanism looks a lot like PolyBase in SQL Server. But in actuality, it’s more like a hybrid of PolyBase and OPENROWSET, as there’s no definition of external data sources or file formats, but there is the creation of an external (“foreign”) table.