Home
Search results “Foreign key index oracle”
Oracle - SQL - Foreign Key Constraint
 
06:15
Oracle - SQL - Foreign Key Constraint Watch more Videos at https://www.tutorialspoint.com/videotutorials/index.htm Lecture By: Mr. Anadi Sharma, Tutorials Point India Private Limited.
Oracle SQL Tutorial 21 - How to Create / Drop Indexes
 
03:58
In the last video, we wrote up the SQL to create three tables: CREATE TABLE users( user_id NUMBER, username VARCHAR2(50 CHAR) UNIQUE, CONSTRAINT users_pk PRIMARY KEY (user_id) ); CREATE TABLE projects( project_id NUMBER, Project_name VARCHAR2(50 CHAR) UNIQUE, creator VARCHAR2(50 CHAR) NOT NULL, CONSTRAINT projects_pk PRIMARY KEY (project_id), CONSTRAINT projects_users_fk FOREIGN KEY (creator) REFERENCES users (username) ON DELETE CASCADE ); CREATE TABLE project_users( project_id NUMBER NOT NULL REFERENCES projects (project_id) ON DELETE CASCADE, user_id NUMBER NOT NULL REFERENCES users (user_id) ON DELETE CASCADE, CONSTRAINT project_users_pk PRIMARY KEY (project_id, user_id) ); I'm going to increase the size of the users table a bit by adding a first and last name column. CREATE TABLE users( user_id NUMBER, username VARCHAR2(50 CHAR) UNIQUE, first_name VARCHAR2(50 CHAR), last_name VARCHAR2 (50 CHAR), CONSTRAINT users_pk PRIMARY KEY (user_id) ); But before we finish this design, we should consider indexing certain columns. What columns should we index? Well, as a reminder, the columns that are indexed by default are columns with the UNIQUE constraint, and those that are labeled as primary keys. Columns that are not indexed but often should be are those labeled as a foreign key. The column that jumps out the most to me is the creator column of the project table. It's the only foreign key that is not part of some index. Let's fix this by creating our first index. The way we do that is with the CREATE INDEX command. CREATE INDEX projects_creator_ix ON projects (creator) What naming convention are we following for the index? We are naming it by the table name, followed by an underscore, followed by the column, followed by an underscore, followed by an ix (for index). In this situation it does not apply, but if our foreign key column is labeled as UNIQUE, we can add the UNIQUE keyword like this: CREATE UNIQUE INDEX projects_creator_ix ON projects (creator) Now if you want to get rid of an INDEX, you can use this command: DROP INDEX projects_creator_ix Now, if we want to select data from the user table and the project table we can do that much faster. That's because the foreign key and column it references are both indexed and those are the columns we would do the join on. We will discuss how to do joins in a future video. So what are some potential problems with this database design? Overall, it is pretty good. With this design though we need to make sure there is no way for someone to update a user's username. In the next video we are going to discuss why. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Support me on Patreon! http://www.patreon.com/calebcurry Subscribe to my newsletter: http://bit.ly/JoinCCNewsletter Donate!: http://bit.ly/DonateCTVM2. ~~~~~~~~~~~~~~~Additional Links~~~~~~~~~~~~~~~ More content: http://CalebCurry.com Facebook: http://www.facebook.com/CalebTheVideoMaker Google+: https://plus.google.com/+CalebTheVideoMaker2 Twitter: http://twitter.com/calebCurry Amazing Web Hosting - http://bit.ly/ccbluehost (The best web hosting for a cheap price!)
Views: 9396 Caleb Curry
Foreign Key | Database Management System
 
06:29
To ask your doubts on this topic and much more, click on this Direct Link: http://www.techtud.com/video-lecture/lecture-foreign-key IMPORTANT LINKS: 1) Official Website: http://www.techtud.com/ 2) Virtual GATE: http://virtualgate.in/login/index.php Both of the above mentioned platforms are COMPLETELY FREE, so feel free to Explore, Learn, Practice & Share! Our Social Media Links: Facebook Page: https://www.facebook.com/techtuduniversity Facebook Group: https://www.facebook.com/groups/virtualgate Google+ Page: https://plus.google.com/+techtud/posts Last but not the least, SUBSCRIBE our YouTube channel to stay updated about the regularly uploaded new videos.
Views: 272221 Techtud
Oracle SQL Tutorial 20 - How to Create Composite Primary Keys
 
07:02
This video is going to be a tutorial on how to create composite and compound keys. The difference between a composite and compound key is that a composite key can consist of any columns while a compound key has to consist of columns that are all keys themselves. We will be working with a compound key because we are going to be using the an intermediary table that has two foreign keys. The combination of both of the keys have to be unique. First, if we have any other CREATE TABLE commands, we are going to comment those out. We will space out the CREATE TABLE to have each column on a line, then we will add constraints as needed. CREATE TABLE project_users( project_id, user_id ) Now, let's add the data types: CREATE TABLE project_users( project_id NUMBER, user_id NUMBER } Now, what about some column attributes? I'm going to make both of the columns NOT NULL because we always want the rows to have a user and a project: CREATE TABLE project_users( project_id NUMBER NOT NULL, user_id NUMBER NOT NULL } Now, let's add the foreign key constraints. Now, what do we name these? We are going to add a primary key that covers both of these columns, so I'm going to be a sinner and not give these constraints names: CREATE TABLE project_users( project_id NUMBER NOT NULL REFERENCES projects (project_id), user_id NUMBER NOT NULL REFFERENCES users (user_id) ) Now, the way we have it now is that if we delete a project in the project table, and there are any rows in the project_users table, it will throw an error and prevent deletion. I would prefer for it to also delete any project members. That would make sense because if you delete a project we want it to delete the associate between that project and certain users. The same goes for if we delete a user, we want their association with a certain project to be deleted. To do this, we need to add the ON DELETE command: CREATE TABLE project_users( project_id NUMBER NOT NULL REFERENCES projects (project_id) ON DELETE CASCADE, user_id NUMBER NOT NULL REFERENCES users (user_id) ON DELETE CASCADE, ) Finally, let's learn how to create a compound or composite key. literally, the only difference is that you put a comma and add the second table inside of the parenthesis. CREATE TABLE project_users( project_id NUMBER NOT NULL REFERENCES projects (project_id) ON DELETE CASCADE, user_id NUMBER NOT NULL REFERENCES users (user_id) ON DELETE CASCADE, CONSTRAINT project_users_pk PRIMARY KEY (project_id, user_id) ) Now, the combination of project_id and user_id cannot be null, is always unique, and has an index. The only thing we should do now is add a few indexes. We aren't done yet...In the next video we are going to figure out what columns would benefit from indexes and we'll add them to it. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ HELP ME! http://www.patreon.com/calebcurry Subscribe to my newsletter: http://bit.ly/JoinCCNewsletter Donate!: http://bit.ly/DonateCTVM2. ~~~~~~~~~~~~~~~Additional Links~~~~~~~~~~~~~~~ More content: http://CalebCurry.com Facebook: http://www.facebook.com/CalebTheVideoMaker Google+: https://plus.google.com/+CalebTheVideoMaker2 Twitter: http://twitter.com/calebCurry Amazing Web Hosting - http://bit.ly/ccbluehost (The best web hosting for a cheap price!)
Views: 11911 Caleb Curry
Oracle SQL Tutorial 6 - Relationships and Primary and Foreign Keys - Database Design Primer 3
 
