TABLE OF CONTENTS 0:00 - Intro 0:19 - Create Table Syntax 1:47 - Outline 3:11 - Where to put the table 4:48 - Naming the table 5:28 - Size of the Table 6:52 - Table Relationships 7:54 - Table Columns 11:29 - Data Types 12:47 - Varchar and NVarchar 14:37 - Number Data Types 20:26 - Date Types 21:56 - Adding Data Types to Columns 27:29 - Null and Not Null Columns 28:24 - Capitalizing Keywords and Best Practices 29:59 - Null and Not Null Columns Continued 31:48 - Primary Key Column 33:53 - Foreign Key Column 36:03 - Recap 36:56 - Table Permissions 38:18 - Run Create Table Statement 39:59 - Conclusion
4:13. You might want to mention to beginners the names of the naming conventions such as "camelCase", "PascalCase", and "snake_case". It would also be good to point out the reasons for using underscores instead of camel case when naming (and referring to tables and columns)- since the SQL query language isn't case sensitive, the separation of words with underscores can eliminate ambiguity and improve readability. Whatever naming convention is chosen, you just want to be sure to remain consistent within that database.
5:13. Yes, if your intention IS to use the dbo schema, it's best to be explicit if you're unsure what default schema will be used. I also wouldn't necessarily say that using the dbo schema is "best practice". It would be considered best practice most of the time- since most of the time you won't need a different schema (different schemas could be used if wanting to control permissions based on schema, for example).
TABLE OF CONTENTS
0:00 - Intro
0:19 - Create Table Syntax
1:47 - Outline
3:11 - Where to put the table
4:48 - Naming the table
5:28 - Size of the Table
6:52 - Table Relationships
7:54 - Table Columns
11:29 - Data Types
12:47 - Varchar and NVarchar
14:37 - Number Data Types
20:26 - Date Types
21:56 - Adding Data Types to Columns
27:29 - Null and Not Null Columns
28:24 - Capitalizing Keywords and Best Practices
29:59 - Null and Not Null Columns Continued
31:48 - Primary Key Column
33:53 - Foreign Key Column
36:03 - Recap
36:56 - Table Permissions
38:18 - Run Create Table Statement
39:59 - Conclusion
Excellent Training, I like that you setup a framework for someone to think about and then walk through each of the steps with a real example.
4:13. You might want to mention to beginners the names of the naming conventions such as "camelCase", "PascalCase", and "snake_case". It would also be good to point out the reasons for using underscores instead of camel case when naming (and referring to tables and columns)- since the SQL query language isn't case sensitive, the separation of words with underscores can eliminate ambiguity and improve readability. Whatever naming convention is chosen, you just want to be sure to remain consistent within that database.
The very best SQL training videos!!!!!! Thanks brother.
Excellent Training - I've watched it to the very end.
5:13. Yes, if your intention IS to use the dbo schema, it's best to be explicit if you're unsure what default schema will be used. I also wouldn't necessarily say that using the dbo schema is "best practice". It would be considered best practice most of the time- since most of the time you won't need a different schema (different schemas could be used if wanting to control permissions based on schema, for example).
Excellent!!!
TO INSTALL THIS PLAT FORM PLEASE LINK... I CANT FIND THE SUCH PLATFORM...PLEASE
What is Varchar because my name is varchas from India