HSQ Databases and SQL

Transcription

1 HSQ Databases and SQL Server Database Golf Forum and Handicap Calculator Reader: Mansha Nawaz Author: Michael Ord H

2 Contents 1. CASE STUDY CASE STUDY SCENARIO CASE STUDY ADDITIONAL CONSIDERATIONS & ERDS CONSULTED DELIVERABLES STUDY PLAN MS SQL SERVER DATABASE DATABASE DIAGRAMS ERD Physical View ERD Logical Views MANAGEMENT STUDIO Tables (physical) with sample data Views (logical) with sample data DEMONSTRATION OF SQL CODE DATA DEFINITION LANGUAGE Create Table Create Index Drop Table Constraint Create View Create Trigger DATA MANIPULATION LANGUAGE Select and From Where Clause Order By Distinct Between and Like In and Not In Joining Tables Aliases for Tables Sub Queries Insert Delete Update SQL: SHOW UNDERSTANDING OF ADVANCES SERVER CLIENT FEATURES MS SQL SERVER IMPORT AND EXPORT MS SQL SERVER ATTACH AND DETACH MS SQL SERVER TO MS ACCESS WORKSTATION MS SQL SERVER WEB DEVELOPMENT (VISUAL STUDIO.NET) CRITICAL REVIEW CONCLUSION CRITICAL REVIEW OF ICA ASSESSMENT CRITERIA OR DELIVERABLES Criteria 1 Report Criteria 2 SQL Implementation: ERD: Selection of entity & relationship types Criteria 2 SQL Implementation: Tables & Views: consistent with ERD & with appropriate primary keys Tables (physical) Views (logical) ii

3 Criteria 2 SQL Implementation: Foreign keys & other attributes Criteria 2 SQL Implementation: Data constraints & Relationships Criteria 2 & 3 SQL Implementation & Test data Criteria 3 SQL Implementation SQL DDL and DML statements based on data model Criteria 4 SQL: Show understanding of Additional or Advance Features Sub Sections to come from ICA feedback sheet CRITICAL REVIEW OF ICA ICA GOALS ICA ACHIEVEMENTS ICA NON ACHIEVEMENTS ICA EVALUATION ICA REFLECTION CRITICAL REVIEW OF PRODUCT DATABASE GOALS DATABASE ACHIEVEMENTS CURRENT SYSTEM STATE DATABASE NON ACHIEVEMENTS INCOMPLETE SYSTEM STATE DATABASE FUTURE ENHANCEMENTS DATABASE EVALUATION DATABASE REFLECTION CRITICAL REVIEW OF PERSONAL DEVELOPMENT REFERENCES APPENDIX HYPERLINKS TO THE SQL DATABASE.MDF AND.LDF FILES SCRIPT FILES FOR SECTION 3 AND ADDITIONAL MATERIAL iii

4 1. Case Study 1.1. Case Study Scenario The Purpose of this report is to design and crate a database which will run in the background of a website. The website will be used by golfer to enter their scores from games of golf and to keep track of their handicap online. The initial design of the Database comes from a previous module studied. The Systems analysis and design module formulated the following Context diagram: Diagram 1.1. Golf Forum and Handicap Calculator As this diagram is expanded deeper the tables needed for the database, can be found. The following partial diagrams show the tables. For golfers; Diagram 1.2. Registration Process 4

5 Scores, Handicaps, Courses; Diagram 1.3. Enter scores Reports; Diagram 1.4 Usage Report 5

6 Scores, Score Difference; Diagram 1.5. Calculate Handicap For the forum part of the database the following additional tables will be needed: FAQ's, Answers; Diagram 1.6. Access forum 6

7 1.2. Case Study Additional Considerations & ERDs consulted In addition to these predefined tables there will be some rearranging and creation of other tables. These tables have been thought of after researching other similar ERD s found online, below is a couple of screenshots. The screenshots show ERD s that includes extra tables I believe will enhance the design of the database; Diagram 1.7. FAQ s model. accessed 11/12/2009 From the above model I will utilise the design of some of the FAQ s tables and adapt them to the tables I am using in the database. 7

8 Diagram 1.8. Golf Tournaments Data Model. Barry Williams August 2001 This model closely represents the idea of database I shall be modelling, some items on the model may be utilised and adapted for use in my report. Throughout the design of the database there will be revisions of tables, columns and relationships. This will be beneficial to the final design and it should lead to a well designed and functioning database. 8

9 1.3. Deliverables The final product of the ICA consists of this report along with a database designed on MSSQL Server. The table and view of the database have been created, using the aforementioned diagrams showing the data model for such a system. The tables fully mirror those of the data model. The views are only a representation of some of the processed that were mentioned in the data model. If the database was to be created into a fully operational and live entity then the other processes of the data model would be replicated. There are also SQL scripts for both the Data Definition Language (DDL), and the Data Manipulation Language (DML). A resources file is packaged on a CDRom along with this report and the database files. In the resource folder there can be found Create scripts and insert scripts for all parts of the database along with true test data and false test data. Files for MS Access and VisualBasic.NET projects are also packed with the resources to show the connection of the database to external software. Links to the.mdf.ldf filed can be found in the appendix, click here. Also the entire data import file can also be found in the appendix, click here Study Plan Below is a diagram showing the intended plan of study for creating the database and report for the ICA in this module. HSQ Databases & SQL ICA Study Plan DD TASKS 1. DESIGN Case Study & Deliverables x x ERD Full & Partial x x Tables x x 2 IMPLEMENTATION TABLES x x x x CONSTRAINTS x x VIEWS x x x TRIGGERS x x x INSERTS x x x DROPS x x SQL - DDL & DML x x x 3 ADVANCE FEATURES SQL-Access Project x x x x SQL Import Export Database x x SQL-Web Database x x 4 REPORT x x x x Dates 5/10/09 21/10/09 6/11/09 22/11/09 8/12/09 24/12/09 9/1/10 Week Diagram 1.9. Database Study Plan. Adapted from M. Nawaz ica.dd.studyguide.xls accessed 11/12/2009 This study plan will be followed as closely as viably possible. 9

