Problems displaying this newsletter? View online.
SQL Server Central
Featured Contents
The Voice of the DBA
 

Get Your Chores Done

I grew up in a pretty rural environment, in the southern US, in what's considered the Old West (Jesse James, reportedly, had a hideout a few miles from my current home, the Daltons, Belle Star, I can keep going, all came through this part of Oklahoma). Here, we call our daily tasks, like taking out the trash, chores. Like many people, I don't particularly care for my chores. One of many that I've added over the years is the chore of going to work out. I know people love it. In my youth, before everything hurt, I did too. Now... it's a chore. However, like a chore, I make sure and take care of it, because, like most chores, it's necessary.

Present me with a query tuning problem and I'm happy. Tell me I've got to set up backups, well, that's a chore. However, like making sure I get my exercise done, you need to ensure that you've got backups on your databases, even though it's a chore. You should also do the added chore of practicing restoring those backups. No fun, not at all. Necessary though. I'd also suggest you toss in the chore of setting up a way to get some of your backups stored offsite, in a secure location. Yeah, I know. Work. Unrewarding work. No fun work. A chore. I have more. I'd also recommend you ensure that you've got good security on your systems. Isolate that security too. Admin to the database shouldn't be admin to the network and vice versa. Yeah, I hear you. Another chore. No fun work. No happy results like when a query runs faster. Make sure you also limit who has admin rights to your clusters (SQL Server instances, whatever). More chores. Hate me now?

Well, if you were with Knights of Old Transport, I'll bet you wish you had done some, or all of these chores. A weak password, followed by poor security principals and a lack of secure, offsite storage for backups, resulted in a hack that put the company out of business. Unemployment is WAY less fun than doing chores.

I get it. Chores are no fun. Who the heck enjoys taking out the trash? Yet, chores must be accomplished, and accomplished well, or, there'll be hell to pay. If I don't keep working out (and keep my weight down), I'm already in line for a pacemaker. So, chore or not, I get that work out completed. Chore or not, set up backups, test your backups through restores, practice restoring, get an offsite storage of some kind that's secure, and isolated, and for the love all that is good in the world, make damned sure you set up security appropriately.

Get your chores done!

Grant Fritchey

Join the debate, and respond to today's editorial on the forums

 
 Featured Contents
SQLServerCentral Article

Model Context Protocol (MCP): A Developer’s Guide to Long-Context LLM Integration

ndulam from SQLServerCentral

Large Language Models (LLMs) like Anthropic’s Cl...

SQLServerCentral Article

How to safely and surgically restore filegroups

Chandan Shukla from SQLServerCentral

Most DBAs are familiar with full and differential ...

Pro SQL Server 2022 Wait Statistics: A Practical Guide to Analyzing Performance in SQL Server and Azure SQL Database

Site Owners from SQLServerCentral

Use this practical guide to analyze and troubleshoot SQL Server performance using wait statistics. You'll learn to identify precisely why your queries are running slowly. And you'll know how to measure the amount of time consumed by each bottleneck so you can focus attention on making the largest improvements first. This edition is updated to cover analysis of wait statistics current with SQL Server 2022. Whether you are new to wait statistics, or already familiar with them, this book provides a deeper understanding on how wait statistics are generated and what they mean for your SQL Server instance’s performance. 

 

 

 

 

 Yesterday's Question of the Day (by dbakevlar)

Capacity Planning for an Existing SQL Server Workload?

You're tasked with planning capacity for a new SQL Server database workload. Which of the following is the most accurate way to determine how much CPU, memory, and I/O throughput your workload requires?  What single or multiple tools would you use to answer the questions around resource needs?

Answer: Use Windows Performance Monitor (PerfMon), Query Store, and sys.dm_os_wait_stats to analyze historical CPU, memory, and I/O usage trends under peak load

Explanation: B. Use Windows Performance Monitor (PerfMon), Query Store, and sys.dm_os_wait_stats to analyze historical CPU, memory, and I/O usage trends under peak load Capacity planning for SQL Server requires a combination of tools to assess real-world usage. PerfMon provides system-level metrics (CPU %, Page Life Expectancy, Disk Queue Length), Query Store captures execution patterns and query-level performance over time, and sys.dm_os_wait_stats helps identify where resource bottlenecks (CPU, memory, I/O) occur. These metrics give a realistic view of what hardware the workload requires, but remember, you need to collect it for both normal and peak workload conditions if you're doing a cloud migration to identify what will be the real needs and make sure it's cost effective. For on-premise, the answer is "B".

Discuss this question and answer on the forums

 

 

 

Database Pros Who Need Your Help

Here's a few of the new posts today on the forums. To see more, visit the forums.


Editorials
Why Podcasts Matter for the Technical Professional - Comments posted to this topic are about the item Why Podcasts Matter for the Technical Professional
Transactional DDL in SQL Server: In Oracle, It Does Not Compute - Comments posted to this topic are about the item Transactional DDL in SQL Server: In Oracle, It Does Not Compute
Article Discussions by Author
How a Legacy Logic Choked SQL Server in a 30-Year-Old Factory - Comments posted to this topic are about the item How a Legacy Logic Choked SQL Server in a 30-Year-Old Factory, which is is not currently available on the site.
Capacity Planning for an Existing SQL Server Workload? - Comments posted to this topic are about the item Capacity Planning for an Existing SQL Server Workload?
Connecting to PostgreSQL with Node.js - Comments posted to this topic are about the item Connecting to PostgreSQL with Node.js
Taming Resource Hogs: Using SQL Server Resource Governor to Restrict User Group Consumption - Comments posted to this topic are about the item Taming Resource Hogs: Using SQL Server Resource Governor to Restrict User Group Consumption
Monitor SQL Server using Zabbix - Comments posted to this topic are about the item Monitor SQL Server using Zabbix
Database Architecture Considerations for Implementing Content Moderation Services - Comments posted to this topic are about the item Database Architecture Considerations for Implementing Content Moderation Services
Database Architecture Considerations for Implementing Content Moderation Services - Comments posted to this topic are about the item Database Architecture Considerations for Implementing Content Moderation Services
TCP Provider Errors in SQL Server - Comments posted to this topic are about the item TCP Provider Errors in SQL Server
Migrate from Linux to Windows with Availability Groups - Comments posted to this topic are about the item Migrate from Linux to Windows with Availability Groups
We Gave Memory-Optimized Tables a Hash Lookup — Then Tried Pattern Matching Instead - Comments posted to this topic are about the item We Gave Memory-Optimized Tables a Hash Lookup — Then Tried Pattern Matching Instead
Always On AG Latency for Read-Only Workload After Failover? - Comments posted to this topic are about the item Always On AG Latency for Read-Only Workload After Failover?
SQL Server 2022 - Development
Archiving data older than 5 years - Hi We have databases with data stored for over 20 years, this is required by law. We though want to move data to a Archive database where is can be accessed at any time, at times directly using a view linking the 2 databases and at other times manually having to select the data using […]
Database growth - Hi all I am currently using the following script to store database growth at clients. There are 2 issues though. One is that it is not taking into account free space on the database, so if there is as an example 100GB free space we do not see any growth until the 100GB is used […]
 

 

RSS FeedTwitter

This email has been sent to {email}. To be removed from this list, please click here. If you have any problems leaving the list, please contact the webmaster@sqlservercentral.com. This newsletter was sent to you because you signed up at SQLServerCentral.com.
©2019 Redgate Software Ltd, Newnham House, Cambridge Business Park, Cambridge, CB4 0WZ, United Kingdom. All rights reserved.
webmaster@sqlservercentral.com

 

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -