Additional Articles


External Article

Building a Data Warehouse Blueprint for Success

One of the most integral components and critical success factors of any enterprise data warehousing initiative is the Solutions Architecture document, a high-level conceptual model of a data warehousing solution. Learn why this collaborative effort that addresses the needs of all major stakeholders, including both the business units and Information Technology (IT), is essential.

2010-07-09

2,224 reads

External Article

Developing Modifications that Survive Concurrency

You can create a database under the assumption that SQL looks after all the problems of concurrency. It will probably work fine under test conditions: then, in the production environment, it starts losing data in subtle ways that defy repetition. It is every Database Developer's nightmare. In an excerpt from his acclaimed book, Alex Kuznetsov explains why it happens, and how you can avoid such problems.

2010-07-09

3,657 reads

Blogs

Prime Day Recommendations

By

It’s Prime Day. A few of my recommendations, since I want to do some...

Fabric for Operational Reporting & SQL Endpoint Trap

By

With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...

Crawl, Walk, Run with Agentic Development of Power BI Assets

By

If you’ve been watching AI roll through the data community and thinking, “this seems...

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...

Concurrency and Baseline Control: Level 5 of the Stairway to Reliable Database Deployments

By Massimo Preitano

Comments posted to this topic are about the item Concurrency and Baseline Control: Level...

Spending Time in the Office

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Spending Time in the Office

Visit the forum

Question of the Day

Multiple Values Inserted

I have this code on SQL Server 2022. What happens when it runs all at once?

DROP TABLE IF EXISTS dbo.Commission
GO
CREATE TABLE dbo.Commission
(id INT NOT NULL IDENTITY(1,1) CONSTRAINT CommissionPK PRIMARY KEY
, salesperson VARCHAR(20)
, commission VARCHAR(20)
)
GO
INSERT dbo.Commission
( salesperson, commission)
VALUES
( 'Brian', 12 ),
( 'Brian', 'None' )
GO
 

See possible answers