A Fine Slice Of SQL Server
Reitse Eskens shares some tips:
When discussing options, possibilities, and solutions with customers, the Real-Time stack began to emerge. We received questions on ingestion that couldn’t be simply answered using batch processing. The best part is that we can start learning new technology!
The following blog will outline the best things I learned working with real-time analytics.
Click through for those items.
Comments closedAndy Brownsword does a bit of logging:
When creating SQL Agent jobs to execute SSIS packages we can choose the level of logging to be captured. Different settings are more beneficial under the right circumstances so it’s important to understand the differences to make the right decision.
These settings control the internal logging done by SSIS. This is out of the box and freely available, so why not use it effectively.
The real trick is that if you swallow all of the exceptions and errors, everybody will just assume your code is working perfectly and boom, problem solved. Or you could read Andy’s post and get actual information. Whatever works for you, I suppose.
Comments closedBrent Ozar flips everything around:
99.9% of you are never gonna need this.
But let’s say you need to run queries with leading (not trailing) wildcards, like this search for all the different national versions of the Encabulator, each of which has different prefixes depending on which government it’s being sold to:
This is indeed a pretty uncommon scenario. I’m pretty sure I’ve only ever needed to do this once. Well, twice, but in one case I couldn’t actually use the REVERSE() function because the column was itself an awful non-deterministic function and this solution wouldn’t work.
Louis Davidson has popped and therefore cannot stop:
The goal of this week’s entry is specifically to show how to see how multiple matches can be viewed using SQL Server’s RegEx, specifically to make the examples clearer (especially in the upcoming entries).
There are several functions that you can use where multiple matches are used as part of the output:
Click through for that list and several examples of relevant functions in action.
Comments closed“SQL Server is slow.”
We’ve all heard it. But that doesn’t always mean SQL Server is the problem. And “slow” means nothing without context and ability to verify.
More often than you’d think, poor performance is rooted in the one thing most sysadmins don’t touch until it’s on fire: the disk subsystem.
There are other potential causes as well, such as choosing the wrong RAID array format (like, say, RAID 6 for your extremely busy log files) and limited bandwidth to a SAN. Note that Kevin’s listings for what constitutes acceptable disk focuses primarily on on-premises solutions, maybe biased toward direct attached storage versus a SAN. For cloud databases, spikes of 30-60 seconds are perfectly fine, of course.
Comments closedReza Rad pulls an older post out of the archives:
The latest update of Power BI Desktop (October 2016) has many features. Two of these features are grouping and binning. These features used to create groups of items and visualize them better in the report. Previously you could do that by Power Query or DAX calculated columns, now it is all possible simply through the graphical user interface of report editor. In this post I’ll show you how to create banding (binning) and grouping simply with these features. If you like to learn more about Power BI; read the Power BI online book from Rookie to Rock Star.
How long has Curated SQL been around? Long enough that I covered this the first time. But hey, it’s still valid information.
2 CommentsKoen Verbeeck doesn’t believe in import-export businesses:
I want to try some of the new features in SQL Server 2025. I’ve installed the CTP 2.0 preview on a virtual machine, and now I need some sample databases to play around with. Can I use the AdventureWorks database like in previous versions of SQL Server?
The answer is yes, and read on for the process.
Comments closedDrew Furgiuele has a follow-up:
A few months ago, I wrote a blog post about using Azure API Management with Databricks Model Serving endpoints. It struck a chord with a lot of people using Databricks on Azure specifically, because more and more people and organizations are trying their damndest to wrangle all the APIs they use and/or deploy themselves. Recently, I got an email from someone who read it and asked a really good question:
Click through for that question, as well as Drew’s answer.
Comments closedCharles Webb lays out some updates:
Welcome to What’s New in Fabric Warehouse, where we’ll spotlight our work improving quality, delivering major performance enhancements, boosting developer productivity, and our continuous investments in security. Whether you’re migrating from Synapse, optimizing your workloads, writing SQL in VS Code, or exploring new APIs, this roundup has something for every data professional. With quality and experience at the forefront, we’ve summarized and highlighted key improvements we think you’ll love, organized into three sections:
- What’s New
- Docs Updates
- Roadmap Updates
Read on for that update.
Comments closedBen Richardson builds a dictionary:
Have you ever opened a Power BI report and felt overwhelmed by all the columns, measures, and tables?
It can feel like a guessing game trying to figure out what each field represents.
A well-built data dictionary eliminates that confusion, giving you clarity and confidence when exploring reports.
This is one of those bits of documentation that can be incredibly useful but people rarely keep it up to date.
Comments closed