CS363: Structured Query Language for Data Management 1. CS363: Structured Query Language (SQL) for Data Management. Team Echo Group Project - Final

Transcription

1 CS363: Structured Query Language for Data Management 1 CS363: Structured Query Language (SQL) for Data Management Team Echo Group Project - Final Trina VanderLouw Other Team Members: Darrell Moore, Kanaan Pitts, Curtis Rice Professor Sabahudin Tricic Colorado Technical University Online April 16, 2012 Highlights: Group Project, SQL, Statements/Queries, Users, Roles, Permissions Programs Used: MySQL, Access, SQL Server, Word, Power Point Instructor Feedback: Thank you for participating this week. This assignment was geared to see how well you understand the decision making process and its implementation through various database decisions that are made while programming. By giving examples of how they work, you showcased your knowledge of how these constructs operate and how team members pick the set up. Keep working hard! Sabahudin Tricic Feedback on Group: Team E, great job on this project, even though only two members were truly active. I was very impressed by the amount of communication, and the effort that was put into the organization of your project. The active members of this team gave his or her best, and the results show that--your final project is of highest quality and would be well accepted in the workplace. It is very accessibile and clear--i especially liked the contents page in terms of your organization. Thank you for including me in your s--great team communication between the active members (Darrell and Trina). Final Grade: A

2 CS363: Structured Query Language for Data Management 2 TABLE OF CONTENTS INTRODUCTION/ABTRACT... 3 SCREEN SHOT OF A ENTITY RELATIONSHIP DIAGRAM (ERD)... 3 DATABASE SCRIPT FOR TABLE CREATION... 4 DCL STATEMENTS FOR LOGIN, USER, ROLES, AND PRIVILEGES (SECTION 1)... 9 REPORT REQUEST QUERIES (SECTION 2) INDEXES AND SCRIPTS (SECTION 3) STORED PROCEDURE (SECTION 4) CONCLUSION REFERENCES... 19

3 CS363: Structured Query Language for Data Management 3 INTRODUCTION/ABTRACT COMPLETED BY: Darrell Moore Canine Caper's Inc (CCI) has accepted our firms solicited proposal. Within that proposal our firm prescribed a solution that incorporated a Relational Database deployed over a Wide Area Network (WAN). This document is to serve as the proposal for the CCI database design. As such, this document includes the CCI database ERD, the scripts necessary to build the CCI database, the scripts necessary to build CCI's users, roles, logins, and privileges, example report queries, functional indexes and scripts, and necessary stored procedures (CS363, 2012). SCREEN SHOT OF A ENTITY RELATIONSHIP DIAGRAM (ERD) Here is a screen shot of the proposed CCI database ERD: Figure 1.1

4 CS363: Structured Query Language for Data Management 4 DATABASE SCRIPT FOR TABLE CREATION Script 1 Categories Table: USE [CCI] /****** Object: Table [dbo].[categories] Script Date: 04/11/ :26:32 ******/ SET ANSI_NULLS ON SET QUOTED_IDENTIFIER ON SET ANSI_PADDING ON CREATE TABLE [dbo].[categories]( [CategoryID] [int] IDENTITY(1,1) NOT NULL, [CatName] [varchar](50) NOT NULL, [CatDescription] [text] NOT NULL, CONSTRAINT [PK_Categories] PRIMARY KEY CLUSTERED ( [CategoryID] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] ) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY] SET ANSI_PADDING OFF Script 2 Customers Table: USE [CCI] /****** Object: Table [dbo].[customers] Script Date: 04/11/ :33:39 ******/ SET ANSI_NULLS ON SET QUOTED_IDENTIFIER ON SET ANSI_PADDING ON CREATE TABLE [dbo].[customers]( [CustomerID] [int] IDENTITY(1,1) NOT NULL, [CusCompanyName] [varchar](50) NOT NULL, [CusContactLastName] [varchar](50) NOT NULL, [CusContactFirstName] [varchar](50) NOT NULL, [CusCompanyAddress] [varchar](200) NOT NULL, [CusCompanyCity] [varchar](50) NOT NULL, [CusCompanyState] [varchar](50) NOT NULL, [CusCompanyPostalCode] [varchar](50) NOT NULL, [CusCompanyCountry] [varchar](50) NOT NULL, [CusCompanyPhoneNumber] [varchar](50) NOT NULL, [CusContact Address] [varchar](150) NOT NULL, CONSTRAINT [PK_Customers] PRIMARY KEY CLUSTERED ( [CustomerID] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] ) ON [PRIMARY] SET ANSI_PADDING OFF