10 2. MS SQL Server Database 2.1. Database Diagrams The database designed can be shown by using different Entity Relationship Diagram (ERD) views, the first view is the full ERD physical view, and other view include the ERD logical views showing partial ERD structures ERD Physical View Below is a diagram of the ERD Physical view; this diagram display the full model indicating the primary and foreign keys and this relationship links. Diagram 2.1. Full Database entity relationship Diagram (ERD) 10

11 ERD Logical Views The following sets of diagrams are partial views of the ERD specifically created to give the views the user of the database would see. The diagram below shows the view of the user using the forum. Diagram 2.2. Forum View The following diagram shows the view for banned players. Diagram 2.3. Banned Players View 11

12 The next diagram shows the view for handicaps. Diagram 2.4. Handicaps view. The next diagram shows the view of the courses. Diagram 2.5. Courses View 12

13 The following diagram shows the view of the scorecard relationships. Diagram 2.6. Scorecard view. The last diagram shows the report view of the tables. 13

14 Diagram 2.7. Reports view Management Studio The following chapter will look at the final views of the tables in the Master Entity Relationship Diagram (ERD), which is the physical view of the database and also the logical view. The management studio is where the database is created and managed. The following screenshot shows the database as accessed through the management studio Tables (physical) with sample data The diagrams below are screen shots of data tables with data inserted into the database. As seen in their design view. The following diagram shows a full list of the tables in the database. Diagram 2.8. Tables list 14

15 Answers Table (Design View) Diagram 2.9. Answers Table (Design View) Answers Table (Test Data) Diagram 2.9. Answers Table (Test Data) 15

16 Banned Table (Design View) Diagram Banned Table (Design View) Banned Table (Test Data) Diagram Banned Table (Test Data) 16

17 Categories Table (Design View) Diagram Categories Table (Design View) Categories Table (Test Data) Diagram Categories Table (Test Data) 17

18 Courses Table (Design View) Diagram Courses Table (Design View) Courses Table (Test Data) Diagram Courses Table (Test Data) 18

19 FAQ s Table (Design View) Diagram FAQ stable (Design View) FAQ s Table (Test Data) Diagram FAQ s Table (Test Data) 19

20 FAQ sanswers Table (Design View) Diagram FAQ sanswers Table (Design View) FAQ sanswers Table (Test Data) Diagram FAQ sanswers (Test Data) 20

21 Handicaps Table (Design View) Diagram Handicaps Table (Design View) Handicaps Table (Test Data) Diagram Handicaps Table (Test Data) 21

22 Holes Table (Design View) Diagram Holes Table (Design View) Holes Table (Test Data) Diagram Holes Table (Test Data) 22

23 Players Table (Design View) Diagram Players Table (Design View) Players Table (Test Data) Diagram Players Table (Test Data) 23

24 PlayersScores Table (Design View) Diagram PlayersScores Table (Design View) PlayersScores Table (Test Data) Diagram PlayersScores Table (Test Data) 24

25 PlayersScoresHoles Table (Design View) Diagram PlayersScoresHoles (Design View) PlayersScoresHoles (Test Data) Diagram PlayersScoresHoles Table (Test Data) 25

26 Reports Table (Design View) Diagram Reports Table (Design View) Reports Table (Test Data) Diagram Reports Table (Test Data) 26

27 ScoreCards Table (Design View) Diagram Scorecards Table (Design View) ScoreCards Table (Test Data) Diagram Scorecards Table (Test Data) 27

28 ScoreDifferences Table (Design View) Diagram ScoreDifferences Table (Design View) ScoreDifferences Table (Test Data) Diagram ScoreDifferences Table (Test Data) 28

29 Views (logical) with sample data Logical views are snap shots of linked tables showing the tables used by users to access different parts of the database. Or to put it another way they are the views of the database tables that users will be able to access during different processes EditingCourse View This view allows the selection of an individual course and the associated holes, the first diagram is of the tables and columns selected. Diagram EditingCourse (Tables and Columns) The second is the SQL code and results. Diagram EditingCourses (SQL Code and results) 29

30 PlayerDetails View The following diagrams show the tables and columns used to filter the players details by username. Diagram PlayerDetails View (Tables and Columns) The next diagrams show the SQL code and Results of the query. Diagram PlayerDetails (SQL code and Results) 30

31 EnteringScores View This view has been created to view a specific course for scores to be entered by the user. The results are filtered by player option and then by hole number. Diagram EnteringScores (Tables and Columns) Diagram EnteringScores (SQL code and Results) 31

