Skip to main content

Some Database questions

Normalization is a set of rules used for the design of database tables and table are meant to be connected through relation ship. This set of rules are know as normalization. Normalization will avoid the repetitive entries, reduces the storage space, will avoid the need to restructure the table to accommodate new data. By doing the normalization you can increase the speed and flexibility of queries, summaries etc.

Data must be broken into the smallest unit as possible and should not contain any repetitive group of fields.

ID      Name                 Pet1   Pet2     Hours  Days  TotalHours/Week
1       Adarsh Soman    Cat    Cat2      5         5        25

Here name can be broken as first name and last name and pet repeating. So based on the first normal form the table will become as

ID      First Name      LastName  Pet    Hours  Days  TotalHours/Week
1        Adarsh           Soman       Cat       5         5        25


Each non key field should be fact about the field in the primary key. Here pet can be moved into a different table



ID      First Name      LastName  PetID    Hours  Days  TotalHours/Week
1        Adarsh           Soman       1           5         5        25


PetID  PetName
1         Cat
2         Dog

A non-key field should not depend upon the other non key field. Here 
In the above table TotalHours/Week is calculated by multiplying hours into days.(total=hours*days). So based on the third normal form we can remove it.





ID      First Name      LastName  PetID    Hours  Days  
1        Adarsh           Soman       1           5         5        


Process of putting one fact in numerous place is know as denormalization and we can tell its a vice versa of normalisation. By doing it we can increase the performance (increasing redundancy as well)

Comments

Popular posts from this blog

How to write secure mvc application using encrypting URL

There are lots ways available to write the secure Mvc application. In my experience I came across lots of secure application in public facing. I want to tell about some of the mechanism I followed. 1- encrypting the URL Parameters and preserving id's encrypted on the client side 1- I always make sure if I pass Id or any sensitive data into the view always make sure it's encrypted. By doing so make sure if we forced to use HTML.hidden or HTML.hidden for have the encrypted values, in action link if I pass any parameters from the client side (eg:- edit or create or navigating between different actions we can make sure that all the values are encrypted) During the design of the actions results if it's http get I usually encrypt the sensitive data [httpget] Public actionresult display() { TestModel testModel=new TestModel(); testModel.id= encrypt(id); Return View(testModel); } [httppost] Public ActionResult Display(string id) { Guid d_id= new Guid(decrypt(id));

Single page application (SPA) using ext.js

what is spa? Single page application are applications that fit in one page with rich and fluid user experiences like a desktop based applications. Why is SPA? All web based elements (html, CSS,javascript) are downloaded from the server on single page load and avoid the continuous page post back. i can explain what this mean. Suppose your web application is made of certain flow and it consists of 5 different pages. Each page need to get data from the user and save before moving to the next page. So when we navigate from one page to other it need to make a round trip to server to store the data in one page and get the data for the next page to display. but in spa we can avoid the continuous post backs. The whole page will not post back any time other than the first load. But it communicate to the server dynamically behind the scene and can achieve the same functionality. Spa using ext.js designing a SPA using ext.js is a challenging task if you are unaware about the ext.js

#saynotointerview for recruitment process

I recently went for a training that consists of employees from multinational corporations. During the brainstorming sessions, one fellow gentleman started speaking about firing his colleague. This guy is actually a senior manager and he interviewed the departed. He was blaming the unfortunate guy told he knows all the job description and he was smart during the interview. So they selected him for the job. But in the job, he never raised to his potential and they sacked him. The senior manager was claiming in the brainstorming session the decision was correct. But lots of people in training disagreed with that. Majority people told the recruitment or interview process in the company flawed to test that lad's knowledge. I strongly believe this might not be a one of the situation in recruitment? How many of you came across similar experience in your professional career? Do you believe the things we put in the job description are the exact things the potential employees will be do