ArtistId int IDENTITY(1,1) NOT NULL PRIMARY KEY, We then define the first column. It is followed by the table name (in this case Artists), followed by the first of the parentheses that enclose the table definition. CREATE TABLE Artists ( This is the start of the CREATE TABLE statement. You don't need this line if you're already working in the correct database. There could be many databases on the server and we want to be sure that we're creating the tables on the correct database. It's only there to switch over to the Music database. Here's a more detailed 'line by line' description: USE Music This part isn't actually part of the CREATE TABLE statement. Each column's definition begins with its name, followed by its data type and any constraints to be applied to that column. This SQL statement creates a table called Artists with three columns, called ArtistId, ArtistName, and ActiveFrom. The script also adds a foreign key constraint, but we'll look at that later.įor now, let's analyze the first CREATE TABLE statement in our script: The script we just ran consists of three CREATE TABLE statements - each one creates a different table. Explanation of the CREATE TABLE Statement You can also expand the Columns node to reveal the list of columns and their data types, as well as any constraints that have been specified. Each table can be expanded to reveal its columns, as well any indexes, triggers, keys, etc. Here's the result in SQL Operations Studio/Azure Data Studio:Īny GUI tool will display the tables in pretty much the same way. The tables are called Artists, Genres, and Albums. That script adds three tables to the database. GenreId int IDENTITY(1,1) NOT NULL PRIMARY KEY,ĪlbumId int IDENTITY(1,1) NOT NULL PRIMARY KEY,ĬONSTRAINT FK_Albums_Artists FOREIGN KEY (ArtistId)

ArtistId int IDENTITY(1,1) NOT NULL PRIMARY KEY,

Sql server create table