Slowly Changing Dimension in SQL Server 2005 – Part 2
This article is Part 2 in the series which explores the options available in SQL Server 2005 for Slowly Changing Dimensions
This article is Part 2 in the series which explores the options available in SQL Server 2005 for Slowly Changing Dimensions
Do you deal with data or information? Do you know the difference and are you transforming one into the other. Steve Jones comments on the state of many companies' data.
Continuing on with his series on building a game in SQL Server, Steve Fibich talks about some more of the tables and the data they contain.
When a team is developing a database application, it is a mistake to believe that deployment is a simple task. It isn’t. It has to be planned, and scripted. Alexander Karmanov describes many of the problems you’re likely to meet, and provides an example solution that aims to save the DBA from the nightmare complexity of an unplanned deployment.
Does your IT organization bring value to your company? Steve Jones takes a look at some of the ways you can do this.
Does your IT organization bring value to your company? Steve Jones takes a look at some of the ways you can do this.
Does your IT organization bring value to your company? Steve Jones takes a look at some of the ways you can do this.
How you use dynamic SQL, when you should - and when you should not.
Steve Jones looks back at a week of news on data center infrastructure, the EF war, and SQL Server 2008 news.
By Steve Jones
It’s Prime Day. A few of my recommendations, since I want to do some...
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
If you’ve been watching AI roll through the data community and thinking, “this seems...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Comments posted to this topic are about the item Concurrency and Baseline Control: Level...
Comments posted to this topic are about the item Spending Time in the Office
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' ) GOSee possible answers