Home
Search results “Primary key columns in oracle”
SQL tutorials 17: SQL Primary Key constraint,  Drop primary Key
 
09:22
Blog link: http://www.rebellionrider.com/sql-primary-key.htm SQL tutorial on Primary key / SQL Primary key, In this tutorial you will learn about simple primary key, composute primary key, how to drop primary key. defining primary key using create table and alter table along with many other things. Tool used in this tutorial is SQL Developer. This tutorial series is part of SQL expert exam certification training. if you are preparing for SQL certification you can use my tutorials. This SQL Tutorial is a part of free training. Copy Cloud referral link || Use this link to join copy cloud and get 20GB of free storage https://copy.com?r=j7eYO7 Contacts E-Mail [email protected] Twitter https://twitter.com/rebellionrider Instagram http://instagram.com/rebellionrider Facebook. https://www.facebook.com/imthebhardwaj Linkedin. http://in.linkedin.com/in/mannbhardwaj/ Thanks for linking, commenting, sharing and watching more of our videos This is Manish from RebellionRider.com So Primary Key There are two types of Primary keys First is Simple primary Key: Primary key which Involves only one column and Second is Composite Primary Key: Primary Key which involves more than one column. We will start with Simple primary key. You can create Primary key either with Create Table statement of by using Alter table Statement. Let's define simple primary key using create table statements. With create table statement we can either define primary key at column level or at table level. We will start with defining Primary key at column level using create table statement. You just have to put keyword Primary key after data type and size of column while defining a column of a table. Here oracle server will create a primary key on product id with default constraint name which will be slightly difficult to understand. You can give your own name to your constraint which is also a good practice.
Views: 105067 Manish Sharma
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: 13373 Caleb Curry
Oracle SQL Tutorial 18 - How to Create Foreign Keys
 
07:09
In this video we are going to be creating foreign keys. I highly recommend watching the previous video before you watch this one. Essentially, we are creating a very simple database for a system where we can create projects and add people to those projects. We started with the users table: --Delete the table if needed: --DROP TABLE users; CREATE TABLE users( user_id NUMBER, username VARCHAR2(50 CHAR) UNIQUE, CONSTRAINT users_pk PRIMARY KEY (user_id) ); Now we are going to create a table for projects with a column that is a foreign key to the username. We're going to want to make this match data types: CREATE TABLE projects( project_id NUMBER, project_name VARCHAR2(50 CHAR) UNIQUE, creator VARCHAR2(50 CHAR) ) Next, we need to add the column attributes we decided on last video: CREATE TABLE projects( project_id NUMBER, project_name VARCHAR2(50 CHAR) UNIQUE, creator VARCHAR2(50 CHAR) NOT NULL ) NOT NULL because we want every project to have a creator, but we are not labeling UNIQUE because that means we could only have a specific username once in the table. We want to allow a user to create multiple projects. We also need to add a primary key: CREATE TABLE projects( project_id NUMBER, project_name VARCHAR2(50 CHAR) UNIQUE, creator VARCHAR2(50 CHAR) NOT NULL, CONSTRAINT projects_pk PRIMARY KEY (username) ) Now, the question that remains is, how can I tell Oracle that I want the username to reference the username column of the other table? We have to make a foreign key constraint. As you've learned from the previous videos, there are about three ways to create constraints. You can do it inline at the column level, unnamed. You can do it at the column level, named, and you can do it at the Table level, named. Usually the table-level is preferred, but I will quickly remind you how to do all three again. CREATE TABLE projects( project_id NUMBER, project_name VARCHAR2(50 CHAR) UNIQUE, creator VARCHAR2(50 CHAR) NOT NULL REFERENCES users (username), CONSTRAINT projects_pk PRIMARY KEY (project_id) ) This works, but if we want to name it, we should do this: CREATE TABLE projects( project_id NUMBER, project_name VARCHAR2(50 CHAR) UNIQUE, creator VARCHAR2(50 CHAR) NOT NULL CONSTRAINT projects_users_fk REFERENCES users (username), CONSTRAINT projects_pk PRIMARY KEY (project_id) ) This works, but the preferred method is to do it at the table level: 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) ) Great! So you've learned how to create a foreign key, now we can see it inside of Oracle SQL Developer. One important thing when it comes to foreign keys is what happens when have data in your database and you try to delete the parent row that a row in the child table references? In the next video we are going to configure that using ON DELETE. See you all then and if you enjoy this series, please do me a huge favor by liking the video and subscribing to my YouTube channel. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 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: 27760 Caleb Curry
Oracle SQL Tutorial 15 - How to Add Primary Key Constraints
 