5 CS363: Structured Query Language for Data Management 5 Script 3 Employees Table: USE [CCI] /****** Object: Table [dbo].[employees] Script Date: 04/11/ :35:05 ******/ SET ANSI_NULLS ON SET QUOTED_IDENTIFIER ON SET ANSI_PADDING ON CREATE TABLE [dbo].[employees]( [EmployeeID] [int] IDENTITY(1,1) NOT NULL, [EmpLastName] [varchar](50) NOT NULL, [EmpFirstName] [varchar](50) NOT NULL, [EmpTitle] [varchar](50) NOT NULL, [EmpHireDate] [date] NOT NULL, [EmpAddress] [varchar](50) NOT NULL, [EmpCity] [varchar](50) NOT NULL, [EmpState] [varchar](50) NOT NULL, [EmpPostalCode] [varchar](50) NOT NULL, [EmpCountry] [varchar](50) NOT NULL, [EmpHomePhone] [varchar](50) NOT NULL, [EmpCellPhone] [varchar](50) NULL, [Emp ] [varchar](50) NOT NULL, CONSTRAINT [PK_Employees] PRIMARY KEY CLUSTERED ( [EmployeeID] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] ) ON [PRIMARY] SET ANSI_PADDING OFF Script 4 Inventory Table: USE [CCI] /****** Object: Table [dbo].[inventory] Script Date: 04/11/ :40:51 ******/ SET ANSI_NULLS ON SET QUOTED_IDENTIFIER ON CREATE TABLE [dbo].[inventory]( [InventoryID] [int] IDENTITY(1,1) NOT NULL, [InvProductID] [int] NOT NULL, [InvCurrentInStock] [int] NOT NULL, [InvMaximumLevel] [int] NOT NULL, [InvMinimumLevel] [int] NOT NULL, [InvDiscontinued] [bit] NOT NULL, CONSTRAINT [PK_Inventory] PRIMARY KEY CLUSTERED ( [InventoryID] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] ) ON [PRIMARY]

6 CS363: Structured Query Language for Data Management 6 ALTER TABLE [dbo].[inventory] WITH CHECK ADD CONSTRAINT [FK_Inventory_Products] FOREIGN KEY([InvProductID]) REFERENCES [dbo].[products] ([ProductID]) ALTER TABLE [dbo].[inventory] CHECK CONSTRAINT [FK_Inventory_Products] Script 5 Orders Table: USE [CCI] /****** Object: Table [dbo].[orders] Script Date: 04/11/ :42:24 ******/ SET ANSI_NULLS ON SET QUOTED_IDENTIFIER ON CREATE TABLE [dbo].[orders]( [OrderID] [int] IDENTITY(1,1) NOT NULL, [OrdCustomerID] [int] NOT NULL, [OrdEmployeeID] [int] NOT NULL, [OrdProductID] [int] NOT NULL, [OrdQuantity] [int] NOT NULL, [OrdShipperID] [int] NOT NULL ) ON [PRIMARY] ALTER TABLE [dbo].[orders] WITH CHECK ADD CONSTRAINT [FK_Orders_Customers] FOREIGN KEY([OrdCustomerID]) REFERENCES [dbo].[customers] ([CustomerID]) ALTER TABLE [dbo].[orders] CHECK CONSTRAINT [FK_Orders_Customers] ALTER TABLE [dbo].[orders] WITH CHECK ADD CONSTRAINT [FK_Orders_Employees] FOREIGN KEY([OrdEmployeeID]) REFERENCES [dbo].[employees] ([EmployeeID]) ALTER TABLE [dbo].[orders] CHECK CONSTRAINT [FK_Orders_Employees] ALTER TABLE [dbo].[orders] WITH CHECK ADD CONSTRAINT [FK_Orders_Products] FOREIGN KEY([OrdProductID]) REFERENCES [dbo].[products] ([ProductID]) ALTER TABLE [dbo].[orders] CHECK CONSTRAINT [FK_Orders_Products] ALTER TABLE [dbo].[orders] WITH CHECK ADD CONSTRAINT [FK_Orders_Shippers] FOREIGN KEY([OrdShipperID]) REFERENCES [dbo].[shippers] ([ShipperID]) ALTER TABLE [dbo].[orders] CHECK CONSTRAINT [FK_Orders_Shippers] Script 6 Products Table: USE [CCI] /****** Object: Table [dbo].[products] Script Date: 04/11/ :43:37 ******/ SET ANSI_NULLS ON SET QUOTED_IDENTIFIER ON

