A Fine Slice Of SQL Server
Steven Sanderson checks the week:
When working with dates in R, you may need to extract the week number for any given date. This can be useful for doing time series analysis or visualizations by week.
In this post, I’ll demonstrate how to get the week number from dates in R using both base R and the lubridate package. I’ll provide simple examples so you can try it yourself.
Steven also makes a good point about ISO weeks (which are common in Europe) versus calendar weeks.
Comments closedSteve Jones shows ERROR_MESSAGE()’s extended family:
I was working with a customer that was doing some error handling in procs and helped them do some error tracking. As we were working through things, I realized that some of functions working with errors operated differently than I expected.
Read on to learn more about these error functions and the proper way to use them.
Comments closedSandeep Pawar builds out some data:
If you want to learn or demo Real Time Analytics in Microsoft Fabric, you will need a streaming data source. You can use the built-in samples to get started. But there are several data generators which you can use to create custom streaming sample datasets, Azure Stream Analytics data generator being one of them. You can see them here. In this blog, I will show how to set one up to use with Fabric Eventstream.
Read on for a step-by-step guide.
Comments closedChad Callihan disambiguates two terms:
You may hear or read about locks and latches and assume these terms are being used interchangeably. After all, if you search for synonyms for the word “lock”, you’ll find “latch” as a potential substitute:
In database terms, lock and latch are similar but have unique purposes of their own. It’s not as simple as “you say toMAYto, I say toMAHto.”
Click through for the difference and a few details on latches.
Comments closedI found a nasty bug in SQL Server and Azure SQL Managed Instance recently: sometimes an “online” index rebuild of a disk-based rowstore clustered index (basically a normal, everyday table) isn’t actually “online”. In fact, it’s very OFFLINE, and it blocks both read and write queries against the table for long periods.
If you manage to make it through a rebuild successfully, the problem goes away for future rebuilds of that clustered index – likely leaving you bruised and bewildered.
Click through for the details, including repo scripts and explanation of what should happen in this case.
Comments closedAndy Brownsword removes a blocker:
Blocking in SQL Server will reduce throughput. Excessive blocking can be cause bottlenecks on our environments so helping to mitigate it. Here we’re going back to basics to look at how it happens and how having effective indexes can reduce it.
The word “effective” is the critical one there.
Comments closed