02:54
The goal of this video is to take the CREATE TABLE statement we have and walk through the different ways to create primary keys. This and foreign keys are the most common constraints, so we need to make sure that you have this one down. Once we have a more complex database design with multiple tables, we will learn the proper way to create foreign keys. For now, I am going to keep all of our constraints at the column level, unnamed. The only exception is the primary key, because that is what we are focusing on in this video. The first way to create the primary key is at the column level, unnamed. The primary key is very important because it what we use to distinguish rows from one another. Every table you create is going to need a primary key, and I suggest putting a lot of effort into making sure your keys are set up correctly and organized. --Delete the table if needed: DROP TABLE users; CREATE TABLE users( user_id NUMBER PRIMARY KEY, username VARCHAR2(50 CHAR) NOT NULL UNIQUE ) The next way is at the column level, but named: --Delete the table: DROP TABLE users; CREATE TABLE users( user_id NUMBER CONSTRAINT users_pk PRIMARY KEY, username VARCHAR2(50 CHAR)NOT NULL UNIQUE ) The general naming convention here is the table name followed by an underscore, followed by pk for primary key. Finally, the third way, which is at the table level, is the way we are going to create our primary key: --Delete the table: DROP TABLE users; CREATE TABLE users( user_id NUMBER, username VARCHAR2(50 CHAR) NOT NULL UNIQUE, CONSTRAINT users_pk PRIMARY KEY (user_id) ) Now, once you've created these constraints, you can use Oracle SQL Developer to find these constraints. Open your databases in the connections tab and find the table in the Tables folder. Double click your table and travel to the Constraints tab. You can tell here that the UNIQUE constraint still exists in this table, but it has a pretty disgusting name. It kind of wants to make me puke. Referencing that constraint in the future with that wacky name would be a burden. Engrave these three options in your head so that you can use any of them whenever you need and can read other peoples' code. Thank you for sticking with the series thus far. In the next video, we will be…doing something. See you then! :) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 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: 18201 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: 18392 Caleb Curry
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: 821 Kishan Mashru
Primary key in Oracle
 
06:32
Primary key in Oracle what is primary key ? 1) Primary key is a single field or combination of fields that uniquely identified. 2)The primary key can not contain a null value. 3)A table can have only one primary key. 4)Primary keys must contain UNIQUE values. 5)Table can have only ONE primary key. CREATE TABLE Employee ( emp_id numeric(10) not null, name varchar2(50) not null, city varchar2(50), CONSTRAINT id_pk PRIMARY KEY (emp_id) ); Other option to Add ALTER TABLE Employee ADD CONSTRAINT id_pk PRIMARY KEY (emp_id); The syntax to drop a primary key : ALTER TABLE Employee DROP CONSTRAINT id_pk; #techquerypond https://techquerypond.wordpress.com https://techquerypond.com https://twitter.com/techquerypond
Views: 197 Tech Query Pond
Oracle - Primary Keys
 
08:37
Oracle - Primary Keys
Views: 2773 Chris Ostrowski
48. PRIMARY KEY in SQL (Hindi)
 
11:12
Please Subscribe Channel Like, Share and Comment Visit : www.geekyshows.com
Views: 39433 Geeky Shows
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: 50764 Caleb Curry
Oracle Part 6 Primary Key
 
24:45
Primary key, varchar, length, trim, order by clause
Views: 1131 Free OpenMentor
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: 78543 Naresh i Technologies
Oracle SQL Tutorial 22 - Why Primary Keys Shouldn't Change
 
07:14
In the last video I mentioned that with our database design it is important to make sure that nobody tries to update a user's username. What happens if they do? Nothing horrible, Oracle will just throw an error. That's not such a big deal, but if you are hoping to make some kind of application that allows someone to change their username, this is not the best set up. Why? If you look at the projects table, we have a foreign key that references the username. Let's assume for a moment that Oracle allows you to do anything with your data. That means that if a user updates their username, there will be projects created by users that don't exist. Or a user could change their name to the previous owner. To fix this problem, we would need something such as an ON UPDATE CASCADE command for our foreign key. That would mean that if the user updated their username, the columns that reference that username would also update to the new value. This exists in some database management systems, but this does not exist in Oracle at the time of this video. How do we get around this problem? I'm sure we could conjure up something to allow us to update the username, but the easiest solution is to reference the user_id instead of the username. That way, when the username is updated, nothing changes inside of the foreign key. As a general rule, primary keys should never change. Foreign keys CAN change, but they should not change because a primary key changed. So, if we did happen to use a username as a column, it would be frowned upon if the username had to change because the column it references changes. However, it would be acceptable to change the foreign key if we needed to point to a new entity in the users table. Even if a username is never intended to change, these complications bother a lot of people. You can mitigate these problems by only referencing surrogate keys in foreign keys. This has the downside though that when you retrieve the data, you are going to have to do more work to make the data readable. For example, we had a table that was called project_users. It is essentially a table that says what users are part of what projects. We could have the foreign keys reference the project's name and the user's username. Then when you could say SELECT * FROM project_users. The data would be completely readable without doing anything. If you switch to only referencing surrogate primary keys, you will have a bunch of random numbers that don't mean anything and will have to be joined with other tables…which is really super frustrating when later you have to join a thousand tables to read anything. Which side do you prefer? Pick a side. Choose wisely. I'll see you all in the next video ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 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: 6861 Caleb Curry
Primary Keys and Foreign Keys in Oracle Database
 
11:04
Primary Keys and Foreign Keys in Oracle Database
Views: 539 Abe Samir's Academy
SQL tutorials 18: SQL Foreign Key Constraint By Manish Sharma
 
