eliminate the optional column list and allow SQL Server to assume we're providing something for every column : Insert « Insert Delete Update « SQL Server / T-SQL Tutorial






3>
4> CREATE TABLE stores(
5>    stor_id        char(4)           NOT NULL,
6>    stor_name      varchar(40)           NULL,
7>    stor_address   varchar(40)           NULL,
8>    city           varchar(20)           NULL,
9>    state          char(2)               NULL,
10>    zip            char(5)               NULL
11> )
12> GO
1>
2>
3>    INSERT INTO stores
4>    VALUES ('TEST', 'Test Store', '1234 Anywhere Street', 'Here', 'NY', '00319')
5> GO

(1 rows affected)
1>
2>    INSERT INTO stores (stor_id, stor_name, city, state, zip)
3>    VALUES ('TST2', 'Test Store', 'Here', 'NY', '00319')
4> GO

(1 rows affected)
1>
2>    SELECT * FROM stores WHERE stor_id = 'TST2'
3> GO
stor_id stor_name                                stor_address                             city                 state zip
------- ---------------------------------------- ---------------------------------------- -------------------- ----- -----
TST2    Test Store                               NULL                                     Here                 NY    00319

(1 rows affected)
1>
2>
3> drop table stores;
4> GO








2.1.Insert
2.1.1.The syntax of the INSERT statement for inserting a single row
2.1.2.INSERT Statement
2.1.3.Inserting Data for a Subset of Table Columns
2.1.4.The insertion of values into some (but not all) of a table's columns usually requires the explicit specification of the corresponding columns.
2.1.5.The order of column names in the VALUE clause of the INSERT statement can be different from the original order of those columns.
2.1.6.An INSERT statement that adds the new row using a column list
2.1.7.INSERT statement with a column list
2.1.8.INSERT...DEFAULT VALUES
2.1.9.Use declared variables in insert statement
2.1.10.An INSERT statement that fails because a related row doesn't exist
2.1.11.eliminate the optional column list and allow SQL Server to assume we're providing something for every column
2.1.12.How to add rows to a table based on the output of a stored procedure