7 CS363: Structured Query Language for Data Management 7 SET ANSI_PADDING ON CREATE TABLE [dbo].[products]( [ProductID] [int] NOT NULL, [CatID] [int] NOT NULL, [ProSKUNumber] [varchar](10) NOT NULL, [ProName] [varchar](50) NOT NULL, [ProDescription] [text] NOT NULL, [ProCurrentQuantity] [int] NOT NULL, [ProStatus] [varchar](8) NOT NULL, [ProDateIntroduced] [date] NOT NULL, [ProCurrentSellingPrice] [money] NOT NULL, [ProMinimumQuantity] [int] NOT NULL, [ProMaximumQuantity] [int] NOT NULL, CONSTRAINT [PK_Products] PRIMARY KEY CLUSTERED ( [ProductID] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] ) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY] SET ANSI_PADDING OFF ALTER TABLE [dbo].[products] WITH CHECK ADD CONSTRAINT [FK_Products_Categories] FOREIGN KEY([CatID]) REFERENCES [dbo].[categories] ([CategoryID]) ALTER TABLE [dbo].[products] CHECK CONSTRAINT [FK_Products_Categories] ALTER TABLE [dbo].[products] WITH CHECK ADD CONSTRAINT [FK_Products_Products] FOREIGN KEY([ProductID]) REFERENCES [dbo].[products] ([ProductID]) ALTER TABLE [dbo].[products] CHECK CONSTRAINT [FK_Products_Products] Script 7 Shippers Table: USE [CCI] /****** Object: Table [dbo].[shippers] Script Date: 04/11/ :45:17 ******/ SET ANSI_NULLS ON SET QUOTED_IDENTIFIER ON SET ANSI_PADDING ON CREATE TABLE [dbo].[shippers]( [ShipperID] [int] IDENTITY(1,1) NOT NULL, [ShipperName] [varchar](50) NOT NULL, [ShipContactFirstName] [varchar](50) NOT NULL, [ShipContactLastName] [varchar](50) NOT NULL, [ShipperAddress] [varchar](50) NOT NULL, [ShipCity] [varchar](50) NOT NULL, [ShipState] [varchar](50) NOT NULL, [ShipPostalCode] [varchar](50) NOT NULL, [ShipCountry] [varchar](50) NOT NULL, [ShipPhoneNumber] [varchar](50) NOT NULL,

8 CS363: Structured Query Language for Data Management 8 [ShipContact Address] [varchar](50) NOT NULL, CONSTRAINT [PK_Shippers] PRIMARY KEY CLUSTERED ( [ShipperID] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] ) ON [PRIMARY] SET ANSI_PADDING OFF Script 8 Vendors Table: USE [CCI] /****** Object: Table [dbo].[vendors] Script Date: 04/11/ :46:26 ******/ SET ANSI_NULLS ON SET QUOTED_IDENTIFIER ON SET ANSI_PADDING ON CREATE TABLE [dbo].[vendors]( [VendorID] [int] IDENTITY(1,1) NOT NULL, [VendorCompanyName] [varchar](50) NOT NULL, [VenPreferred] [varchar](3) NOT NULL, [VenContactName] [varchar](50) NOT NULL, [VenAddress] [varchar](300) NOT NULL, [VenPhoneNumber] [varchar](12) NOT NULL, [VenFaxNumber] [varchar](12) NULL, [Ven Address] [varchar](150) NOT NULL, [VenStatus] [varchar](8) NOT NULL, CONSTRAINT [PK_Vendors] PRIMARY KEY CLUSTERED ( [VendorID] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] ) ON [PRIMARY] SET ANSI_PADDING OFF Script 9 Vendors_Products Table: USE [CCI] /****** Object: Table [dbo].[vendors_products] Script Date: 04/11/ :48:15 ******/ SET ANSI_NULLS ON SET QUOTED_IDENTIFIER ON CREATE TABLE [dbo].[vendors_products]( [LineItem] [int] IDENTITY(1,1) NOT NULL, [VenID] [int] NOT NULL, [ProID] [int] NOT NULL, CONSTRAINT [PK_Vendors_Products] PRIMARY KEY CLUSTERED ( [LineItem] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]

9 CS363: Structured Query Language for Data Management 9 ) ON [PRIMARY] ALTER TABLE [dbo].[vendors_products] WITH CHECK ADD CONSTRAINT [FK_Vendors_Products_Products] FOREIGN KEY([ProID]) REFERENCES [dbo].[products] ([ProductID]) ALTER TABLE [dbo].[vendors_products] CHECK CONSTRAINT [FK_Vendors_Products_Products] ALTER TABLE [dbo].[vendors_products] WITH CHECK ADD CONSTRAINT [FK_Vendors_Products_Vendors] FOREIGN KEY([VenID]) REFERENCES [dbo].[vendors] ([VendorID]) ALTER TABLE [dbo].[vendors_products] CHECK CONSTRAINT [FK_Vendors_Products_Vendors] DCL STATEMENTS FOR LOGIN, USER, ROLES, AND PRIVILEGES (SECTION 1) COMPLETED BY: Darrell Moore Using your team's database, add the following: Section 1 Criteria: 1. DCL statements to create the login, user, role and assign the specified permissions for just the Clerk outlined in P2 DB. Don t forget to map the login to the user and assign the role to the user you create. Hint--use these steps: a. CREATE LOGIN to create the MySQL login b. CREATE USER to create the user, map the login to this user c. CREATE ROLE to create the role d. GRANT, DENY, REVOKE to assign permissions to that role e. assign role to user created in step b In order to meet the objective of this section Team Echo had to first create a login for the MS SQL Server. This login was named Clerk_1 with a password of password. Team Echo used the below script to create the aforementioned login. Script 1: CREATE LOGIN Clerk_1 WITH PASSWORD = 'password' To see the creation of this login Team Echo expanded the Security tab under the object viewer. This is a server level login. After creating this login Team Echo then created a user and assigned that user to the newly created login. To accomplish this Team Echo executed the following script. Script 2: USE CCI CREATE USER Clerk_1 FOR LOGIN Clerk_1