10:23
SQL Tutorial 18: SQL foreign key constraint. Topic covered in this tutorial 1. Defining SQL foreign key using create table at column level 2. Defining SQL foreign key using create table at table level 1. Defining SQL foreign key using Alter Table statement Links Website article: http://www.rebellionrider.com/sql-foreign-key.htm Primary key tutorial: http://www.rebellionrider.com/sql-foreign-key.htm Create Table Tutorial: http://www.rebellionrider.com/sql-create-table.html Tool used in this tutorial is SQL Developer. This tutorial series is part of SQL expert exam certification training. if you are preparing for SQL certification you can use my tutorials. This SQL Tutorial is a part of free training. Copy Cloud referral link || Use this link to join copy cloud and get 20GB of free storage https://copy.com?r=j7eYO7 Contacts E-Mail [email protected] Twitter https://twitter.com/rebellionrider Instagram http://instagram.com/rebellionrider Facebook. https://www.facebook.com/imthebhardwaj Linkedin. http://in.linkedin.com/in/mannbhardwaj/ Thanks for linking, commenting, sharing and watching more of our videos This is Manish from RebellionRider.com Foreign key is an Input/output data constraint which is also known as referential integrity constraint. Foreign key represent a link or say a relationship between columns of tables. Similar to primary key constraint Foreign Key constraint is also of two types. Simple Foreign key constraint and Composite Foreign key constraint. Constraint which involves only one column in foreign key in child table and one column in reference key in parent table is called Simple Foreign Key. While the constraint which involves more than one column in foreign key in child table and more than one column in reference key in the parent table is called Composite Foreign Key.
Views: 106602 Manish Sharma
SQL in Oracle 11g Tutorial #9: Implementation/Example of Primary Key and Foreign Key
 
08:52
SQL in Oracle 11g Tutorial #9: Implementation/Example of Primary Key and Foreign Key. How to create a Primary Key. How to create a Foreign Key. Thanks for Watching my Channel “Learn TechToTech”. Please subscribe my channel for getting first updates after uploading video.Social Media pages of Channel are: 1. My Website : www.learnfromrakesh.com 2. My Twitter: https://twitter.com/LearnTechtotech 3. Facebook Page: https://www.facebook.com/LearnTechToTech 4. Blogger : https://learntechtotech.blogspot.in/ 5. Google+ : https://learntechtotech.blogspot.in/ 6. Pinterest : https://in.pinterest.com/LearnTechToTech/ 7. LinkedIn: https://www.linkedin.com/in/Learntechtotech/ Playlist of Different Technology: 1. Operating System : https://goo.gl/q6SfrW 2. Python Programming Language : https://goo.gl/L8b5dc 3. C Language : https://goo.gl/SwvDu9 4. C language for Placement: https://goo.gl/AaQBa4 5. Java: https://goo.gl/M8F2uy 6. MySql : https://goo.gl/vdJbHQ 7. Android Mobile Application Development: https://goo.gl/M6woaT 8. Kotlin Programming Language : https://goo.gl/GXE5cd 9. Go Programming: https://goo.gl/Ua3xYW 10. Internet of Things(IoT): https://goo.gl/f2afkY 11. Oracle 11g : https://goo.gl/zds8r2 12. C++ : https://goo.gl/C1psMT
Views: 134 Learn TechToTech
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: 25533 Caleb Curry
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: 13863 Caleb Curry
how to add and drop primary key in sql server 2008 and 2012
 
07:59
How to add primary key in sql by query. To allow naming of a PRIMARY KEY constraint and describe how to drop primary keys .
Views: 12438 Programming School
Oracle SQL Tutorial : How to create Id with AUTO INCREMENT in Oracle PL SQL
 
08:43
Oracle SQL Tutorial Oracle tutorial: How to create Id with AUTO INCREMENT in Oracle oracle tutorial for beginners sequence in oracle identity key in sql In this Oracle tutorial , we can create an auto increment field using ‘sequence’ object that can be assigned as primary keys. Using Oracle ‘sequence’ object, you can generate new values for a column. An Oracle sequence is an object like a table or a stored procedure. Examples CREATE SEQUENCE SYSTEM.MYSEQ START WITH 1 MAXVALUE 999999999999999999999999999 MINVALUE 1 NOCYCLE CACHE 20 NOORDER; CREATE OR REPLACE TRIGGER TR_CITY BEFORE INSERT ON CITY FOR EACH ROW BEGIN SELECT LPAD(LTRIM(RTRIM(TO_CHAR(myseq.NEXTVAL))),10,'0') INTO :NEW.id FROM DUAL; END; / Subscribe on youtube: https://www.youtube.com/channel/UCpiyAesWNYOXSz5GPq8lbkA For more tutorial please visit #techquerypond https://techquerypond.wordpress.com https://twitter.com/techquerypond identity column
Views: 11110 Tech Query Pond
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: 5735 TechBrothersIT
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: 285250 Techtud
auto increment in sql oracle - ( Auto increment field )
 
03:07
auto increment in sql oracle ----------------------------------------------- CREATE table customers ( customer_id int not null, customer_name varchar(50), primary key (customer_id) ); create sequence customer_id minvalue 1 start with 1 cache 10; insert into customers values(customer_id.nextval,'maxwel'); -- to drop sequence drop sequence customer_id
Views: 10821 Data Disc
How to create Primary Key in sql  using oracle 10g
 
02:21
This video gives information about how to create primary key to table in oracle 10 g
Views: 1282 AvilTwo Beginer
Oracle SQL Tutorial 16 - Parent Child Relationships
 