32 Forum View This view allows the selection of threads relating to, in this case, all threads under the category of Tour Talk. Diagram Forum View (Tables and Columns) Diagram Forum View (SQL code and Results) 32

33 EndOfMonthReport View This view allows the selection of results to show items from the reports tables depending on selected filtering, in this example a list of reports where the number of banned players is greater than 3. Diagram EndOfMonthReports View (Tables and Columns) Diagram EndOfMonthReports View (SQL code and Results) 33

34 CalculatingHandicaps View This view enables the view of players scores, score differences and handicaps to be viewed while filtering the results through the player username, in this example micktommyord. Diagram 2.46 CalculatingHandicaps View (Tables and Columns) Diagram CalculatingHandicaps View (SQL code and Results) 34

35 3. Demonstration of SQL Code 3.1. Data Definition Language The Data definition Language is SQL code used in the creation and amending of the database, the following sections will demonstrate the use of such code Create Table To create a table in the database follow these following steps. Right click on the Tables folder and select new table. Diagram 3.1. Right Click on Tables folder. Then enter the names of the columns requires and the data type to be stored in the column. Diagram 3.2. Enter Column details Next you need to create the primary key, which need to be unique to the table and database. This is done my highlighting the column to be used and then clicking on the Key Icon. 35

36 More than one column can be selected but for this example I am only going to select one column. Diagram 3.3. Adding a Primary Key Once this is all done then the table can be saved. By clicking the save button and entering a name. I will call this table Drop table for use later in the report. Diagram 3.4. Saving the table The saved table will then be view in the list of tables in the object explorer. Diagram 3.5. DropTable in Tables list 36

37 The SQL code to do the same process is shown below. CREATE TABLE [dbo].[droptable] ( [Test 1] [nchar](10) NOT NULL, [test 2] [date] NULL, [test3] [nvarchar](50) NULL, ) GO A link to the notepad file for this code can be found in the Appendix Create Index To create and index in a table is to define the primary key for he table. To do this expand the drop table by clicking the + and then right click on the indexes folder. Then select new index. Diagram 3.6 Select New Index Then enter the name of the Primary Key and select Clustered and select the unique option. Diagram 3.7. Primary key details pop up. 37

38 Next click add and choose the column you wish to have as the primary key, remember that it is possible to select more than one column. Diagram 3.8. Selecting columns Now click on the OK buttons and the Primary key will be created. The following SQL code will create the same Primary Key. CREATE UNIQUE CLUSTERED INDEX [PK_DropTable] ON [dbo].[droptable] ( [Test 1] ASC ) WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY = OFF, DROP_EXISTING = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] GO A link to the notepad file for this code can be found in the Appendix. 38

39 Drop Table The simplest way to drop a table is to right click on the Drop Table folder and select delete. Diagram 3.9. Deleting the Drop Table The SQL code for this process is as follows. IF EXISTS (SELECT * FROM sys.objects WHERE object_id = OBJECT_ID(N'[dbo].[DropTable]') AND type in (N'U')) DROP TABLE [dbo].[droptable] GO A link to the notepad file can be found in the Appendix Constraint As an example, in the Players table there need to be a constraint to force the default value of the banned bit as false. To add a constraint you will need to complete the following instructions. 39

40 Right click on the Player table and view the properties window. Diagram Creating a new Constraint. Then in the properties window for the Banned column, for the default binding enter ((0)) and save the table. Diagram Enter the default value required. After a refresh of the table when you expand the constraints folder the new constraint will be there. Diagram Refreshing the constraints. 40

41 The SQL code to perform this task is as follows. ALTER TABLE [dbo].[player] ADD CONSTRAINT [DF_Player_banned] DEFAULT ((0)) FOR [banned] GO A link to the notepad file can be found in the Appendix. While trying to add a Check constraint to validate the input of the player option on PlayersScores Table, I ended up with the following error warning, and as to this moment I have not been able to find a solution. Diagram Constraint error. The full insert script for the constraints and a script to test the constraints can be found in the appendix. Click Here. 41

42 Create View The view of the Player details has been created for the database this was done in the following two ways. Right click on the Views folder and select new view. Diagram Create New View. Next add the tables required to the desktop. Diagram Add Tables. 42

43 Then select the columns requires and enter the filters and the sorting options in the columns as they are underneath. This will then create SQL code in the next window down and when the query is run the results will show in the bottom pane. Diagram The filtering, SQL Script and results. The associated script to create the table is below. CREATE VIEW [dbo].[playerdetails] AS SELECT TOP (100) PERCENT dbo.player.golfertitle, dbo.player.golferforname, dbo.player.golfersurname, dbo.player.golferusername, dbo.player.golferpassword, dbo.player.golfer , dbo.player.golferhouse#, dbo.player.golferstreet, dbo.player.golfervillage, dbo.player.golfertown, dbo.player.golfercounty, dbo.player.golferpostcode, dbo.handicap.starthandicap FROM dbo.player INNER JOIN dbo.handicap ON dbo.player.golfer# =dbo.handicap.golfer# WHERE (dbo.player.golferusername = 'leebigcity') GO A link to the notepad file can be found in the Appendix. 43

44 Create Trigger If you wish to create a trigger which will protect the table from being deleted can be accomplished as follows. The idea for this trigger came from Robert Dove 09 ICA for Database and SQL. Open a new query window. Diagram Creating the new trigger. When the execute button is clicked you should receive the Command(s) completed successfully text in the messages pane. To check the trigger we can try to create a new table. Diagram New Table 44

