A Fine Slice Of SQL Server
Jameson Marriott fixes a spacing issue:
I recently noticed that ggplot2 spaces date axes literally even when grouped by month. I’ve been using ggplot2 extensively for years and I don’t remember noticing before, so this is not really a big deal, but now that I know it bugs me a lot. Take a look below.
I don’t think I had noticed this before either, though now that Jameson has pointed it out, it certainly is annoying. H/T R-Bloggers.
Leave a CommentThomas Sobolik and Leopold Boudard talk model drift:
Regardless of how much effort teams put into developing, training, and evaluating ML models before they deploy, their functionality inevitably degrades over time due to several factors. Unlike with conventional applications, even subtle trends in the production environment a model operates in can radically alter its behavior. This is especially true of more advanced models that use deep learning and other non-deterministic techniques. It’s not enough to track the health and throughput of your deployed ML service alone. In order to maintain the accuracy and effectiveness of your model, you need to continuously evaluate its performance and identify regressions so that you can retrain, fine-tune, and redeploy at an optimal cadence.
In this post, we’ll discuss key metrics and strategies for monitoring the functional performance of your ML models in production […]
Click through for the article. There’s a Datadog pitch at the end, but the info is useful regardless of which tool you’re using for monitoring.
Leave a CommentNicky van Vroenhoven shares a public service announcement:
In case you missed the official blog post 2 months ago, I suggest you read my blog post 🙂
Or if you want you can refer to the official blog here: Announcing the retirement of legacy Power BI Apps (pre-audiences).
Already on March 6, 2023(!), Power BI apps with multiple audiences went Generally Available.
Read on for more information, with the note that these things will disappear soon—May 1, 2004 is the date of retirement.
Leave a CommentVlad Drumea doesn’t need no steenkin’ transaction log backups:
This brief post contains a script that can help switch a whole SQL Server instance, model and all user databases, to SIMPLE recovery.
The script is useful in case of dev/test/QA/UAT instances that have been left by accident to use the default FULL recovery model, yet do not have or need transaction log backups.
Read on for the script. It also shrinks the transaction log file after the switch-over.
Leave a CommentAfter a lengthy period in Public Preview it seems, the boffins at Microsoft have finally pushed Elastic Jobs for SQL Azure DB to general availability. Hooray!
But what are Elastic Jobs? And why would I want to use them in SQL Azure DB?
That’s one of the things you’ll learn in this post.
Leave a CommentPavel Borisov explains the importance of vacuuming your tables:
By default, all table data in Postgres are physically stored using the “heap” method. So every database is a set of 1Gb files (”segments”) and each file is logically split into 8Kb pages. Actual table rows are put into any page with enough free space.
When the row data is updated, a new version of a whole row is constructed and written (to any free space). The old one remains because, at the time of the update, the transaction is not completed and can be rolled back in the future. When the transaction is completed we’ll have two or several versions of the same row in the table. Cleaning old ones is by an asynchronous process called vacuum (and autovacuum).
Read on for more information about how this works and what you can (or should) do to help it along.
Leave a Comment