Database Builds

External Article

Deploying Data and Schema Together with SQL Compare or SQL Change Automation

  • Article

You want to use SQL Compare or SQL Change Automation (SCA) to create or update a database, and at the same time ensure that its data is as you expect. You want to avoid running any additional PowerShell scripting every time you do it, and you want to keep everything in source control, including the data. You just want to keep everything simple. Phil Factor demonstrates how it's done, by generating MERGE scripts from a stored procedure.

2019-12-13

SQLServerCentral Editorial

Over-thinking Database Build Scripts

  • Editorial

With SQL Server we tend to build databases, when necessary, from one or more build scripts. If making changes to existing versions of the database, we then script the required changes. Usually, a synchronization tool will create a script that can be tweaked to work; although occasionally it will require something more complicated, as when […]

1 (1)

You rated this post out of 5. Change rating

2019-06-29

335 reads

Technical Article

Static Data and Database Builds

  • DatabaseWeekly

Often, we can't build a fully functional SQL Server database just from the DDL code. Most databases also require what is often referred to as 'static', or 'reference' data, which will include such things as error messages, names of geographical locations, currency names or tax information. What's the best way to handle such data?

You rated this post out of 5. Change rating

2019-05-31

External Article

Better Ways to Build a Database

  • Article

The purpose of a database build is simple: prove that what you have in version control can successfully create a working database, and yet many teams struggle with unreliable and untested database build processes that slow down deployments and prevent the delivery of new functionality. Grant Fritchey explains how to achieve an automated and reliable database build that is only as complex as the database system it needs to create.

2016-03-22

5,439 reads

Blogs

Cloud Data Driven User Group 2025 – Slides & Scripts

By

The slidedeck and the SQL scripts for the session Indexing for Dummies can be...

Leading Through Change: Guiding Teams in Times of Uncertainty

By

Change is not a disruption in technology; it is the rhythm. New frameworks appear,...

The Mystery of the Locked-Up Database -Scooby Dooing Episode 6

By

No Scooby-Doo story is complete without footprints leading to a hidden passage. In SQL...

Read the latest Blogs

Forums

Don't Forget About Financial Skills

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Don't Forget About Financial Skills

Building a Simple SQL/AI Environment

By Tony Savoie

Comments posted to this topic are about the item Building a Simple SQL/AI Environment

Checking Identities

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Checking Identities

Visit the forum

Question of the Day

Checking Identities

The DBCC CHECKIDENT command is used when working with identity values. I have a table with 10 rows in it that looks like this:

TravelLogID CityID  StartDate   EndDate
1           1       2025-01-11  2025-01-16
2           2       2025-01-11  2025-01-16
3           3       2025-01-11  2025-01-16
4           4       2025-01-11  2025-01-16
5           5       2025-01-11  2025-01-16
6           6       2025-01-11  2025-01-16
7           7       2025-01-11  2025-01-16
8           8       2025-01-11  2025-01-16
9           9       2025-01-11  2025-01-16
10          10      2025-01-11  2025-01-16
The docs for DBCC CHECKIDENT say this if I run with only the table parameter: "If the current identity value for a table is less than the maximum identity value stored in the identity column, it is reset using the maximum value in the identity column. " I run this code:
DELETE dbo.TravelLog WHERE TravelLogID >= 9
GO
DBCC CHECKIDENT(TravelLog, RESEED)
GO
INSERT dbo.TravelLog
(
    CityID,
    StartDate,
    EndDate
)
VALUES
(4, '2025-09-14', '2025-09-17')
GO
What is the identity value for the new row inserted by the insert statement above?

See possible answers