45 When we go to save the new table the following happens. Diagram Trigger outputs the following message To remove this trigger we must run the following drop trigger script. Diagram Dropping the Trigger Now it is possible to create, alter and drop tables from the database. A link to the notepad file can be found in the Appendix. 45

46 3.2. Data Manipulation Language Select and From The select and from statement is used to find and display information held in the tables. The information to display can be individually chosen and displayed in a different order to the information held in the tables. The following code will find the data about the Golf courses and show only the Course name, website, , total yards, and the last time the data was updated. Select Course.CourseName, course.whitetotalyards, Course.Course , Course.CourseWebsite, Course.LastEditDate From dbo.course go The results are as shown. Diagram Select and From Results. A link to the notepad file can be found in the Appendix Where Clause The Where clause is used to filter the results of a query to match the chosen criteria. The following script will display the yellow and red holes, par and Scratch Indexes for a filtered course. SELECT Course.CourseName, Holes.Hole#, Holes.HoleName, Holes.YellowPar, Holes.YellowSI, Holes.RedPar, Holes.RedSI FROM Course INNER JOIN Holes ON Course.Course# = Holes.Course# WHERE (Course.Course# = N'0002') 46

47 The result of this script is shown below, Diagram Where Clause A link to the notepad file can be found in the Appendix Order By The Order By statement is used to sort the results into a ascending of descending list. There can be many levels of order each level being sorted in turn until the last level is found. The following example will shoe a multi level Order By. SELECT TOP (100) PERCENT dbo.player.golferusername, dbo.scorecard.datetime, dbo.scoredifference.changeintotal, dbo.handicap.starthandicap, dbo.handicap.handicaprnd, dbo.handicap.handicapexact FROM dbo.handicap INNER JOIN dbo.player ON dbo.handicap.golfer# = dbo.player.golfer# INNER JOIN dbo.scoredifference ON dbo.player.golfer# = dbo.scoredifference.player# INNER JOIN dbo.scorecard ON dbo.scoredifference.scorecard# = dbo.scorecard.scorecard# WHERE (dbo.player.golferusername = 'micktommyord') ORDER BY dbo.player.golferusername, dbo.scorecard.datetime 47

48 The result of the script is shown below, as can be seen the order of the sort is by username first then by the date. Diagram Order By example A link to the notepad file can be found in the Appendix Distinct The Distinct rule will reduce the results shown to only one occurrence of the result, for example there may be many instances of a hole par with the same total, where if the distinct is used then only one instance will appear. For example; SELECT YellowPar From Holes Gives the results of all the yellow pars; Diagram All Yellow Par results. 48

49 Where as when Distinct is used; SELECT DISTINCT YellowPar From Holes The result of this script now is as follows; Diagram 3.25 Distinct Results A link to the notepad file can be found in the Appendix Between and Like These filter options allow the selection of either results within a range, or results which match the criteria. The first example shows the use of Between criteria. SELECT dbo.player.golferusername, dbo.handicap.handicapexact, dbo.playerscores.grossscore, dbo.playerscores.scorecard# FROM dbo.handicap INNER JOIN dbo.player ON dbo.handicap.golfer# = dbo.player.golfer# INNER JOIN dbo.playerscores ON dbo.handicap.golfer# = dbo.playerscores.player# AND dbo.player.golfer# = dbo.playerscores.player# WHERE (dbo.handicap.handicapexact > 15) AND (dbo.handicap.handicapexact < 30) 49

50 The results of this script can be seen below. Diagram Between Filter The second example shows the use of the Like filter; SELECT dbo.catagories.[catagory description], dbo.faqs.faqtitle, dbo.faqs.faqkeywords, dbo.answers.answerdetails FROM dbo.answers INNER JOIN dbo.catagories ON dbo.answers.catagory# = dbo.catagories.catagory# INNER JOIN dbo.faqs ON dbo.catagories.catagory# = dbo.faqs.catagory# INNER JOIN dbo.faqsanswers ON dbo.answers.answer# = dbo.faqsanswers.answer# AND dbo.faqs.faq# = dbo.faqsanswers.faq# WHERE (dbo.catagories.[catagory description] LIKE 'Tour Talk' OR dbo.catagories.[catagory description] LIKE 'Golf equipment') The Results of this script can be viewed below. Diagram Like Filter Example 50

51 A link to the notepad files can be found in the Appendix In and Not In Joining Tables The use of In and Not In is used to simplify the filtering of results, where sometime a large where statement would be needed. The first example is of the In statement. select Player.GolferUsername, Player.banned, Banned.FromDate, Banned.ToDate, Banned.Bannedreason from dbo.player INNER JOIN dbo.banned on dbo.player.golfer# = dbo.banned.golfer# where dbo.player.banned in ('True') The result of this can be view below. Diagram In Statement On the contrary if we use the Not In Statement as follows. select Player.GolferUsername, Player.banned, Banned.FromDate, Banned.ToDate, Banned.Bannedreason from dbo.player INNER JOIN dbo.banned on dbo.player.golfer# = dbo.banned.golfer# where dbo.player.banned Not In ('True') Then the results are now as shown. Diagram Not In Statement. 51

