A Fine Slice Of SQL Server
Kevin Hill takes us through an issue:
This is a stand-alone bare metal server located at a hosting facility with some local storage as well as NAS storage. SQL Server 2016 Standard Edition, 8 cores, 128GB RAM. The primary database is nearing 1TB and is has multiple filegroups (Active, Archive, Indexes, etc.). This database and apps that touch it ARE the company.
Read on for Kevin’s process, which was a solid bit of troubleshooting.
Comments closedGilbert Quevauvilliers wants some long-term storage:
Following on in my series, in this blog post I am going to demonstrate how to store Log Analytics Queries in Blob Storage.
This allows me to be able to store the Power BI Queries externally from Log Analytics and to have an easy way to get the data into my Fabric Lake house in later steps. To do this I am going to use a Logic App in Azure.
In this series I am going to show you all the steps I did to have the successful outcome I had with my client.
Read on to see what Gilbert used for the task.
Comments closedAndrew Pruski saves the day, or at least the data:
In my last couple of blog posts (here and here) I talked about how to get SQL Server running in Docker Swarm. But there is one big (and show-stopping) issue that I have not covered. How do we persist data for SQL Server in Docker Swarm?
Docker Swarm, like Kubernetes, has no native method to persist data across nodes…so we need another option and one of the options available to us is Portworx.
So how can we use Portworx to persist SQL Server databases in the event of a node failure in Docker Swarm?
Read on to find out how.
Comments closedA lot of my customers have a business requirement that –
- once a document is written in storage account, nobody shall be able to modify or delete it, including the administrators
AND / OR- audit data can be written only once, and nobody shall be able to alter them.
These kind of business requirements are called WORM (Write Once, Read Many) and are common for various industries such as ISVs, financial or healthcare. Have you run into these mission-critical requirements? If yes, then immutable storage would be the solution.
Read on to see how this works, using retention policies. But ash Khushbu notes, if you set an absurd retention policy (up to 400 years), you can’t change the data while that policy is active.
Comments closedThe Big Data in Real World team runs rm -rf:
In this post we will see how to recursively delete files/objects, folders and bucket from S3.
I made the joke before reading the article, and it turns out that I was pretty close to spot-on. Read on to see how you can do this via the AWS CLI.
Comments closedDaniel Hutmacher uses a temp disk for a temp database:
Almost all Azure virtual machine sizes come with a temporary disk. The temporary disk is a locally attached SSD drive that comes with a couple of desirable features if you’re installing a SQL Server on your VM:
- Because it is locally attached, it has lower latency than regular disks.
- IO and storage are not billed like regular storage.
As the name implies, the temporary disk is not persistent, meaning that it will be wiped if you shut down your VM or if the VM moves to another VM host (as part of maintenance or troubleshooting). For that reason, we never want to put anything on the temporary disk that we need to keep.
I’d say this was a lot more popular several years ago, back when spinning disk was the default for Azure storage. There can still be benefits from doing this, though if you’re using Premium storage with high IOPS, the biggest remaining benefit is around latency.
Comments closedAndrew Pruski has a video for us:
A while back I posted a blog on how to recover data with crash consistent snapshots.
Snapshots are pretty handy in certain situations so I thought I’d show you them in action!
Want to watch the video? Click through for the video. Just make note that there’s no audio on it, so don’t turn your speakers way up in the hopes that you can hear Andrew.
Comments closedKevin Chant diagnoses an issue:
In this post I want to cover common Azure Synapse Link for SQL storage permission issues. Since I helped a fellow MVP out with this recently.
To be more precise, I want to show how you can fix one of the most common issues I tend to encounter with Azure Synapse Link for SQL. Which is access to the Data Lake Storage Gen2 account.
I have encountered issues like this a few times now. For example, when I was performing my file tests for Azure Synapse Link for SQL Server 2022.
Click through to learn more about a couple of common issues, their causes, and resolutions.
Comments closedJose Manuel Jurado Diaz has a few scripts for us:
Today, we got a new question how much is the size used by a columnstore index table at storage level and memory usage.
TSQL to obtain the total number of rows, size per schema, table and index.
Using the view sys.column_store_row_groups (Transact-SQL) – SQL Server | Microsoft Learn we could see the total number of rows and space usage at storage level.
Click through for that script, as well as a few more to learn how much space and memory that columnstore index is taking.
Comments closedAnthony Nocentino tags all the things:
A tag is a key/value pair that can be attached to an object in FlashArray, like a volume or a snapshot. Using tags enables you to attach additional metadata to objects for classification, sorting, and searching. For example, you can assign a tag to a collection of volumes and then come along later and retrieve a listing of volumes that match a particular key or value. You can use tags to add application context to resources inside FlashArray. Specifically, in the examples in this blog post, I want to tag volumes with the names SQL Server Instances.
Click through to see what you’d need to do, assuming you have an appropriate device running Purity 6.0 or later.
Comments closed