29:40
HAPPY VALENTINES DAY!!! Let's talk relationships.. This is the 6th video in your Oracle Database series. We are discussing database relationships which are a key feature of relational database management systems. We first discussed entities and attributes. I talked about how each entity is assigned a table and each attribute is a column within a table. We moved on to the three kinds of relationships. The first was one-to-one. This describes an entity and an attribute. A piece of data that is exclusive to an entity is, by definition, an attribute of that entity. This is stored in one table with the attribute being a column within this table. The second relationship is one-to-many. This relationship is between two entities. The way we properly store this in a database is using a foreign key in the child table. Remember, the child table is the entity on the many side of the one-to-many relationship. Every row within the child table will have a value for the foreign key that references a primary key in the parent table. This assumes that the foreign key field is not optional (NOT NULL). If the foreign key is optional, than a reference is not required but any reference must be valid. The third kind of relationship is a many-to-many relationship. In this situation, we need 3 tables. The many-to-many relationship is broken up into two one-to-many relationships. The intermediary table will associate each entity from one table with the appropriate entities in the other table. There is debate as to whether this table needs a primary key. This is because you can intact use the combination of two foreign keys as a primary key. This works because we will never have two duplicate rows within the intermediary table and the two foreign keys work as a compound key because of this. We finally discussed primary keys and foreign keys. Primary keys are used to keep each row inside of a table unique. If this key is a computer generated number it is known as a surrogate key, otherwise it is known as a natural key. Natural keys have real world meaning. For example, a social security number may work, or an email address (in some situations), etc. Whichever type of key you choose is solely up to you and/or the company you may be working for. HELP ME! http://www.patreon.com/calebcurry Subscribe to my newsletter: http://bit.ly/JoinCCNewsletter Donate!: http://bit.ly/DonateCTVM2. ~~~~~~~~~~~~~~~Additional Links~~~~~~~~~~~~~~~ More content: http://CalebCurry.com Facebook: http://www.facebook.com/CalebTheVideoMaker Google+: https://plus.google.com/+CalebTheVideoMaker2 Twitter: http://Twitter.com/calebCurry Amazing Web Hosting - http://bit.ly/ccbluehost (The best web hosting for a cheap price!)
Views: 47190 Caleb Curry
45. Primary Key and Foreign Key Constraints in PL/SQL Oracle
 
12:36
In this video you will learn about Primary Key and Foreign Key Constraints in PL/SQL Oracle. For Support =========== Email: [email protected] Contact Form: http://www.learninhindi.com/home/contact Our Social Media ================ Facebook: https://www.facebook.com/LearnInHindi Twitter: https://twitter.com/LearnInHindi For Training & Videos ===================== For more videos and articles visit: http://www.learninhindi.com Free Java Programming In Hindi Course ===================================== https://www.youtube.com/playlist?list=PLOZ3jentlCDAwwhMyoLISrxkXTADGp7PH Free Oracle PL/SQL Programming In Hindi Course ============================================== https://www.youtube.com/playlist?list=PLB5DA82419C2D99B6 Free C Programming In Hindi Course ================================== https://www.youtube.com/playlist?list=PLOZ3jentlCDAxKpBLMWogxSdy6BZcsAJq Trips & Tricks Channel ====================== https://www.youtube.com/channel/UCGmLfkuCo-3lHHJXRJ9HUMw Programming in Hindi Channel ============================ https://www.youtube.com/channel/UCudElIDgwNrybeAvXIy1HZQ
Views: 11677 ITORIAN
Oracle SQL Tutorial 17 - Designing Our Foreign Keys
 
07:47
We are going to continue working with the users table that we've started with, but we are going to add a few tables. Imagine a system where you can create projects. And users can be added to these projects. So this could be some kind of productivity app or a project management solution, think of JIRA. We are going to start with three tables. The first table is going to be a users table that contains all of the information about each user's account. We are then going to have a table that is called projects. Each project will have data about the project and a foreign key that is the creator of the project. This is a situation where the database design depends a lot on the business rules and requirements of the application. Is it appropriate to have only one creator, or can it have multiple creators? We are going to design it with only one creator per project to increase simplicity. The third table is going to be used to record what users are part of certain projects. This situation is a many to many relationship because we've decided that one user can be a part of multiple projects and an individual project can have multiple members working on it. Because this is a many to many relationship, it calls for an intermediary table, project_users. First, we will draw out the user table. We will have a user_id, username, first_name, and last_name. Now, this is our parent table, because it has no foreign keys. Now, this is our parent table, because it has no foreign keys. Other tables are going to be referencing this table, so they would be the children. The project table will have a project_id, title, description, and creator. The column that needs to be a foreign key is the creator. Let's move on to the next table and we'll get back to the foreign key of the project table. The other table was project_users. Knowing that this is an intermediary table, immediately we know that the first two columns are going to be foreign keys to the each of the other tables. Now, let's ask the important questions about the foreign keys. Let's first start with the project table's user column. The first thing we need to ask is what column does it need to reference? Remember, the only options are the columns that are UNIQUE. Our candidates are user_id and username. For now, let's go with username as it makes things easier to work with. Once we go into learning about joins, we will talk about joining things by ID. Different people do it different ways, with the majority using only ID columns for primary and foreign keys, but it's important to be familiar with different ways of doing things. The important thing to remember is that keys should never change, so if we should only reference the username if a user's username will never change. Should the foreign key be labeled UNIQUE? If yes, it means that a user can only create one project. I vote no. Should the foreign key be labeled NOT NULL? If not, it means that a project can exist without a creator. I vote no. Moving on to the next table, I think I'll have the columns reference the project's id and user's id, so we can get some experience referencing surrogate keys. We can apply to these foreign keys the same questions we asked about the other foreign key, and I would encourage you to do so and really think about why. But I can tell you that we are not going to want them to be NOT NULL, but not UNIQUE. Now that we have a pretty decent database design, we can proceed with creating our database. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ HELP ME! http://www.patreon.com/calebcurry Subscribe to my newsletter: http://bit.ly/JoinCCNewsletter Donate!: http://bit.ly/DonateCTVM2. ~~~~~~~~~~~~~~~Additional Links~~~~~~~~~~~~~~~ More content: http://CalebCurry.com Facebook: http://www.facebook.com/CalebTheVideoMaker Google+: https://plus.google.com/+CalebTheVideoMaker2 Twitter: http://twitter.com/calebCurry Amazing Web Hosting - http://bit.ly/ccbluehost (The best web hosting for a cheap price!)
Views: 10885 Caleb Curry
Primary key and Foreign Key in DBMS
 
