Articles

SQLServerCentral Article

Estimating Your Space Needs

How many times have you had to estimate space for a new SQL Server database? How much time did you spend on it? Was it a thumb-in-the-wind guess or did you actually examine a schema and calculate some values. If you have asked someone to estimate the space their database will need, they probably guess more than compute, but now Andre Vigneau gives us an easy way we can teach those developers to put some thought into the process.

(1)

You rated this post out of 5. Change rating

2005-01-25

11,843 reads

SQLServerCentral Article

A Case Study in Performance Tuning

SQL Server does a wonderful job of tuning itself, selecting the optimum query plans and in general performing very well under a variety of conditions. That does not mean the a good DBA cannot add value by setting up the system and ensuring the optimizer receives the information that it needs. New author Gordon Pollokoff brings us a short case study from a project he as recently involved in where a new application required a bit of tuning.

(1)

You rated this post out of 5. Change rating

2005-01-24

12,549 reads

SQLServerCentral Article

Triggers in SQL Server 7.0 and 2000 - The Common Ground

This is a two part series on how triggers work in the two latest versions of MS SQL Server. Because there are some pretty significant additions in trigger functionality from 7.0 to 2000, we'll first need to look at what the two versions have in common. The second part to this series will look at the differences between the two MS SQL Server versions.

(5)

You rated this post out of 5. Change rating

2005-01-21 (first published: )

110,885 reads

SQLServerCentral Article

On the Trail of the ISO Week

Chris Hedgate, one of our regular SQL Server columnists, recently became intrigued by the way that SQL Server implements the week number. His concern was why SQL Server treats week 53 as week 1, which is not that way that ISO6801 sees it. Read about his investigation into the methods of implementing an algorithm to solve this problem.

(3)

You rated this post out of 5. Change rating

2005-01-20

11,664 reads

Technical Article

SQL Server 2005 Recursive Functions

SQL Server 2005 has added a new format for queries called a Common Table Expression or CTE. CTE’s are part of the SQL:1999 Specification and represent further compliance with this specification by SQL Server. This article will cover using one of the many capabilities of CTE’s, implementing recursive functions. A recursive function is a one that iteratively executes itself. Understanding how CTE’s implement recursive functions is the first step to understanding the full capabilities of CTE’s.

2005-01-19

1,858 reads

Blogs

Want to look at cloud reporting but not sure what the costs will be?

By

Have you been thinking about migrating your reporting to Microsoft Fabric or Snowflake but...

The Joyful Craftsmen and the Revolt BI join forces

By

The Joyful Craftsmen has become the new owner of Revolt BI. The merger creates...

Prime Day Recommendations

By

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

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