A Fine Slice Of SQL Server
Mirai Solutions has some tips on cleaning up Shiny apps:
How to apply the spring cleaning principles and advanced programming to your Shiny App.
1. Deep breeze and allocate some time
Do not avoid spring cleaning simply because you don’t know where to start from. Prioritize some time for the task and get inspired by our following points.
Click through for advice on tools and processes to make this code easier to understand. H/T R-Bloggers
Comments closedReiss McSporran explains an issue in Azure Synapse Analytics dedicated SQL pools:
Oh dear. Shuffle. On the surface, shuffle is not necessarily a bad thing and may even be expected, but not in this scenario. So what is shuffle and why can it be bad?
Shuffle occurs when a part of a distributed table is moved to a different node during query execution. To do this a hash value is computed using the join columns, the node is then found that has that hash value and the row is then sent to that node for processing. If the tables you’re joining on have different hash distributions, you’d expect this to happen, (hence why it’s not always a bad thing!), but in this case I’ve used the same value to hash both of my tables, so what’s gone wrong?
Click through to see what’s gone wrong.
Comments closedThomas Rushton attempts to preserve extended property history:
Custom extended properties can be a useful tool when creating a self-documenting database. However, in an environment where tables are routinely dropped and recreated by software/systems not within your control, it may be desirable to have these stored so they can be repopulated when the table is recreated.
Read on to learn about the results of each test. Also read on for a use of the term “faff” in its appropriate context.
Comments closedErik Darling tests an assertion:
After my smash hit double diamond post about index tuning, I got a question questioning my assertion that compressed indexes are also compressed in the buffer pool.
Well, this should be quick. A quick question. Eighty hours later.
Click through for the test.
Comments closedIf you’re using the new Parquet connector in Power BI there’s a chance you will run into the following error:
Parameter.Error: Parquet.Document cannot be used with streamed binary values.
Details:
[Binary]This isn’t a bug or anything that can be fixed, so it’s important to understand why it occurs and what you can do about it.
Click through for the explanation.
Comments closedChad Callihan has a story in three acts:
Once upon a time, I was having a relaxing morning…until I received an e-mail alert about an Error Number 825 on a database. The error stated:
‘D:\sql_dat\DatabaseName.mdf_MSSQL_DBCC47’ at offset 0x00000004b9e000 succeeded after failing 1 time(s) with error: 121(The semaphore timeout period has expired.). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
That’s not how you want your day to go. Fortunately, the database was not one that needed to be online 24/7 so I felt I could relax a little bit while starting to investigate. At this point, the issue seemed to be with one database.
Click through to see if everyone lived happily ever after.
Comments closed