Many of the code examples in Importing and Exporting Bulk Data require a special-purpose test table named myTeam. Before you can run the examples, you must create the myTeam table in the HumanResources schema of the AdventureWorks2012 database.
AdventureWorks2012 is one of the sample databases in SQL Server 2017.
The myTeam table is contains the following columns.
|EmployeeID||smallint||Not null||Primary key for the rows. Employee ID of a member of my team.|
|Name||nvarchar(50)||Not null||Name of a member of my team.|
|Title||nvarchar(50)||Nullable||Title the employee performs on my team.|
|Background||nvarchar(50)||Not null||Date and time the row was last updated. (Default)|
To create HumanResources.myTeam
Use the following Transact-SQL statements:
--Create HumanResources.MyTeam: USE AdventureWorks; GO CREATE TABLE HumanResources.myTeam (EmployeeID smallint NOT NULL, Name nvarchar(50) NOT NULL, Title nvarchar(50) NULL, Background nvarchar(50) NOT NULL DEFAULT '' ); GO
To populate HumanResources.myTeam
INSERTstatements to populate the table with two rows:
USE AdventureWorks; GO INSERT INTO HumanResources.myTeam(EmployeeID,Name,Title,Background) VALUES(77,'Mia Doppleganger','Administrative Assistant','Microsoft Office'); GO INSERT INTO HumanResources.myTeam(EmployeeID,Name,Title,Background) VALUES(49,'Hirum Mollicat','I.T. Specialist','Report Writing and Data Mining'); GO
These statements skip the fourth column,
Background. This has a default value. Skipping this column causes this
INSERTstatement to leave this column blank.