06:11
Primary key vs Foreign key in DBMS. Key concepts in DBMS. (Candidate key, Primary Key, Foreign Key, Alternate Key, Super Key)
Views: 180435 Edu Therapy
Oracle - Foreign Keys
 
11:34
Oracle - Foreign Keys
Views: 3827 Chris Ostrowski
Oracle - SQL - Managing Constraints
 
06:01
Oracle - SQL - Managing Constraints Watch more Videos at https://www.tutorialspoint.com/videotutorials/index.htm Lecture By: Mr. Anadi Sharma, Tutorials Point India Private Limited.
SQL Server 28 - Composite Primary Key
 
04:55
The previous video had these tables: CREATE TABLE Species( ID INT PRIMARY KEY IDENTITY, Species VARCHAR(50) NOT NULL UNIQUE, FriendlyName VARCHAR(50) NOT NULL ); CREATE TABLE Animals( ID INT PRIMARY KEY IDENTITY, Name VARCHAR(50) NOT NULL, Species INT NOT NULL REFERENCES Species(ID), ContactEmail VARCHAR(50) NOT NULL UNIQUE ); These column attributes are all examples of constraints. To be more specific, they are known as column-level constraints. Sometimes you need to create what is known as a table-level constraint. To illustrate this, we are going to create a new table that shows this in action. Remember that we are trying to create an animal dating site. A specific animal can create an account on our website and say what kind of species he or she is interested in. One specific animal can be interested in multiple species and an individual species can be liked by many animals. Therefore, it is a many to many relationship. We already have a Species table and an Animals table, so we need an intermediary table to associate animals with species: CREATE TABLE Interests( AnimalID INT NOT NULL REFERENCES Animals(ID), SpeciesID INT NOT NULL REFERENCES Species(ID) ); But now, we want to create a composite primary key, the combination of both columns. A column-level attribute is not capable of doing this because it is associated with just one column. Let's create a table-level constraint. To do this we add the constraint as if it's another column: CREATE TABLE Interests( AnimalID INT NOT NULL REFERENCES Animals(ID), SpeciesID INT NOT NULL REFERENCES Species(ID), PRIMARY KEY (AnimalID, SpeciesID) ); The downside here is that we cannot create a foreign key to reference this composite key. If for some reason we have to be able to reference an individual interest in another table, we would create an ID column and put a UNIQUE constraint on the combination of AnimalID and SpeciesID. Then we could reference an individual ID. Now, in SSMS, inside of our tables key folder you can find the composite key. Unfortunately, SSMS defaults to a pretty ugly name for our primary key constraint. Fortunately, we can actually give names to our constraints. That's what we will be doing in the next video. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Support me! http://www.patreon.com/calebcurry Subscribe to my newsletter: http://bit.ly/JoinCCNewsletter Donate!: http://bit.ly/DonateCTVM2. ~~~~~~~~~~~~~~~Additional Links~~~~~~~~~~~~~~~ More content: http://CalebCurry.com Facebook: http://www.facebook.com/CalebTheVideoMaker Google+: https://plus.google.com/+CalebTheVideoMaker2 Twitter: http://twitter.com/calebCurry Amazing Web Hosting - http://bit.ly/ccbluehost (The best web hosting for a cheap price!)
Views: 11029 Caleb Curry
Database Design 21 - Primary Key Index
 
06:28
Donate!: http://bit.ly/DonateCTVM2. Primary key will automatically create an index used for database optimization! More content: http://CalebCurry.com Courses for Download: http://www.udemy.com/u/calebcurry/ Facebook: http://www.facebook.com/CalebTheVideoMaker Google+: https://plus.google.com/+CalebTheVideoMaker2 Twitter: http://Twitter.com/calebCurry Subscribe (it's free!): http://bit.ly/PqPyvH Amazing Web Hosting - http://bit.ly/ccbluehost (The best web hosting for a cheap price!)
Views: 18178 Caleb Curry
Learn Oracle SQL Developer in 10 minutes - Data Dictionary - DDL - Part 1/2
 
13:29
Refer Complete Tutorial : http://haneefputtur.com/create-manage-oracle-database-using-oracle-sql-developer-gui.html Create Oracle Database Tables Using GUI SQL developer Tools Tasks: • Create Orale tables using Oracle SQL Developer Creating Oracle Tables . 1. Oracle database required: DNS Name : xxxxxxxxx User Name: haneef Password : xxxxxxxxxxxxxxx Service Name : Haneef 2. Software Required : Oracle SQL Developer ( this requires JDK ) Link to Download : http://www.oracle.com/technetwork/developer-tools/sql-developer/downloads/index.html http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html Create two tables. 1. Employee 2. Department Employee Table : • Employee ID ( Primary key) • Employee Name • Employee Department • Employee Salary Department Table: • Department ID (Primary key) • Department Name • Department Head Create Foreign Key For Employee Department to get ID from Department Table. Create DDL and Execute them.
Views: 27848 Mahammad Haneef
What is the Difference between Primary Key and Unique Key - Database Tutorial 14
 
04:51
Database Tutorial. This video is about Database Fundamentals. I hope this series of videos can help those who want to be Database Professionals. I will cover various database technologies including Oracle Database, Microsoft SQL Server database and Sybase. Video: What is the Difference between Primary Key and Unique Key (Video 14 in the Database Tutorial Series) (Common for Oracle/Microsft SQL Server/Sybase /MySQL)
Views: 35446 Sam Dhanasekaran
How to create Foreign Key Constraint on Multiple Columns in SQL Server - SQL Server Tutorial Part 67
 
10:12
SQL Server / TSQL Tutorial Scenario: You are working as SQL Server developer, you need to create a table dbo.Customer with composite primary key by using columns FName and SSN. One you are done with creating primary key in dbo.Customer table, you need to create second table dbo.Orders and create foreign key constraint by using Primary Key columns. Link to scripts used in SQL Server / TSQL Tutorial Video http://www.techbrothersit.com/2016/04/how-to-create-foreign-key-constraint-on.html Check out our website for Different SQL Server, MSBI tutorials and interview questions such as SQL Server Reporting Services(SSRS) Tutorial SQL Server Integration Services(SSIS) Tutorial SQL Server DBA Tutorial SQL Server / TSQL Tutorial ( Beginner to Advance) http://www.techbrothersit.com/
Views: 5254 TechBrothersIT
Primary Key & Foreign Key Implementation: MySQL
 
06:13
http://technotip.com/2931/primary-key-foreign-key-implementation-mysql/ Implementation of Primary Key and Foreign Key, using MySQL Practical approach and the benefits of using Primary and Foreign key concept in a relational database design.
Views: 240561 Satish B
SQL: Foreign Key Creation
 
05:55
In this tutorial, you'll learn how to create a foreign key column ....
Views: 45780 radhikaravikumar
SQL Foreign Key Constraints
 
07:25
Jamie King of Neumont University showing what are and how to add foreign key constraints.
Views: 57547 Jamie King
Creating Primary and Foreign Keys in SQL Server 2012
 