06:09
So far in this series we have discussed database design, creating tables, and constraints. We've brought up the concept of foreign keys, but we have not explained how to create them. That is the goal of this video and the upcoming videos. We want to study those foreign keys! Let's make them not so foreign. Let's learn the proper way to define a foreign key. As a reminder, a foreign key is a column that references a column of another table. The column it references must either be a primary key, or have the UNIQUE constraint. This means that every value inside of the column that is labeled as a foreign key, there must be that value in some row of the referenced column. As an example, imagine that we have the users table, and we have a table service_requests. We could have a column in the service_request that references a column in the users table. Usually this would be the primary key that is referenced, but there is nothing stopping you from referencing a unique column. Just for fun, let's go through an example using the username column. If we have a service_requests table, every single row within the table is going to be what some would consider an instance of a service_request. This means that the table columns are like the blueprint for what a service request looks like and then each row is an individual service request. If we have one of the columns labeled as a foreign key to the username of the users table, what does that mean practically? It means that for a single row, the value for that column must be a value that exists in the users table. We could have a service_request submitted by a user with the username of Yoloswagman. This means that there must be a row inside of the users table that has the value Yoloswagman for the username column. This brings up the concept of parent and child relationships. Yoloswagman in this situation is the parent, and his service request is the child. When we draw it out, it makes sense why a primary key must be UNIQUE. If we had two Yoloswagmans, the child would not know which column is the parent. The same applies if we were using IDs and we had So remember, always reference a primary key or a column with the UNIQUE constraint. Now, I have a question for you. Do foreign keys automatically have the UNIQUE constraint, just like primary keys? The answer is no. A parent row can have many child rows. It makes sense because the user could submit multiple service requests. Can we force the column to be unique? Absolutely. If that was the case, the user could only make one service request. Another question. Do foreign keys automatically have the NOT NULL constraint, just like primary keys? The answer is no. Essentially what this means is that a child could be created with no parent. Can we force the column to be NOT NULL? Absolutely. It is ok in some situations to allow the row to be null, but in this situation it makes no sense. It would be wise for us to add that constraint ourselves. So now that you understand some more differences between primary and foreign keys and parent child relationships, take all of these questions into consideration when you are creating foreign keys. In the next video, we are going to start a small project that is going to require multiple tables. We'll take a video to design our structure and then we'll get to creating those foreign keys in Oracle SQL Developer. Stick around and if you like these videos please be a serious supporter and subscribe to my channel. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 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: 15336 Caleb Curry
SQL with Oracle 10g XE - Using ALTER TABLE to Modify Table Columns
 
05:23
In this video I use the ALTER TABLE command to modify an existing field column. The command will allow you to change the data types, whether the field can be null, or even the primary key. When using the ALTER TABLE command you would use the keyword MODIFY to make changes to an existing column. Be careful when changing a data type of the null field as existing data may cause an error if not in compliance with the new change. The code I used to alter the Books table is : ALTER TABLE BOOKS MODIFY ISBN_10 VARCHAR(13); This video is part of a series of videos with the purpose of learning the SQL language. For more information visit Lecture Snippets at http://lecturesnippets.com.
Views: 16487 Lecture Snippets
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: 10449 Caleb Curry
drop primary key,not null,unique,default and check constraints from columns in a table
 
12:48
This video explains how to drop primary key,not null,unique,default and check constraints with or without constraint name in a table link to HOW to add constraint while creating table: https:// https://www.youtube.com/watch?v=dh_UKs-LnK8 link to how to add new columns with constraints : https://www.youtube.com/watch?v=UNAatxnnwB8 link to how to add constraints to existing column https://www.youtube.com/watch?v=02_fXRQpwSc how to drop all constraints on the table: https://www.youtube.com/watch?v=CM7FPqIr6gc subscribe - https://www.youtube.com/channel/UCNl7...
Views: 2438 kwl zerotwonine
How to Add Primary Key After Creating a Table | Add Foreign Key After Creating a Table | Oracle 12c
 
09:44
How to Add Primary Key After Creating a Table | Add Foreign Key After Creating a Table | Oracle 12c --------------------------------------------------------------------------------------------------------- how to add primary key after creating a table,sql create table foreign key,alter table add primary key sql server,alter table add primary key mysql,alter table add primary key oracle,sql create table primary key autoincrement,sql server add primary key to existing table with data,sql composite primary key,cannot define primary key constraint on nullable column in table, foreign keys, constraints, oracle sql, primary key, how to, how to add primary key, primary key constraints, constraint, structured query language, oracle sql developer, oracle foreign keys, oracle foreign key, foreign, key, relational databases, database, how to create foreign keys, how to create foreign key, database constraints, sql tutorials for beginners, sql expert, sql expert tutorials, database, oracle, table, online training,insert into oracle,oracle insert into multiple rows,create table oracle,oracle 12c alter table add identity column,oracle create table default value sysdate,collections in oracle pl sql with examples,Oracle 12c, database, oracle database (software), sql, sql developer, sql tutorials, how to create database using dbca, how to create database in oracle,oracle cloud, database 12c, dba genesis,database services, database, create, 11g, dba, db, beginner, Please Subscribe My Channel
Oracle Primary Key Constraint 2 تعليم اوراكل
 
