SQLServerCentral Editorial

Milk

Genome research into producing the best cows for milk has Steve Jones thinking about the implications for other industries. There could be new opportunities for data professionals.

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.

Blogs

T-SQL Tuesday #202: 100 Hours

By

It’s time for T-SQL Tuesday again and this is a great prompt to start...

Exploring DiskANN: Part 2: PQ, SSDs, caching and beam search

By

How I used AI for this postChatGPT to generate images based on info specifically...

T-SQL Tuesday #202: The Two Outages I Won't Ever Forget

By

My T-SQL Tuesday #202 entry for Marlon Ribunal's invitation on memorable SQL Server outages....

Read the latest Blogs

Forums

Performance Regression After Upgrading from SQL Server 2016 to 2022

By abdalah.mehdoini

Hello everyone, Last week we performed an upgrade of our SQL Server instance, moving...

Adding new column with DEFAULT

By Thomas Franz

Comments posted to this topic are about the item Adding new column with DEFAULT

How do I connect to a SQL Server database on my ISP?

By Doctor Who 2

I've got a web application for my side business. I've added a SQL Server...

Visit the forum

Question of the Day

Adding new column with DEFAULT

Which number will the COUNT() return after executing the following statements: 

DROP TABLE IF EXISTS #test;
CREATE TABLE #test (id INT)
INSERT INTO #test (id)
SELECT *
  FROM GENERATE_SERIES(1, 3) AS gs
;

ALTER TABLE #test ADD flag BIT CONSTRAINT DF_#test_flag DEFAULT 0;
go
UPDATE #test SET flag = 0 WHERE id = 1
UPDATE #test SET flag = 1 WHERE id = 2

INSERT INTO #test (id) VALUES (4)

SELECT COUNT(*)
  FROM #test AS t
 WHERE flag = 0
 

See possible answers