18:22
Dr. Soper shows how to create simple and composite primary keys and foreign key relationships in a SQL Server database using SQL Server Management Studio. Several different methods of creating keys and establishing relationships between tables are demonstrated.
Views: 423906 Dr. Daniel Soper
Oracle Tutorial || Oracle| Sql Constraints Part - 1 by basha
 
33:21
DURGASOFT is INDIA's No.1 Software Training Center offers online training on various technologies like JAVA, .NET , ANDROID,HADOOP,TESTING TOOLS ,ADF,INFORMATICA,TABLEAU,IPHONE,OBIEE,ANJULAR JS, SAP... courses from Hyderabad & Bangalore -India with Real Time Experts. Mail us your requirements to [email protected] so that our Supporting Team will arrange Demo Sessions. Ph:Call +91-8885252627,+91-7207212428,+91-7207212427,+91-8096969696. http://durgasoft.com http://durgasoftonlinetraining.com https://www.facebook.com/durgasoftware http://durgajobs.com https://www.facebook.com/durgajobsinfo......
PRIMARY KEY CONSTRAINT IN ORACLE SQL WITH EXAMPLE
 
12:43
This is a free video tutorial by Kishan mashru on primary key constraint in oracle SQL, the video firstly explains what primary key constraint is and how it can be used along with its various limitations, then the video gives perfect examples to understand how to create a primary key at the column level i.e inline declaration, or at the table level i.e out of line declaration. The video gives the demonstration on ALTER TABLE ADD CONSTRAINT and ALTER TABLE DROP CONSTRAINT statements also.
Views: 730 Kishan Mashru
SQL Constraints - NOT NULL , UNIQUE , PRIMARY KEY , FOREIGN KEY , CHECK , INDEX , default
 
10:17
SQL is a standard Structured query language for storing, manipulating and retrieving data in databases. NOT NULL , UNIQUE , PRIMARY KEY , FOREIGN KEY , CHECK , INDEX , default 1) NOT NULL - Ensures that a column cannot have a NULL value 2) UNIQUE - Ensures that all values in a column are different 3) PRIMARY KEY - A combination of a NOT NULL and UNIQUE. Uniquely identifies each row in a table 4) FOREIGN KEY - Uniquely identifies a row/record in another table. The table containing the foreign key is called the child table, and the table containing the candidate key is called the referenced or parent table. prevents invalid data and destroy links between tables. 5) CHECK - Ensures that all values in a column satisfies a specific condition 6) DEFAULT - Sets a default value for a column when no value is specified 7) INDEX - Used to create and retrieve data from the database very quickly.
Views: 40 R K
Oracle Database | Bangla Tutorials 22 :: Constraint Foreign Key
 
03:52
www.facebook.com/oracle.shohag Email : [email protected] Website : www.oraclebangla.com Topics : Constraint Foreign Key
Views: 1168 Oracle Bangla
Oracle SQL Tuning with Foreign Key Constraints
 
03:02
Learn how to tune SQL with Constraints! In this lesson (2 of 5), OCM John Watson demonstrates how to improve query performance by adding foreign key constraints. See all lessons, free at http://www.skillbuilders.com/oracle-database-sql-tuning-with-constraints.
Views: 439 SkillBuilders
Laravel 5.5 lesson - 5  Migrations -Part 5  Primary key and Foreign key relationship
 
06:52
In this video I have shown an demo how to create foreign key relationship between two tables (customers and orders table) using migrations.
Views: 4970 Ruby
How to Drop Foreign Key Constraint in SQL Server Database - SQL Server / TSQL Tutorial Part 75
 
04:17
SQL Server / T-SQL Tutorial Scenario: You are working as SQL Server developer and you need to prepare the script to drop the Foreign Key Constraint which was created on dbo.Orders table. Link to scripts used in SQL Server / TSQL Tutorial Video http://www.techbrothersit.com/2016/04/how-to-drop-foreign-key-constraint-in.html Check out our website for Different SQL Server, MSBI tutorials and interview questions such as SQL Server Reporting Services(SSRS) Tutorial SQL Server Integration Services(SSIS) Tutorial SQL Server DBA Tutorial SQL Server / TSQL Tutorial ( Beginner to Advance) http://www.techbrothersit.com/
Views: 4152 TechBrothersIT
Constraints Part-2 NOT NULL , UNIQUE , PRIMARY KEY , FOREIGN KEY , CHECK , INDEX , default
 
13:22
SQL is a standard Structured query language for storing, manipulating and retrieving data in databases. NOT NULL , UNIQUE , PRIMARY KEY , FOREIGN KEY , CHECK , INDEX , default 1) NOT NULL - Ensures that a column cannot have a NULL value 2) UNIQUE - Ensures that all values in a column are different 3) PRIMARY KEY - A combination of a NOT NULL and UNIQUE. Uniquely identifies each row in a table 4) FOREIGN KEY - Uniquely identifies a row/record in another table. The table containing the foreign key is called the child table, and the table containing the candidate key is called the referenced or parent table. prevents invalid data and destroy links between tables. 5) CHECK - Ensures that all values in a column satisfies a specific condition 6) DEFAULT - Sets a default value for a column when no value is specified 7) INDEX - Used to create and retrieve data from the database very quickly.
Views: 24 R K
07 - Curso de Oracle 10g - Foreign key
 
09:39
Curso Oracle SQL Essentials http://bit.ly/1N3upVn Curso Oracle SQL Expert - Certificação 1Z0-047 http://bit.ly/1G4rKWG Curso Oracle Aprendendo SQL - Preparatório exames 1Z0-051/1Z0-061 http://bit.ly/1eqDlsr Neste Curso de Oracle 10g será demonstrado todo passo a passo desde a istalação até administração e programação em PLSql. No Curso de Oracle 10g você será direcionado passo a passo durante o aprendizado com ótima qualidade do conteúdo disponibilizado. Este curso é oferecido gratuitamente aqui porém caso tenha interesse em se aprofundar e aprender o oracle a fundo praparando para certificação acesse os links acima. https://youtu.be/tcjwZYKDKW4 Tags: oracle cursos gratuitos curso de oracle banco de dados
Views: 3570 Cursos Interativos
SQL Server 34 - How to Create and Drop Indexes
 
