A Fine Slice Of SQL Server
Etienne Lopes tracks a notification event:
Did you ever need to automate some actions immediately after a database restore?
There are several ways to accomplish this, in this article I will demonstrate one of them, using a simple event called: “AUDIT_BACKUP_RESTORE_EVENT“
Read on to learn more about how to use this event.
Comments closedSteve Stedman digs into a class of waits:
What is shown in the image above is that historic wait monitoring feature from Database Health Monitor, and it has been monitoring for a few days and the query with the most waits is xp_delete_file. When we drill down on the details we can see that the wait type is PREEMPTIVE_OS_GETPROCADDRESS.
Read on to see what might cause this and how you can fix it.
Comments closedJeet Kainth shows how to configure a retention strategy in Azure Blob Storage:
This blog is a follow up to a previous blog I wrote about backing up Azure Analysis Services cubes in Azure, that blog can be found here. This blog shows how to implement a retention policy using PowerShell in Azure Runbooks to remove the backups after a set number of days. To create a new Runbook in the Azure portal, go to the relevant Automation account in the relevant resource group and then select Runbooks from the left hand pane. Note you will need to add the Az.Storage module to the automation account to be able to use some of the commands listed in this blog.
Click through for the process, including Powershell code to perform the task.
Comments closedChad Baldwin has a container in search of a database:
Yesterday, I was watching a Pluralsight course which provided a database
.bakfile to follow along with the examples. I generally like to use Docker when working with SQL Server locally…but as a somewhat novice user, I have found it to be a bit of a pain if you need to deal with restoring or attaching a database.When I run into these scenarios, I usually spin up an AWS EC2 instance, install SQL server, and work with it that way. There’s probably a simpler way to do it using RDS or Azure, but I’m not familiar with those just yet. The other option is if I have a Linux machine at hand, I will use that with Docker and mapped volumes work great.
I do happen to have a Linux machine ready to use…but I was determined to figure out how to get this working on Windows.
Bonus points for using RESTORE DATABASE syntax. Every SQL Server user should know how to back up and restore a database using only T-SQL. That’s a skill which will definitely pay dividends.
Gilbert Quevauvilliers wants you to back that thing up:
Continuing with my series of using Power BI Premium Per User (PPU), today I am going to show you how to back up your PPU database.
As far as I am aware all the options below will work for Power BI Premium as well.
To me this is critical when my dataset size grows. Especially when it takes multiple days to process all the data into the required partitions.
Not only is having a backup best practice, if something must go wrong with a deployment (let’s say I wipe out the partitions by mistake) it will be quick and easy to restore from a backup.
Read the whole thing.
Comments closedLee Markum has a starting point for DBAs in a new role:
You’ve just been hired into a DBA role at a new company, or you’ve been given the DBA keys at your current company. Maybe you’re a SysAdmin and your boss has informed you that you are now supposed to manage the SQL Servers as well as everything else on your plate. In any of these situations, you may have some confidence in your skills, but especially in the case of being a new hire, you have absolutely no true idea of what you’re walking into.
In these scenarios, where do you start? Start with these four areas.
Click through for the four areas. I completely agree with Lee on these for DBAs, including the order.
Comments closedDave Ruijter backs that thing up:
Out of the box, Azure Data Lake Storage Gen2 provides redundant storage. Therefore, the data in your Data Lake(house) is resilient to transient hardware failures within a datacenter through automated replicas. This ensures durability and high availability. In this blog post, I provide a backup strategy on how to further protect your data from accidental deletions, data corruption, or any other data failures. This strategy works for Data Lake as well as Data Lakehouse implementations. It uses native Azure services, no additional tools, software, or licenses are required.
Read on for a detailed strategy.
Comments closedKevin Hill answers ja question about whether full backups break log shipping:
Keep on doing your full backups.
Make sure that any databases you Log Ship are NOT also doing log backups in your SQL Maintenance Plans, Ola Jobs, etc.
Click through for a video walkthrough on the topic.
Comments closedSo in the last blog we confirmed that we could move to SQL MI via some analysis, this is now time to actually do a backup and restore via URLs to move data.
Quite simply you need to BACKUP to URL (Azure Storage container) and the setup requirement is that you need to create a SQL credential that holds the SAS token – this is what allows authentication to the container to take place.
Click through for the process.
Comments closedArun Sirpal wants to restore a database:
Now that we have a Managed Instance built, the next question is how do we get data across? I will break this up into separate posts but the lesson for this blog post is ANALYSIS FIRST!
Click through for the analysis.
Comments closed