A Fine Slice Of SQL Server
Thomas Williams illuminates us on the caching process:
Caching in R Markdown is a valuable step to get your app, report or visualisation more production-ready. There are one or two potential issues to watch out for, especially when deploying a cache-enabled R Markdown file to a Shiny server – in this post I’ll go over some of these “gotchas”, and how you could address each one.
Click through for those three gotchas.
Comments closedSomething cool has just been announced for Azure SQL DB: the ability to call a limited number of REST APIs direct from TSQL. The announcement is here:
Read on for sample code, including a way to execute DAX queries from T-SQL.
Comments closedKoen Verbeeck sets up a great weekend project:
SQL Server 2022 has been released! In this blog post, I’ll walk you through how you can install the latest version of SQL Server on your machine. I’ll be using the developer edition of SQL Server 2022, which can be downloaded here.
Click through for guidance on setting up Developer edition.
Comments closedAaron Bertrand follows up on a prior post:
As soon as you realize your growth rates are higher than expected, you need to plan to buy or allocate more disk space. There is no way around this—more data means more disk. You can delay the inevitable for a little bit with better compression, but this is not a long-term fix, and it can impact query performance in different ways (trading CPU for I/O).
Once more disk is in place, you can plan your growth better.
Click through for some guidance on how to plan that growth.
Comments closedTom Zika picked a popular topic:
Thank you everyone for participating! There is a total of 15 submissions and thanks to them, I’ve widened my perspective.
The order of the posts is chosen at random.
Read on for the full list of respondents.
Comments closedDavid Fowler troubleshoots an issue:
Checking the logs on the secondary, it was littered with ‘Database Mirroring login attempt failed with error: ‘Connection handshake failed. An OS call failed: (80090302) 0x80090302(The function requested is not supported).’ messages. The primary server wasn’t able to authenticate with the secondary, but why? Everything looked ok as far as I could see.
Click through for the fruits of David’s labor.
Comments closedWilliam Assaf mentions a welcome change to SQL Server 2022:
Starting with SQL Server 2022, transaction log file growth events up to 64 MB in size can benefit from instant file initialization (IFI). As usual, the transaction log is otherwise unable to benefit from instant file initialization.
This should be a big performance improvement if your transaction log files unexpectedly grow. Of course, you should try to avoid autogrowth events altogether.
The prior default of 10% autogrowth has led to so many problems over the years. I’d like new database files (MDF and NDF) to have a similar default as well.
Comments closedI have a SQL Server Agent job in a disabled status. The disabled status is applied to the SQL Agent Job and the associated schedule. The problem is I’m logged on as a full administrator onto the Windows Server – and as BUILTIN\Administrator is defined on the SQL Server , but am able to manually override the SQL Agent Job.
Is there a way to Disable the SQL Agent Job where I’m not able to manually override the job?
Click through for the answer.
Comments closed