05:15
Creating indexes is a very easy task, but before you go creating indexes on everything, you need to know that some columns are indexed by default. Specifically, any column that is labeled as the PRIMARY KEY or UNIQUE are indexed by default. That means that if you have a UNIQUE column, you do not need to worry about adding an INDEX to it. The columns that you will want to pay special attention to are any foreign keys or columns that you are going to use very frequently. We are going to create an index on our SpeciesID column in our Animals table. This is a foreign key that I'm likely going to use very frequently. CREATE INDEX IX_AnimalsSpecies ON Animals (SpeciesID); The syntax is very similar to CREATE TABLE in that you say CREATE INDEX followed by an index name. The IX_ is a prefix that is sometimes conventionally used to name indexes. Next, we have the table name, and then we have something to describe the column. That way if you see IX_AnimalsSpecies, you automatically know it is talking about an Index for the Animals table that is on the column dealing with the species. To get rid of this index, use this: DROP INDEX IX_AnimalsSpecies; Which is also very similar to how we drop a table. Now, you can also create an INDEX on multiple columns if you are going to use them together very often. The way you do that is just add another column after a comma inside of the () in the index columns. For example: CREATE INDEX IX_AnmialsContact ON Animals (Name, ContactEmail); One other thing I wanted to show you is that you can actually create a UNIQUE Index by adding the keyword in: CREATE UNIQUE INDEX IX_Species ON Species (Species); This should only be used if every value for a column is labeled unique…In fact, it forces every row to be unique. Remember though that if a column is labeled UNIQUE, it is indexed by default...So this is not needed in this situation. In the next video we will discuss in more detail whether you want to use the UNIQUE Constraint create a UNIQUE index. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Support me! http://www.patreon.com/calebcurry Subscribe to my newsletter: http://bit.ly/JoinCCNewsletter Donate!: http://bit.ly/DonateCTVM2. ~~~~~~~~~~~~~~~Additional Links~~~~~~~~~~~~~~~ More content: http://CalebCurry.com Facebook: http://www.facebook.com/CalebTheVideoMaker Google+: https://plus.google.com/+CalebTheVideoMaker2 Twitter: http://twitter.com/calebCurry Amazing Web Hosting - http://bit.ly/ccbluehost (The best web hosting for a cheap price!)
Views: 9394 Caleb Curry
SQL Primary Key and Foreign Key with real life examples
 
09:12
You Can Find the full course of 3 hours in a given link with 50% Coupon= https://goo.gl/g8SyVQ Learn SQL and Database Core Concepts: This SQL Tutorial will cover all Major SQL concepts from Scratch. SQL developers are earning higher salary in IT industry, but, its not about writing queries its about understanding and applying the right query at right time and this course will let you understand complex SQL Statements in an easy way . Moreover, This Course will teach you how to extract Data from Database and write complex queries to a database This course will focus on a wider scale by Covering Structure Query Language SQL concepts as a whole, whether Students work with MySQL, Microsoft SQL Server, Oracle Server, etc. Enroll Today! Lets start together. Jazeb Akram All Right Reserved https://www.Jazebakram.com https://twitter.com/jazebakram https://www.udemy.com/user/jazeb-akram/ https://goo.gl/g8SyVQ Coupon Code = 1YOUTUBE0
Views: 7610 Jazeb Akram
Oracle - SQL - Unique Constraint
 
07:50
Oracle - SQL - Unique Constraint Watch more Videos at https://www.tutorialspoint.com/videotutorials/index.htm Lecture By: Mr. Anadi Sharma, Tutorials Point India Private Limited.
CREATE TABLE WITH CONSTRAINTS - ORACLE - SQL
 
20:35
Create table , add constraints : primary key constraint, foreign key constraint, check constraint, unique constraint, specifying the table space for index, modifying table, dropping table Oracle 10g
Views: 9966 R.N.A. Creation
Primary (PK) and Foreign Key (FK) Relation on Table without Cascade Rules Part 1 | MSSQL Training
 
22:57
** For Online Training Registration: https://goo.gl/r6kJbB ? Call: +91-8179191999 💡Visit Our Website for Classroom Training: https://nareshit.in/sql-server-training/ 💡For Online Training: https://nareshit.com/course/sql-server-dba-online-training/ #sqlserver #server #programming #course #Tutorials #Training #Videos -------------------------- 💡 About NareshIT: "Naresh IT is having 14+ years of experience in software training industry and the best Software Training Institute for online training, classroom training, weekend training, corporate training of Hadoop, Salesforce, AWS, DevOps, Spark, Data Science, Python, Tableau, RPA , Java, C#.NET, ASP.NET, Oracle, Testing Tools, Silver light, Linq, SQL Server, Selenium, Android, iPhone, C Language, C++, PHP and Digital Marketing in USA, Hyderabad, Chennai and Vijayawada, Bangalore India which provides online training across all the locations -------------------------- 💡 Our Online Training Features: 🎈 Training with Real-Time Experts 🎈 Industry Specific Scenario’s 🎈 Flexible Timings 🎈 Soft Copy of Material 🎈 Share Videos of each and every session. -------------------------- 💡 Please write back to us at 📧 [email protected]/ 📧 [email protected] or Call us at the USA: ☎+1404-232-9879 or India: ☎ +918179191999 -------------------------- 💡 Check The Below Links ► For Course Reg: https://goo.gl/r6kJbB ► Subscribe to Our Channel: https://goo.gl/q9ozyG ► Circle us on G+: https://plus.google.com/+NareshIT ► Like us on Facebook: https://www.facebook.com/NareshIT ► Follow us on Twitter: https://twitter.com/nareshitek ► Follow us on Linkedin: https://goo.gl/CRBZ5F ► Follow us on Instagram: https://goo.gl/3UXYK3
Views: 7918 Naresh i Technologies
SelectTec | Aula Nº 31 | Continuação Foreign Key - Oracle SQL Developer
 
10:30
Syntax: ALTER TABLE table_name ADD CONSTRAINT constraint_name FOREIGN KEY (column1, column2, ... column_n) REFERENCES parent_table (column1, column2, ... column_n);
Views: 1515 SelectTec
Foreign Key in Oracle
 
07:00
Foreign Key in Oracle oracle foreign key WHAT IS A FOREIGN KEY IN ORACLE? 1)A foreign key is a use to make referential integrity in database. 2)Foreign key values in one table must also appear in another table also. 3)The referenced table is called the parent table. 4)Table with the foreign key is called the child table. 5)The foreign key generally reference a primary key in the parent table. CREATE TABLE DEPT --- parent table ( DEPT_ID NUMERIC(10) NOT NULL, EMP_ID NUMERIC(10) NOT NULL, CONSTRAINT DEP_PK PRIMARY KEY (DEPT_ID) ); CREATE TABLE EMPLOYEE -- child table ( EMP_ID NUMERIC(10) NOT NULL, NAME VARCHAR2(50) NOT NULL, CITY VARCHAR2(50), DEPT_NO NUMERIC(10), CONSTRAINT ID_PK PRIMARY KEY (EMP_ID), CONSTRAINT FK_DEP FOREIGN KEY (DEPT_NO) REFERENCES DEPT(DEPT_ID) ); #techquerypond https://techquerypond.wordpress.com https://twitter.com/techquerypond
Views: 473 Tech Query Pond
UNIQUE KEY CONSTRAINT IN ORACLE SQL WITH EXAMPLE
 
14:37
This is a free video tutorial by Kishan mashru on unique constraint in Oracle SQL, the video firstly explains what unique constraint is and how it can be used along with its various limitations, then the video gives perfect examples to understand how to create a unique key at the column level or inline, or at the table level i.e out of line. The video gives a demonstration on ALTER TABLE ADD CONSTRAINT and ALTER TABLE DROP CONSTRAINT statements also.
Views: 1104 Kishan Mashru
SQL Server 27 - How to Create FOREIGN KEY Constraints
 
