Products sold or used in the manfacturing of sold products. Product inventory and manufacturing locations. Sales representative current information. Lookup table containing the languages in which some AdventureWorks data is stored.Ĭross-reference table mapping sales orders to sales reason codes. ![]() Individual products associated with a specific sales order. It identifies the heirarchical relationship between a parent product and its components. Items required to make bicycles and bicycle subassemblies. Also see the Person and Store tables.Ĭross-reference table mapping people to their credit card information in the CreditCard table. Lookup table containing standard ISO currencies.Ĭurrent customer information. Human beings involved with AdventureWorks: employees, customer contacts, and vendor contacts. One way hashed authentication information Lookup table containing the ISO standard codes for countries and regions.Ĭompanies from whom Adventure Works Cycles purchases parts or other goods.Ĭross-reference table mapping ISO currency codes to a country or region. Lookup table containing the types of business entity contacts. See PurchaseOrderHeader.Ĭross-reference table mapping stores, vendors, and employees to people Individual products associated with a specific purchase order. Source of the ID that connects vendors, customers, and employees with address and contact information.Ĭross-reference table mapping vendors with the products they supply.Ĭross-reference table mapping customers, vendors, and employees to their addresses. ![]() Types of addresses stored in the Address table. Street address information for customers, employees, and vendors. Résumés submitted to Human Resources by job applicants. Record of each purchase order, sales order, or work order transaction year to date. Manufacturing failure reasons lookup table. Lookup table containing the departments within the Adventure Works Cycles company.Ĭustomer reviews of products they have purchased.Įmployee information such as salary, department, and title. Data is inserted by stored procedure dbo.uspLogError when it is executed from inside the CATCH block of a TRY.CATCH construct.Ĭross-reference table mapping products and product photos. Data is captured by the database trigger ddlDatabaseTriggerLog.Īudit table tracking errors in the the AdventureWorks database that are caught by the CATCH block of a TRY.CATCH construct. Production.ProductModelProductDescriptionCultureĬross-reference table mapping product descriptions and the language the description is written in.Īudit table tracking all DDL changes made to the AdventureWorks database. ![]() (Last updated on Thu, Nov 26th, 2015 at 12:25 PM)Ĭurrent version number of the AdventureWorks 2012 sample database. The size of the tables can be scaled by running the INSERT code block multiple times to increase the size of the Sales.SalesOrderHeader table by roughly 225MB, and to increase the size of the Sales.SalesOrderDetailEnlarged table by roughly 400MB per execution after the index rebuilds are run.Ĭreate Enlarged AdventureWorks Tables.sql (8.Generated using SQL Data Dictionary demo version. These larger tables can be used to produce parallel execution plans, plans that have large execution memory grant requirements, plans that perform sort and hash spill operations through tempdb, and many other uses in SQL Server. The attached script has been tested against the AdventureWorks2008R2 and AdventureWorks2012 databases specifically, but as long as the table schema is the same it may be applied to any version of AdventureWorks. Below is a script that can enlarge these tables into tables named Sales.SalesOrderHeaderEnlarged and Sales.SalesOrderDetailEnlarged in the specific AdventureWorks database being targeted. The tables that I chose to enlarge for demonstration purposes were the Sales.SalesOrderHeader and Sales.SalesOrderDetail tables which can be used to demonstrate a number of different query plan and performance issues in SQL Server. The concept of creating a larger version of AdventureWorks is not new, Adam Machanic ( Blog| Twitter) blogged last year about enlarging specific tables for demonstrations, and at the same time I found that I also needed to create tables that were larger datasets for my own purposes. The AdventureWorks set of sample databases are commonly used for presentation demos and showing how to use SQL Server, but one of the biggest challenges in using these databases is their small size which is geared towards ease of distribution, more than demonstrating all of the functionality of SQL Server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |