Press "Enter" to skip to content

Day: July 7, 2025

Bioconductor in the Wake of ggplot2 4.0.0

Maria Doyle lays it out:

A major update to ggplot2 (version 4.0.0) is expected around mid-to-late July 2025. It brings a significant internal change, replacing most of the S3 backend with the newer S7 object system. While this improves long-term maintainability and extensibility, it may break Bioconductor packages that depend on ggplot2, especially those that customise how plots are built or styled. Packages that use ggplot2 for typical plotting tasks, such as creating plots with ggplot() and geom_*(), are unlikely to be affected.

Click through for notes, tips on what to do, and whether the code you’re using will break with ggplot2 4.0.0. H/T R-Bloggers.

Leave a Comment

Trying out Fabric Unified Admin Monitoring

Reitse Eskens tries out a tool for monitoring Microsoft Fabric installations:

Let me set the scene quickly for you. You’re working for an organisation where Fabric is in the process of being adopted or it’s already fully in use. Regardless of the number of capacities, workspaces, etc, you’re interested in what’s going on in your Fabric environment. You have questions like “Who is using the reports?”, “Who is changing settings in the Admin panel?” and “How is my capacity being used?”.

Read on for a single tool that can solve these sorts of questions.

Leave a Comment

Drop Shadows and Power BI

Elena Drakulevska has some thoughts on drop shadows:

I get why people add them. Shadows might feel like a design upgrade. A quick way to make your visuals pop or feel more “finished.”

But here’s the thing: just like rounded corners, drop shadows are easy to overdo—and they’re not actually helping. Not with clarity. Not with accessibility. Definitely not with UX.

Click through for Elena’s full thoughts. I’m generally against drop shadows. They draw visual attention without providing the report viewer any value. That’s chartjunk.

Leave a Comment

SQL Server Error Log Tips

Kevin Hill notes that the error log isn’t just for errors:

SQL Server’s Error Logs often get overlooked, until something breaks. But if you know how to use them, they can tell you what went wrong before you’re knee-deep in outage mode.

Whether you’re a sysadmin who inherited SQL or an MSP juggling multiple environments, understanding the ErrorLog is low effort, high return.

Let’s decode the basics.

Click through for examples of information you can find in the error log. Kevin mentions cycling the error log weekly. Back in my DBA days, I’d cycle them daily because I didn’t want the files to grow too large and become unwieldy. Some of this, of course, depends upon how hard people are pushing that box and how much you need to log.

Leave a Comment

Backup and Restoration via pgbackrest

Warda Bibi sets up a backup management system:

Recently, we worked with a client who was manually backing up their 800GB PostgreSQL database using pg_dump, which was growing rapidly and had backups stored on the same server as the database itself. This setup had several critical issues:

  • Single point of failure: If the server failed, both the database and its backups would be lost.
  • No point-in-time recovery: Accidental data deletion couldn’t be undone.
  • Performance bottlenecks: Backups consumed local storage, impacting database performance.

Read on to see how pgbackrest can address each of these concerns.

Leave a Comment

Using a File Cache in SSIS

Andy Brownsword makes those SSIS jobs run faster:

Last week we looked at using a cache to improve lookup performance. We saw how a cache improves performance by being able to reuse reference data repeatedly. That used a regular cache but it’s not the only option available to us.

In this post we’re going to look at the File Cache option which can achieve the same results – plus a little more.

My experience with file caches is that they’re a bit finicky but when you get them running, they can provide a significant speed-up to data enrichment tasks.

Leave a Comment