Risk assessment is basically a 5 step process as follows: 1. Look for the hazards associated with the work activities 2. Decide who might be harmed 3. Evaluate the risks and decide on the controls 4. Record the findings and implement them 5. Review your assessment and update if necessary The current system involves the identification of hazards associated with a particular activity, e.g. a field-trip to the Giant’s Causeway). The University has drawn up a list of potential hazards (which can be added to) and once the hazards have been identified the risk of each is graded. Staff who have been appointed as assessors for a particular area are typically members of a particular School which is itself part of a Faculty within the University. I was thinking of having 1 table with these values Assessor,Manager,PeopleAffected,NumberAffected,ActivityFreq,Faulty,Campus,Review,Tasks,Hazards,Controls,RiskRating,Actionbywhom,Actionbywhen,Assessorcomments,Managercomments then try and go through the 3 steps to third normal form so i want help to normalise it.can you help and how much please?
Hello, Looking at your query, your concern is to maintain the security and performance. Well these two things are totally depends on how you design your database, its tables and their structure, schema. Indexing, Optimization and Normalization are the techniques which plays major role in database performance. In fact there are the only techniques which needs to consider to maintain performance. Regarding security, following are some of the tips I can suggest you : 1) Use long names of database user 2) Use strong password and keep it secrete, a strong password is a combination of more that 14 characters containing alphabets, digits, special characters (like @ # $ % ^ etc.), 4) Password should not contain user name, should not contain anything like your own name, surname, birth date, phone number, motor cycle number etc. 5) Do not use plain text login details of database in web site configurations. Some users add database login details in database connection string say in web.config of asp.net web application which is harmful. 6) Do not use default mssql port 1433, to tighten the security change default port and reset it to something which is hard to guess. You can use port in connection string as well. 7) Disable remote connections of database. You can keep it enabled for local connections only, in this case you can use database host as localhost in connection string instead of IP address. When you disable remote connections then it reduce your risk upto 50 % 8) Do not give unnecessary permissions to users over database. 9) keep changing password periodically 10) use server side scripting hope this helps you let me know if you have any queries or doubts regarding this