04:25
In the previous video we set up an entire table. The problem with this table is that the species column is just plain text. The problem with this is that there is a higher probability of incorrect data and if we have tons of animals in here there will be a lot of redundant information. The solution to this is to change this species to a foreign key to another table. Remember that when you create a foreign key it is a child to a parent. The thing you need to know is that the parent has to exist before the child so the child has something to reference. So let's create the parent table. CREATE TABLE Species( ID INT PRIMARY KEY IDENTITY, Species VARCHAR(50) NOT NULL UNIQUE, FriendlyName VARCHAR(50) NOT NULL //NOT UNIQUE because multiple rows could be same category (Ex: Bunny) ); Now, the friendly name will likely have redundant data, so maybe later we can add a table for animal categories or something, but let's not overwhelm ourselves quite yet. Maybe in a few videos. Now that we have created that table, we can recreate the table that references it. The first thing to know when creating a foreign key is that the data type must match. Because the ID column in the species table is of type INT, we should make our Species column in the Animals table also of type INT. Secondly, to make this a foreign key we add REFERENCES Species(ID) to the Species column. DROP TABLE IF EXISTS Animals; CREATE TABLE Animals( ID INT PRIMARY KEY IDENTITY, Name VARCHAR(50) NOT NULL, Species INT NOT NULL REFERENCES Species(ID), ContactEmail VARCHAR(50) NOT NULL UNIQUE ); ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Support me! http://www.patreon.com/calebcurry Subscribe to my newsletter: http://bit.ly/JoinCCNewsletter Donate!: http://bit.ly/DonateCTVM2. ~~~~~~~~~~~~~~~Additional Links~~~~~~~~~~~~~~~ More content: http://CalebCurry.com Facebook: http://www.facebook.com/CalebTheVideoMaker Google+: https://plus.google.com/+CalebTheVideoMaker2 Twitter: http://twitter.com/calebCurry Amazing Web Hosting - http://bit.ly/ccbluehost (The best web hosting for a cheap price!)
Views: 7574 Caleb Curry
Primary key in SQL , Foreign key in SQL
 
07:27
The queries used in the tutorial are given below: CREATE TABLE Employee( EmpId INT PRIMARY KEY, EmpName varchar(25), EmpAddr varchar(50) ) INSERT INTO Employee VALUES (1,'Alex','SCO 1 Link Road') INSERT INTO Employee VALUES (2,'Carol','SCO 2 Link Road') INSERT INTO Employee VALUES (3,'Ross','SCO 3 Link Road') INSERT INTO Employee VALUES (3,'Ross','SCO 3 Link Road') SELECT * FROM EMPLOYEE CREATE TABLE DEPARTMENT ( DepID INT Primary key, Depname Varchar(50), EmpID INT REFERENCES EMPLOYEE(EmpID)) INSERT INTO DEPARTMENT VALUES (201,'Mechanical',4) SELECT * FROM DEPARTMENT
Views: 7629 Edu Therapy
SQL Server 15 - Composite Key
 
07:57
An interesting thing you can do with primary keys is that you can make a combination of columns the primary key. This is important when more than one column is required to make something unique. In an intermediary table, instead of having an association ID, we can have the combination of two rows as the primary key. This is known as either a compound or composite primary key. In the situation of using natural keys, composite keys are more common. For example, you could have a shopping website that allows multiple people from the same household to use a certain coupon you sent out. In this situation, you could use the address and the person's name as the natural primary key. What is the difference between a primary key and a column that has UNIQUE and NOT NULL constraints? The primary difference has to do with indexing. When you create a primary key, the column will automatically be indexed. This means that working with this data is faster. Now, we haven't talked a ton on indexes, but by default this will create a clustered index. UNIQUE constraints are also indexed by default, but the default index for a UNIQUE constraint is a non-clustered index. Clustered indexes determine how the table is actually stored, while non clustered indexes will make a sorted list that has reference to the data. This is not a life changing difference because these can actually be changed. We will discuss all of the details of indexing in future videos. As a side note, the IDENTITY column is not automatically indexed. How do we reference primary keys? This requires what is known as a foreign key, which we will discuss in the next video. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Support me! http://www.patreon.com/calebcurry Subscribe to my newsletter: http://bit.ly/JoinCCNewsletter Donate!: http://bit.ly/DonateCTVM2. ~~~~~~~~~~~~~~~Additional Links~~~~~~~~~~~~~~~ More content: http://CalebCurry.com Facebook: http://www.facebook.com/CalebTheVideoMaker Google+: https://plus.google.com/+CalebTheVideoMaker2 Twitter: http://twitter.com/calebCurry Amazing Web Hosting - http://bit.ly/ccbluehost (The best web hosting for a cheap price!)
Views: 11352 Caleb Curry
Working with Primary & Foreign key Constraint in SQL Server | SQL Server Tutorial
 
24:13
** For Online Training Registration: https://goo.gl/r6kJbB ? Call: +91-8179191999 💡 Visit Our Website for Classroom Training: https://nareshit.in/sql-server-training/ 💡For Online Training: https://nareshit.com/course/sql-server-online-training/ #sqlserver #server #programming #course #Tutorials #Training #Videos -------------------------- -------------------------- 💡 About NareshIT: "Naresh IT is having 14+ years of experience in software training industry and the best Software Training Institute for online training, classroom training, weekend training, corporate training of Hadoop, Salesforce, AWS, DevOps, Spark, Data Science, Python, Tableau, RPA , Java, C#.NET, ASP.NET, Oracle, Testing Tools, Silver light, Linq, SQL Server, Selenium, Android, iPhone, C Language, C++, PHP and Digital Marketing in USA, Hyderabad, Chennai and Vijayawada, Bangalore India which provides online training across all the locations -------------------------- 💡 Our Online Training Features: 🎈 Training with Real-Time Experts 🎈 Industry Specific Scenario’s 🎈 Flexible Timings 🎈 Soft Copy of Material 🎈 Share Videos of each and every session. -------------------------- 💡 Please write back to us at 📧 [email protected]/ 📧 [email protected] or Call us at the USA: ☎+1404-232-9879 or India: ☎ +918179191999 -------------------------- 💡 Check The Below Links ► For Course Reg: https://goo.gl/r6kJbB ► Subscribe to Our Channel: https://goo.gl/q9ozyG ► Circle us on G+: https://plus.google.com/+NareshIT ► Like us on Facebook: https://www.facebook.com/NareshIT ► Follow us on Twitter: https://twitter.com/nareshitek ► Follow us on Linkedin: https://goo.gl/CRBZ5F ► Follow us on Instagram: https://goo.gl/3UXYK3
Views: 67664 Naresh i Technologies
Oracle - SQL - Constraints
 
07:11
Oracle - SQL - Constraints Watch more Videos at https://www.tutorialspoint.com/videotutorials/index.htm Lecture By: Mr. Anadi Sharma, Tutorials Point India Private Limited.
Oracle||Oracle Integrity Constrants Patr -1 by Dinesh
 