10 CS363: Structured Query Language for Data Management 10 This created a user by the name of Clerk_1 and assigned that user to the Clerk_1 login. From this point Team Echo then created a role to assign to the Clerk_1 user. To accomplish this Team Echo executed the following script. Script 3: USE CCI CREATE ROLE Clerks The above script created the role Clerks but that role was not assigned any users. To remedy this Team Echo executed the below stored procedure for adding a role member. Script 4: EXEC sp_addrolemember 'Clerks', Clerk_1 At this point Team Echo has so far created a login, a user, and a role. Now Team Echo must add permissions to the Clerk role as prescribed in the CS363 Phase 2 Discussion Board. If you recall that discussion board required that Clerks be granted SELECT privileges on the Inventory and the Vendor table. All other permissions are to be disallowed. Luckily this made the solution easier as newly created roles are automatically disallowed all privileges until you explicitly allow them. So all that was needed to accomplish the next step, was to perform a GRANT statement for selecting everything from the Vendor and Inventory tables. To accomplish this Team Echo executed the script below. Script 5: USE CCI GRANT SELECT ON OBJECT:: dbo.vendors TO Clerks Following the above command Team Echo performed the next command as listed below. Script 6: USE CCI GRANT SELECT ON OBJECT:: dbo.inventory TO Clerks For the purpose of continuity and cleanliness within the database Team Echo also added a Supervisor login, user, role, and privledges according to the criteria spelled out within Phase 2 Discussion Board. In order to build the Supervisor's login, user, role, and priveliges Team Echo had to accomplish the below scripts. The following scripts are the same as previously mentioned with alterations for the supervisor naming scheme and priveleges. Script 1: CREATE LOGIN Supervisor_1 WITH PASSWORD = 'password' Script 2: CREATE USER Supervisor_1 FOR LOGIN Supervisor_1 Script 3: USE CCI CREATE ROLE Supervisor

11 CS363: Structured Query Language for Data Management 11 Script 4: EXEC sp_addrolemember 'Supervisor', Supervisor_1 Script 5: USE CCI GRANT SELECT ON OBJECT:: dbo.vendors TO Supervisor Script 6: USE CCI GRANT SELECT ON OBJECT:: dbo.inventory TO Supervisor Script 7: USE CCI GRANT DELETE ON OBJECT:: dbo.inventory TO Supervisor Script 8: USE CCI GRANT INSERT ON OBJECT:: dbo.inventory TO Supervisor Script 9: USE CCI GRANT UPDATE ON OBJECT:: dbo.inventory TO Supervisor To test what Team Echo has accomplished, Team Echo connected to another server instance by clicking the connect button above the object viewer. From here Team Echo logged in as Client_1. The new connection only permits the team to view the Vendor and Inventory tables. The team cannot edit data within those tables however we can perform all necessary select statements. Following this the team then logged in as Supervisor_1. Logged in as Supervisor_1 we can view data in both the Vendor and Inventory tables. We can also add, edit, and delete information from the Inventory table but not the Vendor table. All of these parameters are within the prescribed construct of CS363 Phase 2 Discussion Board and CS363 Phase 4 Group Project. REPORT REQUEST QUERIES (SECTION 2) COMPLETED BY: Curtis Rice Section 2 Criteria: For this section of the CCI database design proposal our firm is illustrating the power of the constructed database. To best accomplish this, our firm has developed two specific queries that satisfy two different report requests (CS363, 2012). Report 1: Using the CCI database we generated a query to retrieve all rows of active inventory where the current on hand quantity is less than the prescribed minimum level. Knowing which products where within the threshold criteria of a reorder we then performed an aggregate function to between the current in stock quantity and the maximum allowable quantity to calculate the quantity of the reorder. In addition to this we named the field within the result set as "ReorderQuantity". Another step taken within this query was to include the Vendor information for the items that require a reorder purchase. This report query required the use of a LEFT OUTER JOIN to pull data from the Vendors table. You can see the scripted query below: Script 1:

