Technical Article

Utilize SQL Server Storage Effectively

With the increased use of databases and the need to have more and more data online, database storage is an area DBAs need to manage effectively. If you plan your database and data management correctly you can build and manage a cost effective, high performing SQL Server solution. If not, you risk potential storage issues as well as performance degradation. This session will cover best practices and options focused on helping you manage your SQL Server storage. We will dive into the tools you can use to manage database storage, some of the latest trends, database design implications, data archiving and alternatives such as compression, BLOB data storage, filtered indexes and more. We’ll also introduce a tool that allows you to reduce the storage footprint of your live SQL Server databases.

Join us for this free event and learn how to utilize your SQL Server storage effectively.

External Article

Using DELETE CASCADE Option for Foreign Keys

Referential integrity is a very important thing to consider when designing a database. In my years as a DBA I've seen database designs that sit on both ends of the spectrum, none at all and cases where every table is linked to multiple tables. While the later certainly can be a little more difficult to work with it ensures the integrity of your data stays intact. The other end provides much more flexibility when it comes to updating and deleting data from your database, whether it's being done through the application or directly on the backend, but has the issue of possible orphan records if things are not done properly. This tip will look at the DELETE CASCADE option when creating foreign key constraints and how it helps keep the referential integrity of your database intact.

SQLServerCentral Editorial

A Data Hub

The idea of a data hub in your company is interesting to Steve Jones. He talks about this concept, and how it might help you increase data quality, and perhaps get closed to a single view of the truth.

External Article

Removing the SQL Server Management Data Warehouse

SQL Server 2008 introduced a new feature, Management Data Warehouse (MDW), which allows users to collect metrics on their servers over time to aid in performance troubleshooting. A lot of people try this feature out, because it is easy to set up, and then find that it is not so easy to remove. In fact, removing MDW is not supported; in SQL Server 2012, though, a new system stored procedure was added to make this process easier. The problem is that this stored procedure (as well as several of the workarounds I've seen published) can leave several objects behind.

SQLServerCentral Editorial

Wiggle Room

Consultants sometimes don't live up to their hype. To what extent should we expect them to know exactly what they're doing? This editorial was originally published on Nov 9, 2007. It is being republished as Steve is on vacation.

Blogs

Automatic Index Compaction

By

Index maintenance has always meant nightly jobs and a window you have to defend....

The Goldilocks problem – Materialized Views

By

I’m sure you’ve all heard the tale of Goldilocks and the Three Bears, but...

Monday Monitor Tips: Virtual Machine Usage and Cost

By

One of the things I’ve been requesting for a number of years is cost...

Read the latest Blogs

Forums

SQL Art, Part 4: Happy 4th of July — A British DBA's Guide to Celebrating a War We Don't Talk About

By Terry Jago

Comments posted to this topic are about the item SQL Art, Part 4: Happy...

SQL Server Still Wins

By Steve Jones - SSC Editor

Comments posted to this topic are about the item SQL Server Still Wins

DBCC CHECKDB Limits I

By Steve Jones - SSC Editor

Comments posted to this topic are about the item DBCC CHECKDB Limits I

Visit the forum

Question of the Day

Getting the Average

I have this data in the dbo.Commission table in a SQL Server 2022 database.

salesperson commission
Brian       12
Brian       16
Andy        7
Andy        14
Andy        21
Steve       20
Steve       NULL
All the data is a varchar, and I decide to run this query to get the totals for each salesperson.
SELECT SalesPerson
     , AVG(TRY_PARSE(Commission AS int)) AS TotalCommission
 FROM commission
 GROUP BY SalesPerson
GO
What average commission is calculated for Steve?

See possible answers