32:48
DURGASOFT is INDIA's No.1 Software Training Center offers online training on various technologies like JAVA, .NET , ANDROID,HADOOP,TESTING TOOLS ,ADF,INFORMATICA,TABLEAU,IPHONE,OBIEE,ANJULAR JS, SAP... courses from Hyderabad & Bangalore -India with Real Time Experts. Mail us your requirements to [email protected] so that our Supporting Team will arrange Demo Sessions. Ph:Call +91-8885252627,+91-7207212428,+91-7207212427,+91-8096969696. http://durgasoft.com http://durgasoftonlinetraining.com https://www.facebook.com/durgasoftware http://durgajobs.com https://www.facebook.com/durgajobsinfo......
Oracle SQL Tutorial 4 - Beginner Terms - Database Design Primer 1
 
14:11
The terms covered in this video are: SQL RDBMS Relations NULL Database design Relationships Primary key Foreign key Constraint Indexes Data type HELP ME! http://www.patreon.com/calebcurry Subscribe to my newsletter: http://bit.ly/JoinCCNewsletter Donate!: http://bit.ly/DonateCTVM2. ~~~~~~~~~~~~~~~Additional Links~~~~~~~~~~~~~~~ More content: http://CalebCurry.com Facebook: http://www.facebook.com/CalebTheVideoMaker Google+: https://plus.google.com/+CalebTheVideoMaker2 Twitter: http://Twitter.com/calebCurry Amazing Web Hosting - http://bit.ly/ccbluehost (The best web hosting for a cheap price!)
Views: 67152 Caleb Curry
Oracle SQL Tutorial 14 - Column-Level and Table-Level Constraints
 
04:15
In the previous video we talked about adding constraints at the column-level. We made it nice and simple by only requiring a few keywords, but the problem we were having is that we could not assign a name to the constraint, which many people like to do so we can reference easily if we need to at a later time. To do this, it requires a little bit more typing, but it will give us extra flexibility and many consider it to be the higher quality approach to adding constraints. Let's go though a simple example. Let's say we have a users table with a user_id column that we want to make a primary key. We will create the table like this: CREATE TABLE( user_ id NUMBER PRIMARY KEY ) Instead of adding the PRIMARY KEY keywords after the data type, we add: CONSTRAINT user_pk PRIMARY KEY Now, we have assigned the name user_pk to this constraint. You can do the same with other constraints, such as UNIQUE. The syntax would be CONSTRAINT username_un UNIQUE. The other way to create constraints requires to put all of our constraints at the bottom of our table creation rather than inline with the column. This type of constraint is known as a table-level constraints. To make a column a primary key using table-level constraints, we add it to the CREATE TABLE command as if it is another row and use the CONSTRAINT keyword to tell Oracle that what is coming is a constraint, not a column in our table. CREATE TABLE users( user_id NUMBER, username VARCHAR2(50 CHAR), CONSTRAINT username_un UNIQUE (username), CONSTRAINT users_pk PRIMARY KEY (user_id) ) The primary differences here is that you have to put the column you are talking about in parenthesis after the PRIMARY KEY keyword. That's because it's at the end of the table and you need a way to tell it what column you are talking about. The option of putting it at the end of the table has the added benefit in this situation because if we needed to have a primary key that is the combination of multiple columns, we can do that by just adding the other column in the PRIMARY KEY parenthesis right after a comma. In summary, there are three ways to make constraints. The first is at the column level, unnamed. The second is at the column level, named. The third is at the table level, also named. In the next video we are going to create a named constraint in Oracle SQL Developer, so stay tuned and be sure to subscribe! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Support me! http://www.patreon.com/calebcurry Subscribe to my newsletter: http://bit.ly/JoinCCNewsletter Donate!: http://bit.ly/DonateCTVM2. ~~~~~~~~~~~~~~~Additional Links~~~~~~~~~~~~~~~ More content: http://CalebCurry.com Facebook: http://www.facebook.com/CalebTheVideoMaker Google+: https://plus.google.com/+CalebTheVideoMaker2 Twitter: http://twitter.com/calebCurry Amazing Web Hosting - http://bit.ly/ccbluehost (The best web hosting for a cheap price!)
Views: 16491 Caleb Curry
T-SQL - ForeIgn Key Constraints
 
05:24
T-SQL - ForeIgn Key Constraints Watch more Videos at https://www.tutorialspoint.com/videotutorials/index.htm Lecture By: Mr. Anadi Sharma, Tutorials Point India Private Limited
Candidate, Primary, Alternate, Super and Composite key types in DBMS (SQL)
 
10:00
Candidate, Primary, Alternate, Super and Composite key types in DBMS (SQL) Check my blog on this: https://sqlwithmanoj.com/2014/09/15/db-basics-what-are-candidate-primary-composite-super-keys-and-difference-between-them/ Check the whole "SQL Server Basics" series here: https://www.youtube.com/playlist?list=PLU9JMEzjCv14f3cWDhubPaddxRvx1reKR Check my SQL blog at: http://sqlwithmanoj.com/ Check my SQL FB Page at: https://www.facebook.com/sqlwithmanoj
Views: 50748 SQL with Manoj
Oracle ||  Referential Integrity Constrants Part-1 by Dinesh
 
25:04
DURGASOFT is INDIA's No.1 Software Training Center offers online training on various technologies like JAVA, .NET , ANDROID,HADOOP,TESTING TOOLS ,ADF,INFORMATICA,TABLEAU,IPHONE,OBIEE,ANJULAR JS, SAP... courses from Hyderabad & Bangalore -India with Real Time Experts. Mail us your requirements to [email protected] so that our Supporting Team will arrange Demo Sessions. Ph:Call +91-8885252627,+91-7207212428,+91-7207212427,+91-8096969696. http://durgasoft.com http://durgasoftonlinetraining.com https://www.facebook.com/durgasoftware http://durgajobs.com https://www.facebook.com/durgajobsinfo......
Oracle SQL Tutorial 19 - ON DELETE (SET NULL and CASCADE)
 