52 A link to the notepad file can be found in the Appendix Aliases for Tables The option to rename tables temporarily is useful it the names of the tables are going to be used repeatedly in the 'from, join, and where' statements. The following script is a good example of the use of aliases. Where Player is replaced by a, PlayersScores is replaced by b, PlayersScoresHoles is replaced by c, ScoreCard is replaced by d, and Course is replaced by e. SELECT DISTINCT TOP (100) PERCENT e.coursename, d.datetime, a.golferforname, a.golfersurname, b.playeroption, c.hole#, c.holescore, b.grossscore, b.netscore FROM dbo.player AS a INNER JOIN dbo.playerscores AS b ON a.golfer# = b.player# INNER JOIN dbo.playerscoresholes AS c ON b.scorecard# = c.scorecard# INNER JOIN dbo.scorecard AS d ON b.scorecard# = d.scorecard# AND c.scorecard# = d.scorecard# INNER JOIN dbo.course AS e ON d.course# = e.course# AND d.course# = e.course# WHERE (e.coursename = 'Elemore Family Golf Centre') AND (d.datetime = CONVERT(DATETIME, ' :00:00', 102)) ORDER BY b.playeroption, c.hole# From this the result would be the same as is was without the aliases. Diagram Using Aliases. A link to the notepad file can be found in the Appendix. 52