12 CS363: Structured Query Language for Data Management 12 USE CCI SELECT Inventory.InvProductID, SUM (dbo.inventory.invmaximumlevel - dbo.inventory.invcurrentinstock)as ReorderQuantity, VendorCompanyName, VenAddress, VenPhoneNumber, VenContactName FROM Inventory LEFT OUTER JOIN Vendors ON dbo.inventory.invvendorid = dbo.vendors.vendorid WHERE InvCurrentInStock < InvMinimumLevel and InvDiscontinued = 0 GROUP BY Inventory.InvProductID,VendorCompanyName, VenAddress, VenPhoneNumber, VenContactName Report 2: The second report developed to demonstrate the power of this database had several variables to consider. In an effort to clarify what we accomplished Team Echo will enumerate those variables as follows. 1. The report must generate a number of vendors 2. Those vendors counted must not be preferred vendors 2. The vendor must also be a supplier of Category 2 products 3. The products must be active 4. The products must have been introduced on or after the year 2007 You can see the generated query script below: USE CCI SELECT COUNT(DISTINCT dbo.vendors.vendorid)as NumberOfNotPreferredCatID2VendorsOfActiveProductsIntroducedAfter2007 FROM dbo.vendors, dbo.inventory WHERE dbo.vendors.vendorid = dbo.inventory.invvendorid and dbo.vendors.venpreferred = 'Yes' and dbo.inventory.invcatid = 2 and dbo.inventory.invdiscontinued!= 'True' and dbo.inventory.invdateintroduced > = '2007' COMPLETED BY: Kanaan Pitts INDEXES AND SCRIPTS (SECTION 3) Section 3 Criteria: Within this section of the database design proposal our firm is illustrating the purpose and potential of indexes. As such we have provided a list of suggested indexes and the rationale behind those choices. It is our hope that we will illustrate the power that indexes can delivery when properly applied VARCHAR(MAX),