02:34
by Mohamed El Desouki - محمد الدسوقى [email protected] Tel :00966 553450836 جامعة سلمان بن عبد العزيز - السعودية - الخرج How to Add Primary Key Constraint Using Alter Table Statement.إضافة قيد المفتاح الرئيسى بعد إنشاء الجدول Text Book: Fundamentals of Database Systems, 5th Edition, by Elmasri/Navathe, published by Addison-W oracle create table statement oracle drop table statement oracle constraints database constraints primary key constraint foreign key constraint check constraint null not null constraint unique constraint
Oracle SQL Tutorial 12 - Intro to Constraints
 
06:13
As I believe I've mentioned in an earlier video, a constraint is basically a rule we can put in our database that prevents someone from putting the wrong data in. It protects our relationships and data integrity. Because the goal of these constraints are to protect our data integrity, you may hear them called integrity constraints. There are many integrity constraints we are going to talk about: NOT NULL UNIQUE PRIMARY KEY FOREIGN KRY CHECK There is also the DEFAULT attribute. These are all keywords we can add to our columns that will change the way the database works with our data and also prevents incorrect data. NOT NULL is a constraint you can put on a column that prevents nulls. A null is the absence of a value. When we say null, we are saying that every single row has to have a value for this column. UNIQUE is a constraint that makes every row have a unique value for this column. Now note, this does not require values to be put it, and it will allow multiple rows to be null. Next, we are going to talk about primary keys. What qualifies a column as a candidate key? First, not a single row should have a null for that column. Second, every row must be unique. The primary key constraint is essentially a combination of the NOT NULL constraint and the UNIQUE constraint. The foreign key constraint sets the requirement that any value in this column for any row must match a row in another column. Check constraints allow us to be more strict with what data is allowed in our database. NOT NULL and UNIQUE give some level of restriction, but what if we want something more specific? For example, what if we only want values between 0 and 100? That is where check constraints come in. When using check constraints, you give a boolean expression. A boolean expression is something that can be evaluated to true or false. It will only insert the row if the value you try to put into the row makes the expression evaluate to true. So if you put in a value too great or small, the expression will be false and the data is not allowed to be entered. The default constraint is a value you can give a column, and if for any reason when the row is created in the table a value is not provided, the default value will be given. So for example, we could have a bank account table where the balance defaults to 0. How do you actually implement these constraints when you are creating a table? In the next video we are going to be adding these to our users table. Please be sure to subscribe! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 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: 25564 Caleb Curry
SQL PRIMARY KEY Constraint Telugu | PRIMARY KEY Constraints-vlr training
 
06:08
SQL PRIMARY KEY Constraint Telugu In Telugu: PRIMARY KEY Constraints The PRIMARY KEY constraint uniquely identifies each record in a database table. Primary keys must contain UNIQUE values, and cannot contain NULL values. A primary key is a field in a table which uniquely identifies each row/record in a database table. Primary keys must contain unique values. A primary key column cannot have NULL values. A table can have only one primary key, which may consist of single or multiple fields. When multiple fields are used as a primary key, they are called a composite key. In English: download sql study material Website: http://www.vlrtrain.in/2016/09/download-sql-files.html Learn SQL sql tutorial for beginners sql commands oracle sql tutorial sql tutorial advanced mysql tutorial sql tutorial video SQL Tutorial, Tutorials SQL
Views: 2072 VLR Training
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: 36648 Sam Dhanasekaran
Tutorial#59 How to Use Primary key Constraint in Oracle SQL Database|Primary key Constraint in SQL
 
08:24
Know about Primary Key Constraint in Oracle SQL Database or what is Constraints and Types of Constraints in an Oracle SQL Database | integrity Constraints in SQL Primary Key Constraint is nothing but its allowing Unique and Not null Values in columns Explaining constraints and types of constraints in Oracle or Constraints in Oracle SQL database or Constraints is nothing but a set of rules which is applied to the columns of any table in the database ------------------------------------ Assignment Link: ----------------------------------- https://drive.google.com/open?id=1eMUWZVzoltE-Bim6oPhy0muCoNPRnDjc In this series we cover the following topics: SQL basics, create table oracle, SQL functions, SQL queries, SQL server, SQL developer installation, Oracle database installation, SQL Statement, OCA, Data Types, Types of data types, SQL Logical Operator, SQL Function,Join- Inner Join, Outer join, right outer join, left outer join, full outer join, self-join, cross join, View, SubQuery, Set Operator. follow me on: Facebook Page: https://www.facebook.com/LrnWthr-319371861902642/?ref=bookmarks Contacts Email: [email protected] Instagram: https://www.instagram.com/equalconnect/ Twitter: https://twitter.com/LrnWthR
Views: 63 EqualConnect Coach
Part 12   Can we join two tables without primary foreign key relation
 