53 Sub Queries Sub Queries help to define results from another query, the more sub queries there are the more intricate the result filter would become, so to way if we were to look at a golfer who has played on a certain course then we wanted to find the best score for the player. SELECT Min(PlayerScoresHoles.HoleScore) FROM Player CROSS JOIN PlayersScoresHoles Where Exists (SELECT Player.GolferUsername, Course.CourseName, PlayerScoresHoles.Hole#, PlayerScoresHoles.HoleScore FROM Player CROSS JOIN PlayersScoresHoles CROSS JOIN Course WHERE (Player. Golfer# = PlayerScoresHoles.Player#)) The result from the Sub Query alone would be as follows, Diagram Partial Results of Sub Query 53

54 And the full outcome would be; Diagram Sub Query Result. A link to the notepad file can be found in the Appendix Insert If we wish to insert a column into the Drop table we created earlier when we would use the following SQL code. ALTER TABLE dbo.droptable ADD InsertColumn nchar(10) NULL GO This would produce the following table layout. Diagram Insert Table A link to the notepad file can be found in the Appendix. 54

55 Delete If we like we could now have decided that the delete data which is no longer needed, therefore we could now use the following script to remove the data. For example if we were to delete all the data on the course of beamish then we would use the following script. DELETE FROM holes WHERE Course# = (SELECT DISTINCT Holes.Course# FROM Course INNER JOIN Holes ON Course.Course# = Holes.Course# WHERE (Course.CourseName = 'Beamish Park Golf Club')) GO DELETE FROM Course WHERE Course.CourseName = 'Beamish Park Golf Club' GO The result of using this code would return the table to its original state of only three columns. Diagram Delete from A link to the notepad file can be found in the Appendix. 55

56 Update If we were to have a Golfer who wished to change his username then the following code can be used, this will update the data in the stated cells only. UPDATE Player SET GolferUsername = 'leetheedge' WHERE Golfer# = The completed query returns the following statement. Diagram Update Data And the table now looks like this. Diagram Updated table results A link to the notepad file can be found in the Appendix. 56

57 4. SQL: Show understanding of Advances Server Client Features The following features of the SQL database software if more geared toward an advanced user. The sub chapters will provide evidence of the knowledge and experience gained during the module MS SQL Server Import and Export It is possible to import and export the databases data using the export wizard, the way to do this is by following these instructions. On the database to be exported right click, go down to tasks and then click on export data... Diagram 4.1. Export the data. Doing this will open the export wizard. On the first screen click the OK button. This brings you to the next screen for the selection of the database from which to export the data. The database should already be placed for selection, click next. Diagram 4.2. Select the database. 57

58 For this report there has been a txt file created to export the data to, but in reality the data can be exported to another database running either on a SQL server, Access, Excel, or other database server. The txt file is chosen on the next screen. Diagram 4.3. Select the destination. The next screen will offer a selection of either to copy some or all of the data to copy, or to write SQL script to manipulate or restrict the copied data. Diagram 4.4. selection option for export. 58

59 The next screen allows the selection of the table data to be exported, with the option of a preview to show the output of the export. Diagram 4.5. Select the table to export the data from. The next screen allows for the saving of the SSIS package, but for this scope of this report the finish button can be selected. Doing this will select the defaults for the rest of the options available. Diagram 4.6. Finish the wizard. 59

60 This leads to a confirmation of all to options selected and one final clock of the finish button will execute the package. Diagram 4.7. Check page details and click Finish. Once the package has finished the success screen will be viewed. Diagram 4.8. Success screen If other tables in the database are required to be exported then the wizard must be run for each table. He wizard will add the data onto the end of the previous saved export on the same txt file. 60

61 To import data then right click on the database, and move down to tasks and select Import data... Diagram 4.9. Select import data... This will again open a wizard, this time I have skipped the intro page and I have already selected to import the data from a flat file. Next we have to select the file to import. I will be using the flat file created in the export wizard. Make sure the this option is selected Diagram Browse for the source. 61

62 Click next, the following screen is a preview of the data to be imported. Diagram Preview screen. Next we come to the selection of the destination, for this report the destination id the original database file and the information are already in place. Click Next. Diagram Destination file location. 62

63 The following screen is to select the tables to be imported, but as there is only one table to import then no adjustment is required. Diagram Selection of tables to import. Again there is a confirmation screen to select to option to save the SSIS package, but we are just going to run the package immediately, click finish to skip the other options to their defaults. Diagram Save and run screen. 63

64 This penultimate screen confirms the action to be performed on the next press of the finish button, click finish. Diagram Finish and perform confirmation screen. Once the package has run the confirmation age shows, and the data is now entered into the correct table. Diagram Completed import of data The txt files for the ExportDataExample can be found in the appendix, click here. 64

65 4.2. MS SQL Server Attach and Detach There are times when a database held on a server will need to be attached and detached from the server. For example, at a time of migration, or transfer from one server to another. To complete these tasks I have created a guide to detach and then to attach the database.mdf and.ldf files. The first thing which needs to be done is to take the database offline. This can be done in the following way. Right click on the database move dome to tasks and click on the second option to Take Offline. Diagram Select to take database offline. You will be shown the following pop up which will action and then confirm the offline status of the database. Diagram Offline confirmation. 65

66 Now to detach a database from a server go the database to be detached and right click on the database name. Then from the pop out list hover over tasks and another pop out will appear, then you will be able to select detach. Diagram 4.19 Select to detach the database. Next double check the database is the right one and click OK. Diagram Check the database if the correct one. 66

67 The Object explorer will refresh and the detached database will no longer be available. Diagram Refreshed Object explorer. The following SQL script will also detach the database from the server. USE [master] GO EXEC = N'GolfForum' GO The notepad file for the SQL script can be found in the appendix. Click Here. Now that the database is detached the two files of the database can be copied and moved to wherever it is to be installed. The hyperlinks to the.mdf and.ldf files can be found in the appendix. To attach a database after a migration can be completed in the following way. In the Object explorer right click on the Databases folder and select attach. Diagram Select Attach. 67

68 On the pop up screen click on the add button. Diagram Click the add button. The following pop up then is used to locate the.mdf. As there is a link to the files in the appendix when the pop up appears then direct the browse to the files on the CDRom. In this example the files are held on my memory Key. Diagram Browse for the.mdf file. 68

69 This will now enter the details and locations of both of the database files, from here just click the OK button. Diagram Attach database with location of files in place. Confirmation of the attachment of the database can be found by refreshing the object browser. Diagram The Attached database. 69

70 The Attach database can be completed by using the following SQL script. USE [master] GO CREATE DATABASE [GolfForum] ON ( FILENAME = N'C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\GolfForum.mdf' ), ( FILENAME = N'C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\GolfForum_log.ldf' ) FOR ATTACH GO A link to the notepad file for the SQL script can be found in the appendix. Click Here. 70

71 4.3. MS SQL Server to MS Access workstation One of the must useful uses for a SQL database is to have the ability to connect to a variety of other database programs. In this way it is possible to design and store the database on the SQL server and to use an alternate program to run the front end, or user view of the database. The following screen shots will take you through connecting MS Access to a SQL database and create the tables. First open up MS Access and create a new database. In this example I have called the file Connection. Diagram Creating a new file. Once the file is created, click on the external data tab, select the more pull down and select ODBC Database. Diagram Selecting the external source. 71

72 The source pop up will appear and you then have two choices, highlight the Link to the data source by creating a linked table. choice as the SQL Database already exists. Diagram Select create link. At the select data source screen click on new or type in the name of the SQL Server. Here I chose new. Diagram Input name of data source. 72

73 Then scroll down to the SQL Server Native Client 10.0 and click next, or if you know the server details click on advanced. Diagram Select the driver for the data source. If you clicked next then now click browse. Diagram Browse for the data source. Then select where the dta is stored on the machine. Diagram 4.32.a. Finding the data file. Diagram 4.32.b. File path in text box. 73

74 There will then follow a confirmation screen, here check the details and click next. Diagram Confirmation page. We then return to the data source wizard and input the description and select the server. The default is (Local) but the show in this example I have been more specific and shown the server name. Diagram Description and server input. 74

75 Click next and select the option to change the default database to the GolfForum instead of Master. Then continue through the rest of the screens until the configuration screen is seen. Diagram Select GolfForum as default The rest of the options can be skipped as we will only use the defaults, click finish and the next screen will appear. On this screen click the Test Data Source... to test the connection. Diagram Test the source. 75

76 Once the button is clicked a test will run and return any errors found, but in this example we have a test successful displayed. Diagram Test Completed successfully confirmation. Click Ok twice to get back to the data selection screen and click ok. Diagram Final selection of data source. 76

77 Now select all the tables to link to from Access. Diagram Select tables. Once the wizard has completed its import all the tables can be viewed on the left hand side of the screen, and if a table is double clicked, the table opens and all the data for the table has been populated. Diagram Linked table with data populated. A shortcut to the MS Access database can be found in the appendix. Click Here. 77

78 4.4. MS SQL Server Web Development (Visual Studio.NET) As this database is going to be running on a website I feel it is necessary to show how to connect the database to a website using Visual Studio.Net. I will be using Visual Basic as this is the only language I have started to learn. Open Visual studio and on the projects prompt select web and click on ASP.Net web page. Then enter the name of the solution and click ok. Diagram Create a new project. Doing this created the script for the web page, now right click on GolfForumVB in the solution explorer select, Add, New Item... Diagram Select Add New Item. 78

79 Add a master page and rename it something suitable, for example I have named mine GolfForumMaster.Master. Diagram Create master page. Next we will add a CSS file to control the look of the web page, repeat the instructions to add item, but this time select a style sheet and name it something appropriate. Diagram Create Cascading style sheet (CSS) Although there is nothing in my web page at the moment I am still able to connect to the database. Click on the tools tab at the top of the screen and on the pull down select Connect to Database.... Diagram click to connect to a database. 79

80 On the choose database source pop up select Microsoft ODBC Data Source and click continue. Diagram Select Microsoft ODBC Data Source. On the add connection screen select Use connection string and click Build.. Diagram Click Build. 80

81 One the select Data source screen click New.... Diagram Open the Database file. On the Create New Data Source screen scroll down and select SQL Server Native Client Then Click Next. Diagram Select new source. 81

82 Click Browse, search for the database file then click save. Diagram Search for Database File. Click Next. Diagram File found now click next. 82

83 Check the details on the confirmation page and click finish. Diagram Confirm details and click finish. This opens another screen to connect to SQL server, enter the details and select the server. Click next twice. Diagram Server details. 83

84 Now select the default database to be the correct one, i.e. GolfForum, Then click next. Diagram Change the default database to the correct one. Select any other optional choices for the database running over the internet and click finish. Diagram Choose option for security and log file. 84

85 A confirmation page will appear, check the details and then click test connections. This will follow with a confirmation of success screen. Diagram 4.46.a. Confirmation page Diagram 4.46.b. Test Completed Successfully screen. Then once returned to the add database screen click OK. Diagram Add connection with connection string added. 85

86 The added database can now be seen in the Server explorer. Diagram Database connected to VisualBasic.Net. 86

87 5. Critical Review This is my critical review of the work produced for this ICA; overall I feel that the final document covers all the criteria. But with practice and more knowledge of the systems design and implementation future reports would be even more professionally produced, and contain more relative and accurate information CONCLUSION To the end of this ICA I feel that there has been a lot of learning and knowledge gained. The task of producing a database from previous ideas has been enjoyable. Overall I feel I have worked toward a Distinction, but in reality I guess a merit will be given. There have been times when the workload has seemed to be mountainous, and then once halfway through a task the path became a lot clearer. In hindsight I think that making a start earlier to the document would have been to my advantage CRITICAL REVIEW of ICA Assessment Criteria or Deliverables Criteria 1 Report To the best of my capacity I have attempted to produce a professional and detailed document, highlighting the function of the created database. I do feel that the document looks a bit wordless, but as the saying goes a picture paint a thousand words. I do find it difficult to put in the effort and concentration in completing documents like this, but when I take the production in small time scales then the final product look to me, well presented Criteria 2 SQL Implementation: ERD: Selection of entity & relationship types The creation of the entity relationship diagram was one of the easiest tasks in the ICA. It basically became a join the dots task, as the primary keys and foreign key had been created at the time of the tables. To start with I did over complicate the diagram by creating too many relationships on the ERD, but once I started to work with the data I soon noticed that all the relationship links started to over complicate the process of entering data into the system. The software used also automatically selects the best relationship type for the join. The final ERD is a very close representation of the original data model, with the exception of the extra tables to link the FAQ s and Answers Criteria 2 SQL Implementation: Tables & Views: consistent with ERD & with appropriate primary keys Tables (physical) Views (logical) This section of the report was easy to create, as I have worked from the model produced in an earlier module. As I had received a high mark for the module it was apparent that the model structure was sound. From there I pretty much translated the model into tables and view. The creation of the tables was very straight forward; the only trouble I ran into was when I was creating the courses table and where to place the holes for the course. I realised that the holes was a repeated group of results but, I was unsure of how to implement them into the database. After a quick consultation with Mr. Nawas we came to the conclusion that they belonged in a separate table with a compound key made up of the course number and the hole number. The task of creating views was a bit more difficult, I had to design and create new views from my imagination pooling my knowledge of Forums and also the game of golf. In this fashion I have in my opinion cobbled together possible views that would be needed on the website. I am fully aware that the views may not represent the views of the final product but for the function of this report they will suffice. 87

88 Criteria 2 SQL Implementation: Foreign keys & other attributes In this part of the design of the database I had to concentrate a lot, the idea of foreign keys is still a little beyond my understanding in the full use of the idea. So, a bit too much time may have been put into the creation of the foreign keys and other attributes. I will admit that to start with there were a few errors and correction needed to get the keys working correctly. Also, with the attributes of the tables I did make a few errors. Once the database was populated with data the errors appeared and I corrected all the ones which affected the product. It may turn out that is the database was to be used live on a website then more errors would appear. There are a couple of instances where composite keys are used, using a primary key from one table to link to the second table with an extra column to create the full composite key. The attributes of the column and keys have been designed to accommodate the expansion of the website over time. Giving enough space for the volume of entries I anticipate there will be entered into the database Criteria 2 SQL Implementation: Data constraints & Relationships Throughout the database there has been the need for various data constraints, I have tried my best to ensure that all scenarios have been covered, but I realise that with this database being the first I have created on SQL server I may have made some errors and forgotten to create constraints for certain information. With reference to the relationships in the database, I have had experience of creating entity relationship diagrams, and the correct way to link tables, so to this extent I believe that the relationships in this database have been created to make the database work efficiently Criteria 2 & 3 SQL Implementation & Test data The test data in the database took the longest to create. I have tried to ensure that there is an adequate volume of test date to enable the testing of the data relationships of the database. One thing I have not produced enough of is extra data to test the constraints of the system. This will be something I will rectify when I work on the final project for the course Criteria 3 SQL Implementation SQL DDL and DML statements based on data model In this report I have used SQL script to show my understanding of DDL and DML statements which also show the possible uses of script to show the kind of information users of the website and database would require. I also know that I still have a limited understanding of SQL script, however with more practice and time I feel I will become more confident and proficient with the syntax needed in the script. All the sub criteria have been demonstrated without any exception, which I am very pleased with. 88

89 Criteria 4 SQL: Show understanding of Additional or Advance Features Sub Sections to come from ICA feedback sheet The advanced features of SQL were a little taxing on me. I had to research a little deeper to the connection of the database to other Microsoft programs. Once the connections were successful I felt great satisfaction. This also opened up better possibilities for the used of databases in storing information for use on websites and also for the creation of user interfaces using MS Access CRITICAL REVIEW of ICA ICA GOALS The main goal was to create a professional document outlining my new knowledge and understanding of SQL Server database, and also to create a database from scratch utilising data models I created from a previous module. In that respect I feel I have managed to reach those goals. The only reservation I have is that on my one fault, I have been very relaxed in attitude in the time spent creating the database. The database closely represents the initial scenario and data models, and the report itself looks professionally created ICA ACHIEVEMENTS I have great pride in the fact I have managed to achieve all the criteria set out in the ICA requirements. Also I have gained new and useful knowledge about creating databases from data models, the SQL script to design the table and attributes and the script to manipulate the data within those tables. Also I am proud of my commitment to succeed; I possibly wasted too much time on solving certain problems with the database. For example; with the constraints syntax for the Holes table. It took three days of problem solving and searching for solutions online and in the help pages on Mr Nawas homepage before I found the correct answers ICA NON ACHIEVEMENTS The non achievements of the ICA are the lack of time to complete every single piece of data to insert and test the database fully. In addition the webpage link to the database is the connection only. As, I have not had time to completely design the look or the format of the website to insert the data fields, and tables into. Overall I believe that with more time a fuller report and product could have been achieved ICA EVALUATION In summary I believe that the final product of the ICA covers all the pass and merit criteria. The look of the report is professional and the lay out is of good design. There has been a lot of thought put into the design of the database. All tables in the original scenario have been replicated their specification, with the addition of the extra tables needed to take into consideration the removal of the many to many relationships, replaced by a joining table of consisting of the Primary keys of the connected tables as it s compound primary key ICA REFLECTION In reflection, I would like to have the chance to redo the ICA and make a start to the solution earlier in the time frame. This would have lead to a deeper amount of detail both in the database relationships, tables, and columns; and the diversity of evidence placed in the report. I would even have liked to attempt to create a video tutorial on the SQL database. 89

90 5.4. CRITICAL REVIEW of PRODUCT DATABASE GOALS The goals of the database were to mirror the design in the original data model which, was designed in a previous module. To create tables and attributes which will hold and manipulate data, and uphold the integrity of the data by the use of correctly applied relationships. Within the tables some of the attributes needed to have constraints applied. The test data used in the database has been created to test the integrity of the database and to test the running of query scripts. Other false data scripts have been created also to test the constraints to ensure that they work correctly. Connection to external software has been tested by connecting MS Access, VisualBasic.net to the database using links DATABASE ACHIEVEMENTS CURRENT SYSTEM STATE In its current state, the database can store and retrieve data relating to golfers and their handicaps, and forum FAQ s and Answers. The tables are linked correctly using relationships via the primary and foreign keys. For the user views, inner and cross joins have been created to query scripts will provide accurate and dependable results. The constraints in place on several tables work in their intended ways, by implementing default values and validating new data inserted into the database. The test data used in the database works perfectly to show valid and invalid entry of information into the database. Overall the current state is fit for being placed in a live situation without problem DATABASE NON ACHIEVEMENTS INCOMPLETE SYSTEM STATE Parts of the database which are incomplete are; within tables there will probably need to be some revision to adapt to the needs of actual users. Also to fully test the connection to Access and VisualBasic.Net user interfaces and web interfaces need to be designed and created. Repetition constraints need to be written to remove the possibility of ambiguous data being entered into multiple tables when the information held should be equal DATABASE FUTURE ENHANCEMENTS Further enhancements to the data base would include; the creation of user interface in both application based software and online websites. The expansion of the attributes of the tables to allow the holding of more relevant data, base on scenario testing in a live environment using feedback from users of the database system. The writing of stored queries to calculate output for the processes outlined in the system data model which, the database was created from DATABASE EVALUATION On the whole the database is a true representation of the data model. Most tables, attributes, constraints, and relationships are well designed. For a person with limited knowledge in the design and creation of databases through SQL server the product looks and works as expected. A little more tweaking is needed and in time a full live product would be available DATABASE REFLECTION 90