13 CS363: Structured Query Language for Data Management BIT -- used solely for putting information into the result table IF EXISTS (SELECT * FROM tempdb.dbo.sysobjects WHERE id = object_id(n'[tempdb].[dbo].[#indexsql]')) DROP TABLE [dbo].[#indexsql] CREATE TABLE #IndexSQL ( TableName VARCHAR(128) NOT NULL,IndexName VARCHAR(128) NOT NULL,IsClustered BIT NOT NULL,IsPrimaryKey BIT NOT NULL,IndexCreateSQL VARCHAR(max) NOT NULL ) IF EXISTS (SELECT * FROM tempdb.dbo.sysobjects WHERE id = object_id(n'[tempdb].[dbo].[#indexlisting]')) DROP TABLE [dbo].[#indexlisting] CREATE TABLE #IndexListing ( [IndexListingID] INT IDENTITY(1,1) PRIMARY KEY CLUSTERED, [TableName] SYSNAME COLLATE SQL_Latin1_General_CP1_CI_AS NULL, [ObjectID] INT NOT NULL, [IndexName] SYSNAME COLLATE SQL_Latin1_General_CP1_CI_AS NULL, [IndexID] INT NOT NULL, [IsPrimaryKey] TINYINT NOT NULL, [FillFactor] INT, [FilterDefinition] NVARCHAR(MAX) NULL ) IF EXISTS (SELECT * FROM tempdb.dbo.sysobjects WHERE id = object_id(n'[tempdb].[dbo].[#columnlisting]')) DROP TABLE [dbo].[#columnlisting] CREATE TABLE #ColumnListing ( [ColumnListingID] INT IDENTITY(1,1) PRIMARY KEY CLUSTERED, [ColumnIDInTable] INT NOT NULL, [Name] SYSNAME COLLATE SQL_Latin1_General_CP1_CI_AS NULL, [ColumnIDInIndex] INT NOT NULL, [IsIncludedColumn] BIT NULL ) INSERT INTO #IndexListing( [TableName], [ObjectID], [IndexName], [IndexID], [IsPrimaryKey], [FILLFACTOR], [FilterDefinition] ) SELECT OBJECT_NAME(si.object_id), si.object_id, si.name, si.index_id, si.is_primary_key, si.fill_factor, si.filter_definition FROM sys.indexes si LEFT OUTER JOIN information_schema.table_constraints tc ON si.name = tc.constraint_name AND OBJECT_NAME(si.object_id) = tc.table_name WHERE OBJECTPROPERTY(si.object_id, 'IsUserTable') = 1 ORDER BY OBJECT_NAME(si.object_id), si.index_id = = 1

14 CS363: Structured Query Language for Data Management 14 = = = = = = = [FilterDefinition] FROM #IndexListing WHERE [IndexListingID] -- So - it is either an index or a constraint -- Check if the index is unique IF (@IsPrimaryKey = 1) = 'ALTER TABLE [dbo].[' + '] ADD CONSTRAINT [' + '] PRIMARY KEY ' -- Check if the index is clustered IF 'IsClustered') = 0) + 'NON' = 0 ELSE = 1 + 'CLUSTERED' + CHAR(13) + '(' + CHAR(13) ELSE = 'CREATE ' -- Check if the index is unique IF 'IsUnique') = 1) + 'UNIQUE ' -- Check if the index is clustered IF 'IsClustered') = 1) + 'CLUSTERED ' = 1 ELSE = 0 + 'INDEX [' + '] ON [dbo].[' + ']' + CHAR(13) + '(' + = 0 -- Get the number of cols in the index = COUNT(*) FROM sys.index_columns ic INNER JOIN sys.columns sc ON ic.object_id = sc.object_id AND ic.column_id = sc.column_id WHERE ic.object_id AND index_id AND ic.is_included_column = 0

15 CS363: Structured Query Language for Data Management Get the file group info = f.[name] FROM sys.indexes i INNER JOIN sys.filegroups f ON i.data_space_id = f.data_space_id INNER JOIN sys.all_objects o ON i.[object_id] = o.[object_id] WHERE o.object_id AND i.index_id -- Get all columns of the index INSERT INTO #ColumnListing( [ColumnIDInTable], [Name], [ColumnIDInIndex],[IsIncludedColumn] ) SELECT sc.column_id, sc.name, ic.index_column_id, ic.is_included_column FROM sys.index_columns ic INNER JOIN sys.columns sc ON ic.object_id = sc.object_id AND ic.column_id = sc.column_id WHERE ic.object_id AND index_id ORDER BY ic.index_column_id > 0 = 1 = = = '' = = = = IsIncludedColumn FROM #ColumnListing WHERE [ColumnListingID] = 0 = CHAR(9) + '[' + '] ' -- Check the sort order of the index cols???????? IF (INDEXKEY_PROPERTY (@idxtableid,@idxid,@columnidinindex,'isdescending')) = 0 + ' ASC ' ELSE + ' DESC ' + ', ' ELSE -- Check for any include columns IF LEN(@sIncludeCols) > 0 + ',' + '[' + ']' + 1 TRUNCATE TABLE #ColumnListing --append to the result IF LEN(@sIncludeCols) > 0

16 CS363: Structured Query Language for Data Management CHAR(13) + ') ' + ' INCLUDE ( ' + ' ) ' ELSE + CHAR(13) + ') ' -- Add filtering IS NOT NULL = ' WHERE ' + ' ' + CHAR(13) ELSE = '' -- Build the options = 'WITH ( PAD_INDEX = ' IF 'IsPadIndex') = 1 + 'ON,' ELSE + 'OFF,' + ' ALLOW_PAGE_LOCKS = ' IF 'IsPageLockDisallowed') = 0 + 'ON,' ELSE + 'OFF,' + ' ALLOW_ROW_LOCKS = ' IF 'IsRowLockDisallowed') = 0 + 'ON,' ELSE + 'OFF,' + ' STATISTICS_NORECOMPUTE = ' -- THIS DOES NOT WORK PROPERLY; IsStatistics only says what generated the last set, not what it was set to do. IF 'IsStatistics') = 1) + 'ON' ELSE + 'OFF' -- Fillfactor 0 is actually not a valid percentage on SQL 2008 R2 IF 90 ) <> 0 + ',FILLFACTOR = ' + CAST( 90 ) AS VARCHAR(3) ) IF (@IsPrimaryKey = 1) -- DROP_EXISTING isn't valid for PK's + ' ) ' ELSE + ',DROP_EXISTING = ON ) ' + CHAR(13) + CHAR(13) R2 allows ON [filegroup] for primary keys as well, negating the old "IF THE INDEX IS NOT A PRIMARY KEY - ADD THIS - ELSE DO NOT" IsPrimaryKey IF statement + ' ON [' + ']' + CHAR(13) INSERT INTO #IndexSQL (TableName, IndexName, IsClustered, IsPrimaryKey, IndexCreateSQL) SELECT * FROM #IndexSQL