10:38
Link for all dot net and sql server video tutorial playlists http://www.youtube.com/user/kudvenkat/playlists Link for slides, code samples and text version of the video http://csharp-video-tutorials.blogspot.com/2014/09/part-12-can-we-join-two-tables-without.html Can we join two tables without primary foreign key relation Yes, we can join two tables without primary foreign key relation as long as the column values involved in the join can be converted to one type. ID column in Departments table is not the primary Key and DepartmentId column in Employees table is not the foreign key. But we can still join these tables using ID column from Departments table and DepartmentId column from Employees table, as both the columns involved in the join have same data type i.e int. Select Employees.Name as EmployeeName, Departments.Name as DepartmentName from Employees join Departments on Departments.ID = Employees.DepartmentId The obious next question is, if primary foreign key relation is not mandatory for 2 tables to be joined then what is the use of these keys? Primary key enforces uniqueness of values over one or more columns. Since ID is not a primary key in Departments table, 2 or more departments may end up having same ID value, which makes it impossible to distinguish between them based on the ID column value. Foreign key enforces referential integrity. Without foreign key constraint on DepartmentId column in Employees table, it is possible to insert a row into Employees table with a value for DepartmentId column that does not exist in Departments table. The following insert statement, successfully inserts a new Employee into Employees table whose DepartmentId is 100. But we don't have a department with ID = 100 in Departments table. This means this employee row is an orphan row, and the referential integrity is lost as result Insert into Employees values (8, 'Mary', 'Female', 80000, 100) If we have had a foreign key constraint on DepartmentId column in Employees table, the following insert statement would have failed with the following error. Msg 547, Level 16, State 0, Line 1 The INSERT statement conflicted with the FOREIGN KEY constraint. The conflict occurred in database "Sample", table "dbo.Departments", column 'ID'.
Views: 128102 kudvenkat
PRIMARY KEY and UNIQUE KEY Constraints in Oracle Database
 
09:22
unique constraint oracle oracle check constraint alter table add constraint primary key oracle oracle unique constraint multiple columns oracle unique constraint vs unique index
Views: 15 Adam Tech
SQL Server 26 - PRIMARY KEY, NOT NULL, UNIQUE
 
03:36
In the last video we created our first table, but I want to give SQL Server some extra information so the database knows more about each of the columns. The first thing is to establish the primary key. To do this all we do is add PRIMARY KEY after the column we want to be the primary key. Simple enough. When we add a constraint right after the column like this, it is often called a column attribute. CREATE TABLE Animals( ID INT PRIMARY KEY, Name VARCHAR(50), Species VARCHAR(50) ); Additionally, if you are using an ID column, it is best to have it labeled as the IDENTITY column. That way, SQL Server will automatically increment the number. CREATE TABLE Animals( ID INT PRIMARY KEY IDENTITY, Name VARCHAR(50), Species VARCHAR(50) ); The other attributes we've discussed in this series are NOT NULL and UNIQUE. We can make the name NOT NULL and the species NOT NULL. We don't have a good column for UNIQUE, so let's add one: CREATE TABLE Animals( ID INT PRIMARY KEY IDENTITY, Name VARCHAR(50) NOT NULL, Species VARCHAR(50) NOT NULL, ContactEmail VARCHAR(50) NOT NULL UNIUQE ); You can see that it is very easy to add multiple column attributes to a column. Just separate them by spaces. The order does not matter. Also, when you say primary key the column is automatically NOT NULL and UNIQUE. There are other attributes you can use including DEFAULT, FOREIGN KEY, and SPARSE. DEFAULT will give a value for a column if you do not put anything in yourself. Foreign keys are used to reference other columns. SPARSE is an attribute we haven't discussed. You can use SPARSE if most of the rows are going to have a NULL for a column and it saves storage space, but we will worry about that in another 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: 6546 Caleb Curry
how to add primary key in existing table in mysql
 
07:16
this video shows how to add and remove primary key in existing mysql table .
Views: 5715 expert programming
SQL in Oracle 11g Tutorial #7: Alter table( Add, Delete , Enable and Disable Primary Key)
 
08:22
SQL in Oracle 11g Tutorial #7: Alter table( Add, Delete , Enable and Disable Primary Key). This video will explain you the following: 1. How to Add the Primary Key 2. How to delete the primary Key 3. How to Enable the Primary Key 4. How to disable the primary key Thanks for Watching my Channel “Learn TechToTech”. Please subscribe my channel for getting first updates after uploading video.Social Media pages of Channel are: 1. My Website : www.learnfromrakesh.com 2. My Twitter: https://twitter.com/LearnTechtotech 3. Facebook Page: https://www.facebook.com/LearnTechToTech 4. Blogger : https://learntechtotech.blogspot.in/ 5. Google+ : https://learntechtotech.blogspot.in/ 6. Pinterest : https://in.pinterest.com/LearnTechToTech/ 7. LinkedIn: https://www.linkedin.com/in/Learntechtotech/ Playlist of Different Technology: 1. Operating System : https://goo.gl/q6SfrW 2. Python Programming Language : https://goo.gl/L8b5dc 3. C Language : https://goo.gl/SwvDu9 4. C language for Placement: https://goo.gl/AaQBa4 5. Java: https://goo.gl/M8F2uy 6. MySql : https://goo.gl/vdJbHQ 7. Android Mobile Application Development: https://goo.gl/M6woaT 8. Kotlin Programming Language : https://goo.gl/GXE5cd 9. Go Programming: https://goo.gl/Ua3xYW 10. Internet of Things(IoT): https://goo.gl/f2afkY 11. Oracle 11g : https://goo.gl/zds8r2 12. C++ : https://goo.gl/C1psMT
Views: 615 Learn TechToTech
Create Oracle SQL database with auto-incrementing integers for the primary key
 