05:59
Welcome everyone! Something you need to consider when you are creating foreign keys is what happens if you delete the parent? As a reminder, the parent is the row that has the value you are referencing in the row that has a foreign key. Why is this something important to consider? It's important because foreign keys need to protect us from two primary things, unacceptable INSERT statements, and unacceptable DELETE statements. Let's see what happens when we try to insert incorrect data into the table with the foreign key: INSERT INTO projects VALUES (1, 'Update website homepage', 'CalebCurry') The response tells us plainly that there is no such user in the users table. So this works correctly. Deleting data on the other hand works a bit differently because the database does not know what you want to do with the child row when you delete the parent from the parent table. By default, we will get an error message that prevents the parent from being deleted, but there are some other options. How do we configure this? This is where the ON DELETE statement comes in. We add the keywords ON DELETE right after the foreign key and then we can give it the option of CASCADE or SET NULL. CASCADE means that if we delete the parent, we are also going to delete the child. In our situation what that means is that if somebody creates a project in our project table and then that persons account gets deleted, all of the projects he owns will also be deleted. CASCADE: CREATE TABLE projects( project_id NUMBER, Project_name VARCHAR2(50 CHAR) UNIQUE, creator VARCHAR2(50 CHAR) NOT NULL, CONSTRAINT projects_pk PRIMARY KEY (project_id), CONSTRAINT projects_users_fk FOREIGN KEY (creator) REFERENCES users (username) ON DELETE CASCADE ) SET NULL will take the value in the child table and get rid of it. What you are left with is NULL. This means that we have an orphaned child. The first thought you might have is that it is a bad thing to have an orphaned child, but in databases that is not always so. In our application if we had it set to SET NULL, when a user account gets deleted the projects would remain in existence they would just lack a creator. This might be a good thing if you are concerned about the long term survival of a project, this might be the route you want to go. It ultimately depends on the application purpose. If you don't like CASCADE or SET NULL, you can leave the entire ON DELETE statement and just have Oracle throw an error when a parent is deleted. As for us, we are going to use ON DELETE CASCADE. We need to use this with extreme caution. If you are not careful, someday you will run a delete a row and that will cascade through you database deleting a bunch of stuff you didn't want to delete. Stuff happens, so make sure you back up your database every once in eternity. Now, in the last video we started with a database design that had three tables. We've only created two in this video. In the next video we are going to create the next one, which is a little special. Then we'll finish things up by adding some indexes. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Support me on Patreon! http://www.patreon.com/calebcurry Subscribe to my newsletter: http://bit.ly/JoinCCNewsletter Donate!: http://bit.ly/DonateCTVM2. ~~~~~~~~~~~~~~~Additional Links~~~~~~~~~~~~~~~ More content: http://CalebCurry.com Facebook: http://www.facebook.com/CalebTheVideoMaker Google+: https://plus.google.com/+CalebTheVideoMaker2 Twitter: http://twitter.com/calebCurry Amazing Web Hosting - http://bit.ly/ccbluehost (The best web hosting for a cheap price!)
Views: 17441 Caleb Curry
SQL Server 33 - Indexes
 
07:42
Indexes allow us to tell the database that certain columns are columns we want to retrieve commonly. This allows the database to optimize retrieval. Additionally, when we get into the SELECT statement, we will often have to join data from multiple tables. When we correctly add indexes to our tables, we can improve the speed of our SELECT and also our joins. There are two types of Index. One is called clustered and the other is called non-clustered. Clustered indexes determine the actual order of the table. By default this is going to be the primary key column. So when you label a column as PRIMARY KEY, you are also going to be creating an INDEX that is a clustered index. A clustered index is kind of like a telephone book, where the data is right there when you look up a phone number. This means that if you are just making a small database that is only going to store a few things, you may be fine. But more likely than not you are going to want to add additional indexes. When you add a new index, you create a non-clustered index. These things do not actually determine the order of the rows in the table. A way of how you can think of how these work is like an index in the back of a book. The index of the book does not actually contain the data, it just tells you where to find it. What columns do you index? You are going to want every primary key to be indexed. What about foreign keys, are they indexed by default? No, they are not. Of all columns, you are probably going to want to index the foreign keys the most because they are used in joins. Lastly, you will likely want to index columns that you are going to use on a regular basis. You can also make composite indexes just like you can make composite keys. You would want to do this when you are going to constantly being using those columns together. There is a lot to learn on multicolumn indexes. We may explore this concept in more detail and see how SQL Server uses them in a future video, but as of right now it's probably more important that we get a general understanding of all things SQL Server before we deep dive on something like that. In the upcoming videos I'll be teaching you how to create indexes. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Support me! http://www.patreon.com/calebcurry Subscribe to my newsletter: http://bit.ly/JoinCCNewsletter Donate!: http://bit.ly/DonateCTVM2. ~~~~~~~~~~~~~~~Additional Links~~~~~~~~~~~~~~~ More content: http://CalebCurry.com Facebook: http://www.facebook.com/CalebTheVideoMaker Google+: https://plus.google.com/+CalebTheVideoMaker2 Twitter: http://twitter.com/calebCurry Amazing Web Hosting - http://bit.ly/ccbluehost (The best web hosting for a cheap price!)
Views: 11393 Caleb Curry
Oracle SQL Tutorial 13 - How to Add Column Constraints (Attributes)
 
05:55
So far, we have this table declaration: CREATE TABLE users( user_id NUMBER, username VARCHAR(50 CHAR) first_name VARCHAR2(50 CHAR), last_name VARCHAR2(50 CHAR) ) We can run this command see that it works. As we are learning though, we are going to want to be able to recreate our table with different settings and such, but if you try to run this command, it will complain that the table already exists. So we first need to delete this table before we start editing settings. When we get more experienced, we will learn about ways to edit the structure of a table that already exists. To fix this, we can get rid of the table using the DROP TABLE command: DROP TABLE users You can run this every time if you need to practice by adding a semicolon after it. This is how you can tell Oracle that you are putting in another command after it. This is known as a delimiter. When you run the script, it is going to run both commands. Now we can go through and reconsider our table structure. This is fine for starting out because we don't have any important data in our database, but once your database is in production you are not going to want to just drop tables. In the last video we discussed different constraints that you can apply to columns in a database table, but how do you actually apply these when you are creating a table? The first way you define constraints is to put them right after the column in your CREATE TABLE statement. CREATE TABLE users( username VARCHAR2(50 CHAR) NOT NULL ) When we define constraints this way, we usually say we are adding column attributes. If you have two constraints you want to add, you just put one after the other with spaces in between. There is no particular order that is required. CREATE TABLE users( username VARCHAR2(50 CHAR) NOT NULL UNIQUE ) In this situation we have already given the column the NOT NULL and UNIQUE attributes, so we should consider making this a primary key: CREATE TABLE users( username VARCHAR2(50 CHAR) PRIMARY KEY ) As you can see, adding column attributes is super easy. We can add a default like this: CREATE TABLE users( username VARCHAR2(50 CHAR) PRIMARY KEY, account_balance NUMBER DEFAULT 0 ) Note that now we need the comma after the first row. There are a few constraints we did not talk go through an example, specifically foreign keys and check constraints. We will be adding these constraints to our database in future videos. In the mean time, I have a thought for you… Many people prefer to name their column constraints. That way, we can refer to certain constraints by name. For example, we might have a primary key constraint that could be named users_pk. The way we are creating these constraints does not allow for this feature, so in the next video we are going to be discussing different ways to create constraints. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Support me on Patreon! http://www.patreon.com/calebcurry Subscribe to my newsletter: http://bit.ly/JoinCCNewsletter Donate!: http://bit.ly/DonateCTVM2. ~~~~~~~~~~~~~~~Additional Links~~~~~~~~~~~~~~~ More content: http://CalebCurry.com Facebook: http://www.facebook.com/CalebTheVideoMaker Google+: https://plus.google.com/+CalebTheVideoMaker2 Twitter: http://twitter.com/calebCurry Amazing Web Hosting - http://bit.ly/ccbluehost (The best web hosting for a cheap price!)
Views: 22611 Caleb Curry