17 CS363: Structured Query Language for Data Management 17 STORED PROCEDURE (SECTION 4) COMPLETED BY: Trina VanderLouw Section 4 Criteria: A Stored Procedure that does the following: it accepts three parameters called Category, InventoryLevel and IntroDate. The output should list all Inventories where the current quantity is below the specified InventoryLevel for the specified Category. It should exclude any Inventories that are time stamped prior to the supplied IntroDate parameter. Name the stored procedure appropriately and provide the script to create it. Also, supply the script to call this new stored procedure passing it parameter values of your choice (CS363, 2012). Stored Procedure for CCI STORED PROCEDURE LowInventory USE [CCI] /****** Object: StoredProcedure [dbo].[lowinventory] Script Date: 04/13/ :24:50 ******/ SET ANSI_NULLS ON SET QUOTED_IDENTIFIER ON -- ========================================================= -- Author: Trina VanderLouw -- Create date: April 13, CS363: SQL for Data Management; Group Project: Team E -- Description: Returns list of all inventories where the -- current inventory is below the specified InventoryLevel -- for the specified Category. List Excludes any inventories -- that are time stamped prior to the supplied IntroDate. -- ========================================================== CREATE PROCEDURE [dbo].[lowinventory] -- Parameters for the stored int = int = date AS -- SET NOCOUNT ON added to prevent extra result sets from -- interfering with SELECT statements. SET NOCOUNT ON; -- Statements to return low inventory list SELECT CCI.dbo.Products.ProName FROM CCI.dbo.Products LEFT OUTER JOIN CCI.dbo.Inventory ON Products.ProductID = Inventory.InvProductID WHERE Inventory.InvCurrentInStock AND Inventory.InvCatID AND NOT Inventory.InvDateIntroduced CALL TO EXECUTE STORED PROCEDURE

18 CS363: Structured Query Language for Data Management 18 USE [CCI] EXEC LowInventory 1, 50, ' ' To test the query: Team Echo passed in category 1, less than 50 for inventory level, and not prior to This was the product list returned. (Team Echo added a few more products to try out the query with different parameters.) Second test: Team Echo changed the date to a later date and only one product was returned. USE [CCI] EXEC LowInventory 1, 100, ' '

19 CS363: Structured Query Language for Data Management 19 CONCLUSION COMPLETED BY: Darrell Moore In closing, we are awaiting Canine Caper's Inc (CCI) acceptance of this database design proposal. The necessary tools to deploy this design have been included within this proposal. Upon deployment of the CCI database we will remove all test data and user accounts. At that time new user accounts will be created prior to the addition of legitimate data. In recap this proposal contains the necessary CCI database ERD, the scripts necessary to build the CCI database, the scripts necessary to build CCI's users, roles, logins, and privileges, example report queries, functional indexes and scripts, and necessary stored procedures (CS363, 2012). REFERENCES CS363. (2012, February 21). Colorado Technical University Online CS363 Task Listing. Retrieved February 21, 2012, from Colorado Technical University Online Virtual Campus:

20 CS363: Structured Query Language for Data Management 20 SQL Statements Trina VanderLouw Colorado Technical University

21 CS363: Structured Query Language for Data Management 21 Northwind SQL Statements This assignment requires statements to check the modifications to the database from Phase 3 IP 1. Each of the queries returned the desired results. 1. Using the Northwind database, write a script to insert the following data: One new Category Name = Junk Food, Description = yummy delights SELECT * FROM Northwind.dbo.Categories WHERE CategoryName = 'Junk Food' This query returned one new category called Junk Food with a description of yummy delights. 2. Add a Product for your new Junk Food category. Product = Twinkies, Supplier = Tokyo Traders, Category = Junk Food QuantityPerUnit = 10 boxes UnitsInStock = 0, UnitsOnOrder = 0, ReorderLevel = 10, Disabled = 0 SELECT * FROM Northwind.dbo.Products WHERE ProductName = 'Twinkies' This query returned one product entry for Twinkies with all the correct values set. 3. In an attempt to liquidate some Products, in the Northwind database, provide a script to set all Products in the Condiments category that have less than 20 units in stock to a price of $5.00 and disable them. HINT: four records should be affected SELECT * FROM Northwind.dbo.Products WHERE CategoryID=2 AND UnitsInStock<20 This query showed me the four products that were changed and that they were all set to $5.00 and Discontinued. 4. Your boss has decided against the new Junk Food Category. Provide a script to delete the Junk Food Category as well as any Products assigned to that category. SELECT * FROM Northwind.dbo.Products WHERE CategoryName = 'Junk Food' SELECT * FROM Northwind.dbo.Categories WHERE CategoryName = 'Junk Food' Both queries returned 0 results.