12:49
Create a new Oracle SQL database using SQL. After the database is created, I demonstrate using an Oracle SQL sequence and trigger to create auto-incrementing integers which are used as the table's primary key.
Views: 12723 Mike Colbert
Oracle SQL Tutorial 7 - Normalization - Database Design Primer 4
 
20:38
The database normal forms are used to normalize a database. What does it mean to normalize a database? It means to break it up into multiple tables to prevent redundant, conflicting, and bad data. The three normal forms are 1nf, 2nf, and 3nf. These stand for first normal form, second normal form, and third normal form. There are other normal forms, such as Boyce Codd normal form (BCNF), but the first 3 normal forms are the ones that are really important to know. The normal forms depend on one another. It is kind of like a ladder. In order to be in 2nd normal form, you must first be in first normal form. In order to be in 3rd normal form, you must first be in 2nd normal form. First normal form is all about individuality and giving data its space. Each column must be atomic...that is, in the smallest indivisible piece. Each value for the column must also only contain one value. To fix first normal form when you have a column violation, break the column into multiple columns. To fix first normal form when you have data violation, break the column into a new table and have a column that references the old table. Second normal form is all about partial dependencies. A partial dependency is when a column only depends on part of the primary key. This is often seen when you have an intermediary table in a many to many relationship (as a reminder, we break up many to many relationships into one to many relationships with intermediary tables in between). The solution to get rid of partial dependencies is to put the data in the table to where the column depends entirely on the key. If you do not already have a table that fits the rule, you can consider creating one. Third normal form is all about transitive dependencies. This is when a column in a table depends on another column instead of depending solely on the primary key. The solution to this is to take the column that is directly dependent on the primary key and bring it into its own table. Then, you can use foreign keys to connect the tables. This video concluded with a noble speech on how database design is very subjective. Thus is so because as we normalize more and more, the design becomes more and more complex. If we get to the point where we have hundreds of tables for a relatively small database, we can really hurt performance and increase risk of mistakes. Hopefully this video was helpful to everyone. See you in the next one! 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: 30995 Caleb Curry
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: 444865 Dr. Daniel Soper
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: 248709 Satish B
How to create Virtual Columns in Oracle Database
 
09:02
How to create Virtual Columns in Oracle Database 12c When queried, virtual columns appear to be normal table columns, but their values are derived rather than being stored on disc. The syntax for defining a virtual column is listed below. column_name [datatype] [GENERATED ALWAYS] AS (expression) [VIRTUAL] If the datatype is omitted, it is determined based on the result of the expression. The GENERATED ALWAYS and VIRTUAL keywords are provided for clarity only. The script below creates and populates an employees table with two levels of commission. It includes two virtual columns to display the commission-based salary. The first uses the most abbreviated syntax while the second uses the most verbose form. CREATE TABLE employees ( id NUMBER, first_name VARCHAR2(10), last_name VARCHAR2(10), salary NUMBER(9,2), comm1 NUMBER(3), comm2 NUMBER(3), salary1 AS (ROUND(salary*(1+comm1/100),2)), salary2 NUMBER GENERATED ALWAYS AS (ROUND(salary*(1+comm2/100),2)) VIRTUAL, CONSTRAINT employees_pk PRIMARY KEY (id) ); INSERT INTO employees (id, first_name, last_name, salary, comm1, comm2) VALUES (1, 'JOHN', 'DOE', 100, 5, 10); INSERT INTO employees (id, first_name, last_name, salary, comm1, comm2) VALUES (2, 'JAYNE', 'DOE', 200, 10, 20); COMMIT; Querying the table shows the inserted data plus the derived commission-based salaries. SELECT * FROM employees; ID FIRST_NAME LAST_NAME SALARY COMM1 COMM2 SALARY1 SALARY2 ---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- 1 JOHN DOE 100 5 10 105 110 2 JAYNE DOE 200 10 20 220 240 2 rows selected. SQL The expression used to generate the virtual column is listed in the DATA_DEFAULT column of the [DBA|ALL|USER]_TAB_COLUMNS views. COLUMN data_default FORMAT A50 SELECT column_name, data_default FROM user_tab_columns WHERE table_name = 'EMPLOYEES'; COLUMN_NAME DATA_DEFAULT ------------------------------ -------------------------------------------------- ID FIRST_NAME LAST_NAME SALARY COMM1 COMM2 SALARY1 ROUND("SALARY"*(1+"COMM1"/100),2) SALARY2 ROUND("SALARY"*(1+"COMM2"/100),2) 8 rows selected. SQL Notes and restrictions on virtual columns include: 1)Indexes defined against virtual columns are equivalent to function-based indexes. 2)Virtual columns can be referenced in the WHERE clause of updates and deletes, but they cannot be manipulated by DML. 3)Tables containing virtual columns can still be eligible for result caching. 4)Functions in expressions must be deterministic at the time of table creation, but can subsequently be recompiled and made non-deterministic without invalidating the virtual column. In such cases the following steps must be taken after the function is recompiled: a)Constraint on the virtual column must be disabled and re-enabled. b)Indexes on the virtual column must be rebuilt. c)Materialized views that access the virtual column must be fully refreshed. d)The result cache must be flushed if cached queries have accessed the virtual column. e)Table statistics must be regathered. 5)Virtual columns are not supported for index-organized, external, object, cluster, or temporary tables. 6)The expression used in the virtual column definition has the following restrictions: a.It cannot refer to another virtual column by name. b.It can only refer to columns defined in the same table. c.If it refers to a deterministic user-defined function, it cannot be used as a partitioning key column. e.The output of the expression must be a scalar value. It cannot return an Oracle supplied datatype, a user-defined type, or LOB or LONG RAW.
Views: 585 OracleDBA
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: 10075 R.N.A. Creation
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: 13216 Caleb Curry
Oracle Database11g tutorials 14 : How to CREATE TABLE using sql developer and command prompt
 
08:36
Oracle Database11g tutorials 14 How to Create table using command prompt and Create table using sql developer Blog Link http://bit.ly/1TkY4Oe Time Line 0:25 Introduction of Tables in Database 1:03 What is Create Table (Introduction of create table) 1:30 Syntax of Create Table 2:08 How to create table using Command Prompt 4:55 How to create table using SQL Developer Links for Oracle Database tutorials 4: database connectivity using SQL developer and command prompt http://youtu.be/wSqoXRlXDUU You can have indepth knowledge about SQL create table here http://www.rebellionrider.com/sql-create-table.html Tool used in this tutorial is command prompt. This tutorial series is part of SQL expert exam certification training. if you are preparing for SQL certification you can use my tutorials. This SQL Tutorial is a part of free training. Copy Cloud referral link || Use this link to join copy cloud and get 20GB of free storage https://copy.com?r=j7eYO7 Contacts E-Mail [email protected] Twitter https://twitter.com/rebellionrider Instagram http://instagram.com/rebellionrider Facebook. https://www.facebook.com/imthebhardwaj Linkedin. http://in.linkedin.com/in/mannbhardwaj/ Thanks for linking, commenting, sharing and watching more of our videos This is Manish from RebellionRider.com Today in this oracle database tutorial we will see How to CREATE A TABLE. if we have to define a table in layman language then we can say that Tables are just a collection of Rows and Columns but In RDBMS tables are database objects which help in organizing data into ROWS and COLUMNS. We can also say that SQL tables are kind of data structure which are used by database for efficient storage of data. To create a table in our database we use SQL CREATE TABLE command. SQL CREATE TABLE is a type of DATA DEFINITION LANGUAGE also known as DDL. To Create a table in your schema you will require CREATE TABLE system privilege. In our future videos we will see what are system and object privileges and how to grant them to a user. Today for this video we will be using Sample schema HR which already has all the necessary privileges. Ohk Let's see the syntax. CREATE TABLE table name ( column name1 Data-Type(size), column name2 Data-Type(size), ..... ); CREATE TABLE is an oracle reserved word or say an Oracle key word whereas There are 3 different ways of creating a table in Oracle database. Creating a table using Command Line Interface (CLI) in Oracle database For demonstrating how to create table in oracle database using CLI, I'll be using Command prompt. Thats how we create table using command prompt. you can check your table structure by DESCRIBE command for that just write DESC and your table name. Like this Another way of creating a table is by using Graphic user interface (GUI) in Oracle database To demonstrate how to create table using GUI we will use SQL developer. Lets open our SQL developer I am connected to HR schema if you do not know how to create a connection to database using SQL developer please watch my oracle database tutorial 4 that explains database connectivity using SQL developer and command prompt. Link for this video is in the description below. So lets create a table. Creating a table using SQL developer is very easy we do not have to fire any query here. Let's start First of all right click on your connection in which you want to create a table and choose schema browser. This will open a separate schema browser pane or you can expend your connection by clicking this + sign and then right click on table and choose New Table. However I prefer working with schema browser so let's skip to schema browser pane here from the first drop-down list you can choose connection name and in the second drop down list you can choose what database objects you want to work with we want to create a table thus I'll choose table and then click this arrow here and choose option for new table Ok we have created a table wizard first of all give a unique name to your table and add some column as well. For this, click the green plus button. Now we already have a column so give it some name. Also choose a datatype from the list and specify any size you can check this not null column if in case you want to make this a mandatory column you can also specify default value and constraint If you want to make this column a primary key you can click here In my future video i'll show you what are these constraints and different ways of applying them on a column in a table. for this video we will concentrate on create table only so when you are done with all your columns click ok Thats your table You can double click on your table here and can see its structure. Thats it
Views: 191509 Manish Sharma
Oracle SQL Tutorial 8 - Indexes - Database Design Primer 5
 
11:06
The concept of an index is extremely important when managing a database. An index has the power of making your database very quick or it has the power to bog down your update, delete, and insert statements. The trick is to find a good balance. You will want to index any columns that are used continually in a select or a join. By default, all primary keys are indexed as well as any columns with the UNIQUE column attribute. I suggest you consider adding an index to your foreign keys as these will often be used in joins as well. You can actually create an index on a group of columns. This will allow you to search for data and return multiple columns. This is known as a composite index. There are many other things to database design...much more than we have covered. I have decided I will cover these as we go so that we can start applying what we learn practically. 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: 20676 Caleb Curry