22 CS363: Structured Query Language for Data Management Using the Northwind database, write a script to insert the following data: One new Category Name = Junk Food, Description = yummy delights INSERT INTO Northwind.dbo.Categories (CategoryName, Description) VALUES ('Junk Food', 'yummy delights') 6. Add a Product for your new Junk Food category. Product = Twinkies, Supplier = Tokyo Traders, Category = Junk Food QuantityPerUnit = 10 boxes UnitsInStock = 0, UnitsOnOrder = 0, ReorderLevel = 10, Disabled = 0 For this query I had to lookup the SupplierID and CategoryID. These were found using: SELECT * FROM Northwind.dbo.Categories WHERE CategoryName='Junk Food' This told me the CategoryID was 9. SELECT * FROM Northwind.dbo.Suppliers WHERE CategoryName= Tokyo Traders This told me the SupplierID was 4. Then I wrote the query to add the Twinkies. INSERT INTO Northwind.dbo.Products (ProductName, SupplierID, CategoryID, QuantityPerUnit,UnitsInStock, UnitsOnOrder, ReorderLevel, Discontinued) VALUES ('Twinkies', 4, 9, 10, 0, 0, 10, 0) 7. In an attempt to liquidate some Products, in the Northwind database, provide a script to set all Products in the Condiments category that have less than 20 units in stock to a price of $5.00 and disable them. HINT: four records should be affected For this update I looked up the condiments CategoryID. SELECT * FROM Northwind.dbo.Categories WHERE CategoryName='Condiments' This told me the CategoryID was 2. The next query I ran was an update to set the price to $5.00 and discontinued for the products that are in category 2 and have less than 20 in stock. It changed four products. UPDATE Northwind.dbo.Products SET UnitPrice=5, Discontinued=0 WHERE CategoryID=2 AND UnitsInStock<20

23 CS363: Structured Query Language for Data Management Your boss has decided against the new Junk Food Category. Provide a script to delete the Junk Food Category as well as any Products assigned to that category. For this query I chose to delete all the products in category 9 (Junk Food) and then to delete the Category Junk Food. DELETE FROM Northwind.dbo.Products WHERE CategoryID=9 DELETE FROM Northwind.dbo.Categories WHERE CategoryName='Junk Food' Northwind Customer s Report 1. For a Customers report, show the Company, Contact name, their title, the CustomerId, Country and Region (in that order). Rename the Region column in your output as RegionOrState. Sort by Country, then Region. USE Northwind SELECT CompanyName, ContactName, ContactTitle, CustomerID, Country, Region AS "RegionOrState" FROM Customers ORDER BY Country, Region; 2. Provide a unique list of the Countries where we have Customers USE Northwind SELECT DISTINCT Country FROM Customers; 3. A list of all Customers that don't have a Fax number USE Northwind SELECT CompanyName FROM Customers WHERE Fax IS NULL; 4. An Ordering Clerk comes to you with the Company name of a supplier and needs the SupplierId. The Company is Mayumi's. Write a query to provide the SupplierId. USE Northwind SELECT SupplierID, CompanyName FROM Suppliers WHERE CompanyName LIKE 'Mayumi%s'; 5. A list of all discontinued products in Category 1 and 6. **** I ordered by category and then alphabetically even though it was not required****

24 CS363: Structured Query Language for Data Management 24 USE Northwind SELECT ProductName FROM Products WHERE Discontinued = '1' AND (CategoryID = '1' OR CategoryID = '6') ORDER BY CategoryID, ProductName 6. A list of all Orders that contains the OrderId, OrderDate and name of the Company that placed the Order, sorted by most recent date USE Northwind SELECT OrderID, OrderDate, CompanyName FROM Orders, Customers WHERE Orders.CustomerID = Customers.CustomerID ORDER BY OrderDate; 7. Provide a list of all orders that includes the OrderId, the employee s name that helped with that order and the name of the company that placed the order. The list should also have the country of the shipping address. Sort it alphabetically by employee name, then country. The list should include only those orders shipped outside of the USA USE Northwind SELECT OrderID, FirstName, LastName, CompanyName, Customers.Country FROM Orders, Employees, Customers WHERE Customers.Country NOT LIKE 'USA' ORDER BY FirstName, LastName, Customers.Country 8. Number of Orders placed in the month of April of 1997 USE Northwind SELECT COUNT(OrderID) AS 'TotalOrders' FROM Orders WHERE OrderDate BETWEEN ' ' AND ' '; 9. What is the total number of Customers in each country? Name the count column CountryCount and sort in order of most to least. USE Northwind SELECT Country, COUNT(CustomerID) as 'CountryCount' FROM Customers GROUP BY Country ORDER BY CountryCount desc 10. List all Customers (include CustomerId and CompanyName) that have placed less than orders. Include those who have zero orders placed. Name the count field "OrderCount". Sort by least number of orders placed.

25 CS363: Structured Query Language for Data Management 25 USE Northwind SELECT Customers.CustomerID, Customers.CompanyName, COUNT(OrderID) as 'OrderCount' FROM Customers LEFT OUTER JOIN Orders ON Customers.CustomerID = Orders.CustomerID GROUP BY Customers.CustomerID, Customers.CompanyName HAVING COUNT(OrderID) <= 3 ORDER BY OrderCount

26 CS363: Structured Query Language for Data Management 26