1 00:01.910 --> 00:02.570 I am harshit. 2 00:03.170 --> 00:12.740 I have total ten plus years of experience in SQL, data migration, ETL and other, uh, SSIS as well. 3 00:13.220 --> 00:17.930 And I am working in the in majority of my projects. 4 00:17.930 --> 00:22.880 I have worked on the SQL related, uh, things. 5 00:23.450 --> 00:31.840 So we will cover over here SQL from basic to uh, advanced level as well as we will see some of the 6 00:31.840 --> 00:35.860 queries asked in the uh product based companies. 7 00:37.210 --> 00:39.340 So let me share my screen. 8 00:40.930 --> 00:45.070 And if you have any doubt or any query then you can ask me any time. 9 00:48.400 --> 00:51.640 Let me know once you are able to see my screen. 10 00:59.820 --> 01:01.410 You are able to see right? 11 01:04.530 --> 01:11.790 Okay, so we will see most of the things in SQL server only. 12 01:12.240 --> 01:17.450 So let me know if you have not installed SQL server in your system. 13 01:18.560 --> 01:21.470 I will let you know how we can install. 14 01:21.470 --> 01:25.250 These are the links I have mentioned over here. 15 01:25.370 --> 01:28.580 So let me open this first link. 16 01:31.340 --> 01:35.480 Because without without having the software we can't do anything right. 17 01:36.410 --> 01:37.550 So. 18 01:40.010 --> 01:41.620 So over here. 19 01:44.290 --> 01:45.100 Yeah. 20 01:45.280 --> 01:52.810 But for SQL Server Management Studio, we need to install a, uh, SQL engine as well. 21 01:52.810 --> 01:53.440 Right. 22 01:54.310 --> 01:57.910 So we need to install two different software. 23 01:58.360 --> 02:01.300 So I have right over here. 24 02:01.300 --> 02:02.860 First one is this one. 25 02:04.750 --> 02:05.860 Let me. 26 02:09.760 --> 02:12.220 So this is the first software right. 27 02:12.700 --> 02:18.280 So this is basically a SQL engine we are installing. 28 02:18.760 --> 02:25.090 Because in SSMs we can't do anything right without having our database right inbuilt database. 29 02:25.450 --> 02:35.310 So this will provide the inbuilt SQL engine and database to communicate with SSMs. 30 02:35.430 --> 02:38.460 So first one is you need to install is this one. 31 02:38.460 --> 02:41.970 And then second one you need to install is this one. 32 02:42.780 --> 02:46.110 This is called SSMs SQL Management Studio. 33 02:47.970 --> 02:51.030 So these two software you need to install. 34 02:51.030 --> 02:56.660 If you go to the download page then you it will showing over here, right? 35 02:56.660 --> 02:58.610 Choose the download you want. 36 02:58.970 --> 03:05.330 So what you want to do you need to select this one and you need to select this one. 37 03:08.390 --> 03:09.320 One minute. 38 03:17.380 --> 03:18.310 Uh, yes. 39 03:26.650 --> 03:26.830 Yeah. 40 03:26.830 --> 03:33.430 I will prefer to install the SQL server because maybe it's a syntactically difference. 41 03:33.430 --> 03:37.900 May be there in my SQL and SSMs SQL server. 42 03:38.410 --> 03:46.320 So we will I don't have my SQL as of now, so we will most of the things we will do in SQL server only, 43 03:47.130 --> 03:49.590 but the concept will be the same like. 44 03:57.120 --> 04:00.000 Ah yes yes sure I will provide the link as well. 45 04:07.370 --> 04:09.680 You are recording right now, I will not provide. 46 04:09.680 --> 04:13.820 But after, uh, few days, I will provide the recordings. 47 04:16.220 --> 04:16.580 Okay. 48 04:16.580 --> 04:19.520 I have put the links into the chat. 49 04:23.870 --> 04:29.120 Now, when you click on these two things, you need to directly go to the download. 50 04:29.830 --> 04:37.360 So both of the chapters will be downloaded right in your uh, download box. 51 04:37.570 --> 04:39.280 Sorry download folder. 52 04:40.330 --> 04:44.500 And then from over here you will install it one by one. 53 04:46.120 --> 04:52.330 So as of uh, I have already installed in my system, I am not installing again. 54 04:52.330 --> 04:56.580 But if you face any problem then you will let me know. 55 04:56.580 --> 04:59.850 I will happily help you to install this software. 56 05:03.690 --> 05:12.270 Or if you if any one of you do as of now, right now then also there will be no problem as per your 57 05:12.270 --> 05:13.080 choice. 58 05:28.230 --> 05:29.940 Yes, that will be fine. 59 05:30.090 --> 05:32.460 But maybe it will take some time. 60 05:32.850 --> 05:32.970 Uh. 61 05:32.970 --> 05:33.990 Let's see. 62 05:34.020 --> 05:35.490 Can anyone share the screen? 63 05:35.490 --> 05:36.510 And we will. 64 05:37.770 --> 05:41.100 You will download and then we will see how to install. 65 05:43.250 --> 05:46.220 If anyone share the screen then it will be fine. 66 05:50.810 --> 05:51.860 Okay. 67 05:54.380 --> 05:54.590 Yeah. 68 05:54.590 --> 05:55.220 Please share. 69 05:55.340 --> 05:57.860 Download uh and share the screen. 70 06:14.380 --> 06:14.950 Uh, sorry. 71 06:14.980 --> 06:16.090 Can you repeat? 72 06:28.240 --> 06:35.880 Actually, uh, for that, you need some good means, uh, good average configuration laptop. 73 06:35.880 --> 06:41.160 And it may slow, but for practice purpose, it is necessary, right? 74 06:41.160 --> 06:45.960 Because without installing software, we cannot do the practice. 75 06:45.960 --> 06:46.590 Right. 76 06:51.030 --> 06:57.560 Just understanding the concept and better to do practice that will make the difference, right? 77 06:59.480 --> 07:02.270 So not not huge difference actually. 78 07:02.660 --> 07:07.610 Uh, my laptop is working very good even though I have so many softwares. 79 07:12.950 --> 07:17.360 So again, anyone sharing the screen or we will move forward. 80 07:18.340 --> 07:19.540 Whatever is. 81 07:21.670 --> 07:22.390 Yes. 82 07:29.470 --> 07:30.880 A yes, that is fine. 83 07:30.880 --> 07:31.510 Yes, yes. 84 07:34.360 --> 07:38.080 You are able to, uh, create tables and execute queries. 85 07:38.080 --> 07:39.160 Everything right? 86 07:40.720 --> 07:40.990 Yeah. 87 07:40.990 --> 07:41.470 Yeah. 88 07:41.790 --> 07:42.420 Okay, okay. 89 07:42.420 --> 07:43.290 That is fine. 90 07:55.740 --> 07:56.040 Okay. 91 07:56.040 --> 07:58.380 I think someone has said the screen. 92 08:01.230 --> 08:01.680 Okay. 93 08:01.680 --> 08:03.090 Go to the download. 94 08:08.180 --> 08:12.740 If it is taking time then we will move forward and understand the concepts. 95 08:13.640 --> 08:14.720 Uh, parallelly. 96 08:19.370 --> 08:19.820 Okay. 97 08:19.820 --> 08:21.650 Till it is downloaded, we will. 98 08:30.530 --> 08:31.010 Okay. 99 08:31.010 --> 08:34.700 So let's move forward. 100 08:36.260 --> 08:41.540 So let's uh, start with the very basic concepts like what is a database? 101 08:42.470 --> 08:51.050 So can anyone tell me in, uh, your language or your understanding what we can say is a database. 102 08:51.080 --> 08:54.280 My screen is visible. 103 08:54.280 --> 08:54.910 Okay. 104 08:55.810 --> 08:58.180 Can anyone tell me what is a database? 105 09:24.540 --> 09:25.380 Okay. 106 09:27.300 --> 09:28.830 There anyone else? 107 09:31.440 --> 09:32.490 So. 108 09:34.440 --> 09:35.310 Yes. 109 09:42.500 --> 09:43.190 Okay. 110 09:43.850 --> 09:44.480 Uh, yeah. 111 09:44.480 --> 09:45.140 Right. 112 09:45.260 --> 09:52.880 So we can say that database, uh, is a organized collection of data, organized collection of data 113 09:52.880 --> 09:55.730 that can be easily accessed and managed. 114 09:56.330 --> 09:58.100 So we can say that. 115 09:58.100 --> 10:02.510 And it is also a collection of different objects, not only tables. 116 10:02.510 --> 10:02.810 Right. 117 10:02.810 --> 10:07.000 Someone has mentioned only tables, but it is a collection of tables. 118 10:07.000 --> 10:15.430 Then you can say that other objects like store procedures, functions, then, uh, synonyms, then 119 10:15.430 --> 10:16.330 views. 120 10:18.340 --> 10:20.620 Then we can say that, uh, triggers. 121 10:20.620 --> 10:28.360 So this database is a collection of different objects, uh, which we, which can be easily managed 122 10:28.360 --> 10:33.510 and accessed through the, some of the some of the user interface software. 123 10:33.960 --> 10:42.960 And over here we have the user interface software that is known as a SSMs, SQL Server Management studio. 124 10:42.960 --> 10:43.530 Right. 125 10:45.270 --> 10:52.860 So, so without SSMs we cannot manage how how we can manage these tables, how we can manage these stored 126 10:52.860 --> 10:53.730 procedures. 127 10:54.140 --> 11:03.200 So this is a user interface software which is a helpful tool to communicate with the database. 128 11:03.200 --> 11:03.860 Right. 129 11:06.200 --> 11:09.410 And uh, yeah. 130 11:09.410 --> 11:11.870 If anyone has any question they can ask. 131 11:16.670 --> 11:20.440 And then for that purpose we need to install the SQL server. 132 11:20.530 --> 11:23.860 So over here we need to install two different things. 133 11:24.220 --> 11:30.040 This is known as SQL Database engine right. 134 11:30.040 --> 11:32.800 And this is a user interface. 135 11:36.190 --> 11:37.870 User interface software. 136 11:37.870 --> 11:40.360 So only this one will not work. 137 11:40.360 --> 11:42.750 And only this one will will not work. 138 11:43.350 --> 11:49.650 So both of the things are mandatory to work with SQL server, right? 139 11:56.220 --> 11:58.920 Now let me know if you have any question. 140 12:05.550 --> 12:06.240 Okay. 141 12:06.240 --> 12:06.840 Yeah. 142 12:06.840 --> 12:12.930 So, uh, so, um, we can say that, uh, there are mainly two types of databases. 143 12:12.930 --> 12:17.820 Are there, which one is OLTP and one is OLAp. 144 12:18.330 --> 12:20.580 So what do you mean by OLTP. 145 12:21.720 --> 12:23.880 So we can say that online. 146 12:24.780 --> 12:25.710 Uh, yes. 147 12:27.690 --> 12:28.170 Uh yes. 148 12:28.170 --> 12:28.560 Right. 149 12:28.560 --> 12:30.390 Online transaction processing. 150 12:31.580 --> 12:34.010 in OLAp means. 151 12:36.290 --> 12:40.340 Online analytical processing. 152 12:40.580 --> 12:47.450 Now if you see online transaction processing is processing. 153 12:47.450 --> 12:53.210 So whenever we whenever we go to the bank. 154 12:53.450 --> 12:59.080 So bank is the banking is the perfect example of online transaction processing, right? 155 12:59.440 --> 13:03.940 Because in the bank, every day or day to day transactions are happening. 156 13:03.940 --> 13:04.450 Right? 157 13:07.090 --> 13:10.390 Day to day, day to day transactions are happening each day. 158 13:10.420 --> 13:14.710 Many customers are coming to the banks and they are withdrawing the amount. 159 13:14.710 --> 13:17.710 Then, uh, crediting the amount. 160 13:17.710 --> 13:18.190 So. 161 13:19.140 --> 13:24.450 So I will show you one, uh, image I have with me. 162 13:24.930 --> 13:27.120 So let me show you that image. 163 13:30.900 --> 13:32.370 So if you see. 164 13:32.370 --> 13:38.820 Right, uh, bank has a different, different types of accounts are there, right. 165 13:39.450 --> 13:43.670 Like saving account, current account, then, uh, different customers. 166 13:43.670 --> 13:44.210 Ah. 167 13:45.230 --> 13:45.620 Uh. 168 13:56.690 --> 13:58.910 No, I am already presenting. 169 13:59.270 --> 14:01.070 Uh, are you able to see my screen? 170 14:01.820 --> 14:02.660 Everyone. 171 14:07.720 --> 14:09.700 Okay, let me share it again. 172 14:20.290 --> 14:22.840 Now, I think you should able to see. 173 14:25.690 --> 14:32.730 Okay, so, uh, this is a perfect example of OLTP system. 174 14:33.690 --> 14:40.470 So in the, uh, banking, we whenever we different customers are there, right in the bank. 175 14:40.830 --> 14:47.190 So all of our, all of the customers has their personal informations are there uh, with the bank. 176 14:47.190 --> 14:47.790 Right. 177 14:49.290 --> 14:57.350 So that customer personal information will be stored in the one table like customer ID, customer name, 178 14:57.350 --> 14:58.340 phone number. 179 14:58.460 --> 15:02.660 Then their customers have, uh, different accounts are there, right? 180 15:02.960 --> 15:03.710 So. 181 15:03.710 --> 15:04.550 So sorry. 182 15:04.550 --> 15:11.120 One customer is maybe multiple accounts or must multiple different types of accounts will be there. 183 15:11.150 --> 15:15.710 So their account ID will be also separated in the separate table. 184 15:15.710 --> 15:16.070 Right. 185 15:16.070 --> 15:17.870 Maintain in the separate table. 186 15:18.140 --> 15:22.220 So for that this is a separate table called accounts. 187 15:22.610 --> 15:24.680 So their account ID will be there. 188 15:24.680 --> 15:28.250 Then what kind of account name will be there. 189 15:28.610 --> 15:34.340 Then when the customer is open that particular account so that date will be there. 190 15:34.340 --> 15:41.270 And then if you see over here customer ID in the customer table is a primary key over here. 191 15:42.290 --> 15:43.940 We will show all this thing. 192 15:44.030 --> 15:44.930 Primary key. 193 15:44.930 --> 15:47.660 Foreign key in, uh, detail level. 194 15:47.660 --> 15:50.030 But for now, understanding purpose. 195 15:50.750 --> 15:57.230 I am just showing you customer ID is primary key in customer table where it has the same customer ID 196 15:57.230 --> 15:59.420 is foreign key in the accounts table. 197 16:00.770 --> 16:04.940 So like primary key foreign key relationships are also maintained. 198 16:05.930 --> 16:06.680 Right. 199 16:07.200 --> 16:12.540 Then, uh, what kind of purchases customer has done, like purchase ID? 200 16:12.930 --> 16:16.440 So for that purpose, another table has been maintained. 201 16:16.740 --> 16:20.580 Now again, what kind of transaction a customer has done. 202 16:20.580 --> 16:26.370 So all every transaction has a one transaction ID attached with it. 203 16:26.370 --> 16:27.000 Right. 204 16:27.210 --> 16:29.700 So for that transaction ID is maintained then. 205 16:29.700 --> 16:33.350 And what date particular transaction is done then. 206 16:33.350 --> 16:34.490 Amount of transaction. 207 16:34.490 --> 16:38.240 Let let's see how much 5000 amount has been withdrew. 208 16:38.360 --> 16:43.430 So 5000 will be maintained over here in the transaction table. 209 16:44.870 --> 16:46.790 So this is you can say this. 210 16:46.790 --> 16:49.940 This is the perfect example of OLTP system. 211 16:57.430 --> 17:02.170 And the other one is a ol AP, right? 212 17:02.410 --> 17:06.790 So ol AP means over here aggregate. 213 17:09.340 --> 17:16.570 Data has been maintained for the reporting purpose. 214 17:16.600 --> 17:25.440 So suppose if you do the reporting on the online transaction processing, then it will be a huge amount 215 17:25.440 --> 17:26.340 of data right? 216 17:26.340 --> 17:33.270 In online transaction processing every day bank has lots of transactions for lots of customers are there. 217 17:33.660 --> 17:37.020 So it is not it is not. 218 17:38.700 --> 17:40.170 We can say it is not. 219 17:40.170 --> 17:49.520 Consider consider for the reporting purpose because the data is uh, data is huge amount of data. 220 17:49.520 --> 17:58.520 So if we do the reporting or if we connect the power BI, uh, with this, uh, transaction tables, 221 17:58.670 --> 18:03.530 then our power BI report will be stopped, right? 222 18:03.530 --> 18:07.480 Or it will take a huge amount to open, even open the report. 223 18:07.990 --> 18:19.060 But what if we if we have the like, aggregate information like, uh, per quarter, per quarter data? 224 18:19.060 --> 18:23.620 Or we can say that per a monthly data or yearly data. 225 18:23.620 --> 18:24.250 Right. 226 18:25.540 --> 18:31.000 Then this data will be generated on the this, uh. 227 18:32.080 --> 18:38.770 transaction table, but it will be considered as a OLAp like online analytical processing. 228 18:39.340 --> 18:49.210 And if we have this amount of, uh, data in any kind of, uh, tables, or we can say that we use then 229 18:49.210 --> 18:58.890 this, we can say that this report we can the file size Can you tell me the file size of this report 230 18:58.890 --> 19:00.420 will be larger or. 231 19:00.630 --> 19:02.250 This report will be larger. 232 19:02.880 --> 19:04.380 In power BI or. 233 19:06.930 --> 19:08.730 You are OLTP will be larger. 234 19:08.730 --> 19:09.270 Right. 235 19:09.270 --> 19:13.320 Because it is row wise each of the row data. 236 19:13.710 --> 19:19.320 But if we have the data into the this format then file size will be smaller. 237 19:19.340 --> 19:23.660 and also for reporting purpose this one will be more preferred. 238 19:24.320 --> 19:24.710 Right? 239 19:24.740 --> 19:26.780 Aggregate data will be more preferred. 240 19:36.080 --> 19:36.650 Uh, yes. 241 19:36.650 --> 19:36.860 Yes. 242 19:36.860 --> 19:38.300 Now you can hear me, right? 243 19:40.880 --> 19:41.690 Okay. 244 19:43.660 --> 19:44.050 Yeah. 245 19:44.380 --> 19:50.020 So, uh, file size will be more in OLTP than in. 246 19:52.540 --> 19:52.900 Yeah. 247 19:52.900 --> 19:53.770 One minute. 248 19:56.410 --> 19:56.590 Yeah. 249 19:56.590 --> 19:56.890 Now. 250 19:56.890 --> 19:57.190 Clear. 251 19:57.190 --> 19:57.760 Right. 252 20:00.490 --> 20:01.210 Okay. 253 20:02.200 --> 20:06.790 So reporting purpose always OLAp is more preferred than the OLTP. 254 20:06.790 --> 20:07.150 Right. 255 20:07.150 --> 20:15.480 So that's where that's why we are creating OLAp database as well while doing the any kind of reporting. 256 20:19.830 --> 20:24.870 Now let's see what are the different types of data are there with us. 257 20:25.050 --> 20:28.440 So previously we have mostly the structured data. 258 20:28.440 --> 20:29.340 Are there right. 259 20:29.640 --> 20:34.520 Structured data means what the image we have seen just. 260 20:36.860 --> 20:39.920 So this one we can say that a structured data. 261 20:39.920 --> 20:40.490 Right. 262 20:40.490 --> 20:49.580 Because how we can say this structured data because every different categorized data are stored in the 263 20:49.580 --> 20:50.840 different tables. 264 20:51.140 --> 20:53.960 That is why it is known as a structured data. 265 20:54.440 --> 21:01.990 But nowadays we can say that the unstructured data and semi-structured data are also there. 266 21:02.080 --> 21:09.640 So can anyone tell me which is the example of semi-structured data and which is the example of unstructured 267 21:09.640 --> 21:10.240 data? 268 21:20.910 --> 21:21.450 Yeah. 269 21:21.480 --> 21:22.470 Column names? 270 21:22.680 --> 21:23.970 Uh, yes. 271 21:24.840 --> 21:25.350 Yeah. 272 21:25.350 --> 21:26.730 Column names are. 273 21:40.530 --> 21:41.280 Yeah. 274 21:45.770 --> 21:46.280 Yeah. 275 21:46.280 --> 21:53.630 Files, audio, videos, images, PDF docs. 276 21:53.630 --> 21:57.380 These are called unstructured data and semi-structured data. 277 21:57.380 --> 22:02.060 I think columns will be there, but it will be not in the tabular format. 278 22:02.060 --> 22:04.250 You can perfect example of this. 279 22:04.250 --> 22:07.430 Semi-structured data is JSON. 280 22:09.950 --> 22:17.780 Is a semi-structured data in which columns will be there, but it is not in the tabular format, right? 281 22:20.600 --> 22:21.050 Yeah. 282 22:21.050 --> 22:23.810 Maybe it will, uh, be like this one. 283 22:23.810 --> 22:35.660 I can we can say like this, then you can say that name, then like, uh Hershey, then Empid one, 284 22:35.660 --> 22:37.280 then this will be the first record. 285 22:37.280 --> 22:42.560 Then again, maybe second record will be start like this and like this. 286 22:43.070 --> 22:46.850 Mostly this kind of JSON formats are there, right? 287 22:49.280 --> 22:53.090 Uh, again we can say that employee this is employee table. 288 22:53.570 --> 22:56.520 Then these are the columns. 289 22:56.520 --> 22:59.010 Then again this is first record. 290 22:59.040 --> 23:00.690 Then this is second record. 291 23:01.200 --> 23:04.530 And this employee table will be closing over here. 292 23:05.040 --> 23:06.510 So this is employee table. 293 23:06.510 --> 23:09.720 Two columns are there and two records are there. 294 23:09.840 --> 23:11.010 We can say. 295 23:15.480 --> 23:19.620 In the distinct record means uh ID one and ID two. 296 23:19.620 --> 23:20.210 right? 297 23:20.300 --> 23:25.460 So this is normally a JSON format and that is known as a semi-structured data. 298 23:26.840 --> 23:29.990 So these are mostly the types of data are there. 299 23:30.890 --> 23:34.580 Now let's see the fact table and the dimension table. 300 23:34.880 --> 23:37.520 So let's come again with this image. 301 23:37.520 --> 23:47.050 And can anyone tell me any idea about fact table which is the fact table over here from this diagram. 302 24:08.670 --> 24:10.800 Okay, so which is the fact table over here? 303 24:15.840 --> 24:18.780 Um, no, I think yeah. 304 24:23.130 --> 24:23.670 Uh, yes. 305 24:23.670 --> 24:24.090 Right. 306 24:24.090 --> 24:32.720 Only I think only transactions is the fact table and all others are the we can say that dimension table. 307 24:33.260 --> 24:33.710 Why? 308 24:33.740 --> 24:38.330 Because if you see over here one minute. 309 24:40.580 --> 24:45.950 Because if you see over here, if you see, uh, in the customers table. 310 24:45.950 --> 24:46.490 Right. 311 24:46.730 --> 24:52.790 Primary key or customer table, primary key are there then maybe unique customer ID will be assigned 312 24:52.820 --> 24:55.190 to all of the customers, right. 313 24:55.400 --> 24:59.300 Name may be duplicate, but customer ID will be unique, right? 314 25:00.500 --> 25:05.870 So it is only containing the detailed information of all of the customers. 315 25:06.350 --> 25:08.270 Then if you see the account types. 316 25:08.270 --> 25:11.780 So account types what are the different accounts. 317 25:11.780 --> 25:12.410 Are there. 318 25:12.410 --> 25:14.600 So s a means saving account. 319 25:14.870 --> 25:16.730 Then CA means current account. 320 25:16.730 --> 25:20.920 So again it will be the dimension table will be there. 321 25:20.920 --> 25:21.490 Right. 322 25:25.720 --> 25:36.850 But if you see over here in the accounts as well, if you see so there is no different accounts or different 323 25:36.850 --> 25:38.200 customer accounts are there. 324 25:38.200 --> 25:38.770 Right. 325 25:38.920 --> 25:47.880 But there is no specific transaction like you can say that there is no any amount related fields, are 326 25:47.880 --> 25:51.240 there right in the accounts table. 327 25:52.080 --> 25:55.800 So that one we can also consider as a dimension table. 328 25:55.800 --> 26:02.880 But if you see over in here in the transactions table, all of there is only one transaction key is 329 26:02.880 --> 26:03.390 there. 330 26:09.170 --> 26:13.070 is one only one transaction ID, so that is fine. 331 26:13.190 --> 26:18.020 It is maintaining the transaction details of all the transactions. 332 26:18.230 --> 26:24.710 But if you see over here purchase ID, account ID and transaction type code and also amount is mentioned 333 26:24.710 --> 26:26.540 right amount of transaction. 334 26:27.470 --> 26:36.880 So for that purpose transactions we can say that as a fact table because in the transaction table mostly 335 26:37.030 --> 26:37.540 sorry. 336 26:37.540 --> 26:47.110 In the fact table, mostly all the table's primary key will be stored as a foreign key in the transaction 337 26:47.110 --> 26:47.770 table. 338 26:47.980 --> 26:50.980 And that is we can consider as a fact table. 339 26:51.460 --> 26:55.900 But whenever in the dimension table only mostly the primary keys are there. 340 26:55.920 --> 26:56.490 right? 341 26:58.740 --> 27:04.020 So foreign key is there, but there it is just for the reference purpose. 342 27:04.500 --> 27:08.040 There is no meaning of foreign key merchant ID in this table. 343 27:08.640 --> 27:13.560 It is only used for the reference to connecting two different tables. 344 27:14.580 --> 27:15.210 Right. 345 27:20.180 --> 27:25.250 So is the fact table and dimension table concepts are clear. 346 27:34.670 --> 27:35.120 Yeah. 347 27:35.120 --> 27:45.160 So we can easily say that whichever table we are using for the sum of the calculation purpose, right? 348 27:45.250 --> 27:54.940 Like, uh, if I am a customer of the bank, then in within a month, how much amount I have withdrawn 349 27:55.810 --> 28:00.190 and how much amount I have credited in one month. 350 28:00.700 --> 28:04.480 So how we can check that data. 351 28:04.480 --> 28:07.600 So for that data we need to go to the transaction table. 352 28:07.600 --> 28:08.080 Right. 353 28:08.490 --> 28:21.000 So over here we can say that in the transaction table or my uh customer ID my entire one month data 354 28:21.000 --> 28:21.570 will be there. 355 28:21.570 --> 28:22.140 Right. 356 28:22.770 --> 28:26.730 So amount of transaction of one month. 357 28:27.150 --> 28:31.980 And if we can say that, uh, transaction type code, it means like withdraw. 358 28:31.980 --> 28:35.280 So in one month, how much amount I have withdrawn. 359 28:35.520 --> 28:38.370 We can consider from this transaction table. 360 28:38.370 --> 28:38.910 Right. 361 28:39.420 --> 28:48.840 So that is known as a fact table because some we are doing some some of the you can say that some we 362 28:48.840 --> 28:51.540 will use some aggregate function in this transaction table. 363 28:51.540 --> 28:52.080 Right. 364 28:52.410 --> 28:58.490 But can we use the aggregate function in the customer table or is it meaningful to use the aggregate 365 28:58.490 --> 29:00.260 function in the customer table? 366 29:01.040 --> 29:02.660 Can anyone say that? 367 29:03.260 --> 29:04.430 Is it meaningful? 368 29:06.350 --> 29:07.610 Yeah, right. 369 29:07.640 --> 29:09.260 It is not meaningful. 370 29:09.260 --> 29:09.830 Right. 371 29:09.860 --> 29:11.390 So all these. 372 29:11.390 --> 29:13.910 That is why customer is a dimension table. 373 29:13.910 --> 29:18.260 It is providing the dimension to connect with the transaction table. 374 29:18.290 --> 29:27.760 But we are mostly we are using our aggregations or any type of aggregations on the fact table, right? 375 29:28.540 --> 29:33.820 That is why transaction is known as a fact table, not the dimension table. 376 29:36.340 --> 29:36.730 Okay. 377 29:36.730 --> 29:38.410 In one you can say that again. 378 29:38.410 --> 29:44.880 One example like uh customer account types, you can say, so what are the different accounts are available 379 29:44.880 --> 29:51.510 in the bank like savings account, current account, fixed deposit account, recurring account. 380 29:51.630 --> 29:55.920 So these are the different accounts are unique values are there. 381 29:55.920 --> 29:56.460 Right. 382 29:57.270 --> 30:03.090 So that is why account type will be considered as a what kind of table. 383 30:08.840 --> 30:10.160 Dimension or fact. 384 30:16.070 --> 30:17.810 No, no, it will be dimension. 385 30:17.810 --> 30:19.040 It will be dimension. 386 30:19.040 --> 30:19.670 Table. 387 30:21.920 --> 30:23.990 There is no fact information, are there? 388 30:23.990 --> 30:24.470 Right? 389 30:24.560 --> 30:29.420 Is there any amount or are we doing any aggregation on this account type table? 390 30:29.420 --> 30:29.900 No. 391 30:29.900 --> 30:30.470 Right. 392 30:31.190 --> 30:35.830 It has a unique value of different accounts available in the bank. 393 30:36.910 --> 30:39.640 So it will be a dimension table only, right? 394 30:39.670 --> 30:40.870 Not the fact table. 395 30:44.980 --> 30:46.300 Are you getting. 396 30:50.830 --> 30:51.220 Okay. 397 30:53.890 --> 30:56.140 You just need to remember one thing. 398 30:56.320 --> 31:04.080 In which table we will be doing our aggregation transformation for the reporting purpose. 399 31:05.820 --> 31:14.760 From this diagram, in which table we will be doing our aggregation, transformation or aggregation 400 31:14.760 --> 31:17.580 function for reporting purpose. 401 31:17.610 --> 31:19.740 Can you tell me in which table? 402 31:21.920 --> 31:22.430 Yes. 403 31:22.430 --> 31:24.170 Only transactions table. 404 31:24.170 --> 31:28.280 So that is why transaction table will be known as a fact table. 405 31:32.810 --> 31:40.790 But but rest of the tables are giving us the information regarding unique customers detail. 406 31:40.790 --> 31:45.220 Then unique account details, then unique merchant details. 407 31:45.220 --> 31:45.880 Right? 408 31:50.230 --> 31:51.700 Please be on mute. 409 31:51.730 --> 31:52.930 Uh, please be on mute. 410 31:59.290 --> 32:03.340 So that is why all these are the dimension tables. 411 32:07.030 --> 32:08.110 Except transactions. 412 32:08.110 --> 32:08.500 Tables. 413 32:08.500 --> 32:08.500 stables. 414 32:08.500 --> 32:09.130 Now. 415 32:09.130 --> 32:09.820 Clear. 416 32:26.740 --> 32:27.250 Okay, okay. 417 32:27.250 --> 32:27.730 We will. 418 32:27.730 --> 32:29.710 Maybe we will see you in the future. 419 32:29.710 --> 32:31.630 A few more examples as well. 420 32:33.360 --> 32:34.020 Yeah. 421 32:40.740 --> 32:43.170 Now we have seen this online. 422 32:45.660 --> 32:46.710 OLTP, OLAp. 423 32:46.740 --> 32:48.090 It is written over here, right? 424 32:48.120 --> 32:50.460 OLAp is good for analysis purpose. 425 32:50.850 --> 32:53.280 Analysis means we can say that. 426 32:56.400 --> 32:57.470 Reporting purpose. 427 32:57.470 --> 33:03.410 Right now, data will be of, uh, two different types that we have also seen. 428 33:04.850 --> 33:06.770 Now creating a table. 429 33:07.850 --> 33:10.730 So mostly we will start with the creating tables. 430 33:10.730 --> 33:14.270 Then we will adding the constraint into the tables. 431 33:14.270 --> 33:23.680 Then we will see the how constraints are effective Effective use of the constraints. 432 33:23.680 --> 33:26.560 Then we will see the normalization. 433 33:26.590 --> 33:29.170 What are the different types of normalization. 434 33:29.170 --> 33:30.070 We will see. 435 33:30.310 --> 33:32.230 So let us see the creating a table. 436 33:32.230 --> 33:34.750 What are the basic rules for creating a table. 437 33:37.450 --> 33:45.660 So the basic rule for the creating the tables are always recommend to start the table name with the 438 33:45.660 --> 33:46.560 alphabet. 439 33:46.860 --> 33:49.410 Now let me try. 440 33:49.440 --> 33:53.250 Are we able to use with numeric value or not? 441 33:53.250 --> 34:07.410 Like uh imp then imp id integer imp name where cur of ten is is this allowed or not? 442 34:15.680 --> 34:18.950 No, it is starting from the alphabet, right? 443 34:19.550 --> 34:21.290 So yeah, right. 444 34:21.290 --> 34:22.490 It is not allowing. 445 34:22.760 --> 34:24.380 But if I. 446 34:26.570 --> 34:29.630 Do like this now. 447 34:37.900 --> 34:38.080 What? 448 34:38.350 --> 34:39.400 Okay. 449 34:40.600 --> 34:41.740 It is allowing me. 450 34:41.740 --> 34:42.340 Right? 451 34:43.390 --> 34:44.050 But. 452 34:44.050 --> 34:47.500 But it is a, uh, wrong practice. 453 34:47.500 --> 34:51.370 I just show you different examples to your understanding. 454 34:51.370 --> 34:51.910 Right? 455 34:52.690 --> 34:56.980 Now, if I run this query, then it will show me the blank table. 456 34:57.360 --> 34:59.730 But it is not a good practice. 457 35:02.160 --> 35:02.490 Right. 458 35:02.490 --> 35:04.680 It is not a good practice. 459 35:08.730 --> 35:11.850 Always recommend to start the table with the alphabet. 460 35:11.850 --> 35:17.250 So always start with like this only not like numeric. 461 35:21.310 --> 35:29.710 Right now 128 128 characters can be used for the table name, where 128 characters can be used for the 462 35:29.710 --> 35:30.550 column name. 463 35:30.580 --> 35:32.020 What does it mean? 464 35:32.020 --> 35:36.370 Means if you use like this, like this one. 465 35:36.640 --> 35:38.440 So this is a character, right? 466 35:38.530 --> 35:42.670 So this length should be 128 characters. 467 35:44.680 --> 35:51.680 So the best practice, I am telling you for the best practice, not more than 128 characters over here 468 35:51.680 --> 35:55.670 and not more than 128 characters over here as well. 469 35:57.920 --> 36:03.230 Because ideally 128 is also very large, right? 470 36:08.600 --> 36:09.230 Yeah. 471 36:09.430 --> 36:16.630 so always 128 characters can be used for double name means less than you can say that. 472 36:16.630 --> 36:17.500 Less than. 473 36:19.990 --> 36:23.710 And less than 128 characters can be used for. 474 36:25.930 --> 36:27.010 Column name. 475 36:27.010 --> 36:28.690 Now one more thing. 476 36:29.200 --> 36:32.500 We can have only 1024 column in a table. 477 36:34.470 --> 36:39.420 So ideally it will be less than 1024 only. 478 36:39.420 --> 36:44.250 But sometimes maybe it has a in Excel file right. 479 36:44.250 --> 36:49.140 Sometimes maybe from the csv file we are trying to create a table. 480 36:49.530 --> 37:00.830 But what if in the CSV file one zero column information will be more than 1024 then it will be giving 481 37:00.830 --> 37:01.880 us the error. 482 37:03.470 --> 37:11.030 It will not allow SQL server wait, or maybe Oracle SQL will be also will not allow to create a table 483 37:11.030 --> 37:12.620 more than 1024. 484 37:13.430 --> 37:15.500 So it is a thumb rule, right? 485 37:15.500 --> 37:18.710 You need to follow this uh practice. 486 37:19.940 --> 37:24.910 Now let's create one table I think I have already created. 487 37:28.120 --> 37:30.520 Now, can anyone tell me why? 488 37:31.120 --> 37:31.720 Over here. 489 37:31.720 --> 37:32.020 Red. 490 37:32.020 --> 37:33.340 Red line is coming. 491 37:48.960 --> 37:49.590 Uh, yes. 492 37:49.590 --> 37:49.890 Right. 493 37:49.890 --> 37:57.000 So if you if you see over here, there is already an object name EMP in the database, right. 494 37:57.450 --> 38:04.440 So now let me first show you before this table creation, let me show you the different types of commands 495 38:04.440 --> 38:05.730 in SQL server. 496 38:08.130 --> 38:13.880 So if you see over here you can see this image right in my screen. 497 38:16.730 --> 38:21.080 So there are mainly five different types of commands are there. 498 38:23.300 --> 38:29.660 DDL command data definition language then DML command data manipulation language. 499 38:29.660 --> 38:33.860 Then data control language, then transaction control and data query language. 500 38:34.780 --> 38:38.020 So data DDL commands. 501 38:38.020 --> 38:47.230 So whenever we are creating, whenever we are creating any object in the database, or when we are altering 502 38:47.230 --> 38:55.150 any object in the database, and when we are removing object, any object permanently into the database 503 38:55.150 --> 39:00.310 that is known as a DDL command data definition language command. 504 39:00.850 --> 39:05.980 We will see example of each and every one from the coming classes. 505 39:06.400 --> 39:07.780 But this is the. 506 39:07.900 --> 39:10.480 I am telling you in the high level right. 507 39:10.720 --> 39:12.190 So create table right. 508 39:12.190 --> 39:16.210 Create table or create store procedure or drop the store procedure. 509 39:16.450 --> 39:19.750 Or if the table is already created right. 510 39:20.770 --> 39:24.840 If the table is already created, then what if? 511 39:24.840 --> 39:27.480 Suppose let me give you one example. 512 39:29.520 --> 39:31.590 This is the EMP table, right? 513 39:32.100 --> 39:36.240 So what if I want to add phone number over here in this table? 514 39:38.730 --> 39:41.610 Now can anyone tell me what I have to do? 515 39:45.240 --> 39:45.960 No, no. 516 39:45.960 --> 39:48.230 But, uh, let me tell you now. 517 39:48.230 --> 39:49.940 Let me show you over here. 518 39:50.270 --> 39:51.650 Let me drop this table. 519 39:51.650 --> 39:52.310 Drop. 520 39:55.370 --> 39:55.940 Table. 521 39:55.940 --> 39:56.570 EMP. 522 40:00.020 --> 40:02.270 Now, let me create this table. 523 40:04.130 --> 40:04.640 Okay. 524 40:04.640 --> 40:07.010 Now I want to add phone number then. 525 40:14.320 --> 40:15.130 Yeah. 526 40:15.130 --> 40:16.300 So yeah. 527 40:16.300 --> 40:16.840 Perfect. 528 40:16.840 --> 40:19.900 So we will see the example I am just showing you. 529 40:19.900 --> 40:22.240 So alter is a DDL command. 530 40:22.240 --> 40:22.420 Right. 531 40:22.420 --> 40:31.510 Because we are adding any information or any kind of information further into the already existing table. 532 40:31.930 --> 40:36.210 So that is why alter is also the part of the DDL command. 533 40:36.900 --> 40:46.500 Now, now suppose sometimes someone will tell that the manager information is not required in the employee 534 40:46.500 --> 40:47.040 table. 535 40:47.790 --> 40:49.950 Then we need to what we need to do. 536 40:49.980 --> 40:51.210 Can you tell me? 537 40:53.520 --> 40:54.240 Yeah right. 538 40:54.240 --> 40:55.710 We need to drop that column. 539 40:55.710 --> 41:06.620 So again drop is a DDL command right now let's see the example of that means let's see whenever the 540 41:06.620 --> 41:09.050 table is already available with us. 541 41:09.050 --> 41:09.650 Right. 542 41:10.160 --> 41:11.480 So it is a blank table. 543 41:11.480 --> 41:11.720 Right. 544 41:11.720 --> 41:15.320 But we are inserting some data into the table. 545 41:16.190 --> 41:18.800 So let me insert the data. 546 41:21.830 --> 41:24.460 We will see everything in more detail level. 547 41:25.300 --> 41:27.490 I just show you this example. 548 41:27.490 --> 41:32.170 So this data is now available right into this particular table. 549 41:32.710 --> 41:36.400 Select star from EMP. 550 41:37.570 --> 41:42.850 So so now insert will be the part of the DML statement. 551 41:42.850 --> 41:43.360 Right. 552 41:43.570 --> 41:47.220 We are doing some data manipulation in the table. 553 41:47.670 --> 41:53.970 So that is why Insert will be the part of the DML statement. 554 41:54.480 --> 41:58.890 Then suppose in the future we need to increase the salary of some. 555 42:00.600 --> 42:07.830 Increase the salary of the all the department, all the employees working in the department. 556 42:07.830 --> 42:08.850 20 right. 557 42:09.630 --> 42:11.580 I will give you one example. 558 42:17.910 --> 42:25.560 Sometimes we need to we have a requirement to increase the salary of all the employees working in the 559 42:25.560 --> 42:30.150 department, and we want to increase by ₹1,000. 560 42:30.180 --> 42:32.580 So what is that kind of command? 561 42:35.420 --> 42:36.590 That is the update statement. 562 42:36.590 --> 42:39.350 And update is a part of DML statement. 563 42:39.980 --> 42:42.890 That is also we are doing some data manipulation. 564 42:42.890 --> 42:43.430 Right? 565 42:45.710 --> 42:52.340 And suppose sometimes we need to entirely remove the all the employee details were working in the department. 566 42:52.340 --> 42:55.610 20 means we want to remove the six rows. 567 42:56.630 --> 42:58.870 So for that what we need to write. 568 43:01.210 --> 43:04.390 Delete statement and delete is also the part of the. 569 43:04.390 --> 43:06.220 We are doing some data manipulation. 570 43:06.280 --> 43:10.450 So that is also part of the DML statement right. 571 43:12.490 --> 43:16.450 Now one more thing is that data control statement. 572 43:17.050 --> 43:26.070 So if you are working as a data engineer or data analyst then you do not need to work with this data 573 43:26.070 --> 43:27.300 control language. 574 43:27.900 --> 43:31.440 Mostly you do not need to do so. 575 43:31.440 --> 43:38.640 If you if we as a database administrator, I want to give some grant to some of the user. 576 43:41.100 --> 43:51.290 To select the data from the table or to update the data into the table, then for that purpose. 577 43:51.770 --> 43:52.880 Grant statement. 578 43:52.910 --> 43:54.620 Grant command will be used for. 579 43:54.620 --> 43:56.120 Grant statement will be used. 580 43:59.090 --> 44:06.710 That we are giving the permission to retrieve employee data to some particular user. 581 44:09.050 --> 44:12.340 So that will be the part of the data control language. 582 44:12.790 --> 44:19.960 And suppose if you want to revoke suppose some user has already that kind of permissions is there. 583 44:20.380 --> 44:24.880 But now that user will be the no part of the organization right. 584 44:25.420 --> 44:28.510 That user will be no part of the organization. 585 44:28.960 --> 44:37.980 So at that time we have to revoke the permission, whichever we have given to that particular user. 586 44:37.980 --> 44:38.610 Right. 587 44:39.540 --> 44:44.790 So that revoke statement also will be the part of the data control statement. 588 44:47.220 --> 44:51.570 Now one more thing is transaction control statement right. 589 44:53.190 --> 44:55.770 So what is a transaction control statement. 590 44:55.800 --> 44:59.820 So if you see over here let me show you one. 591 44:59.820 --> 45:00.870 Let me. 592 45:02.940 --> 45:04.770 Again drop this table. 593 45:06.570 --> 45:09.210 Now let me create this table. 594 45:12.630 --> 45:14.820 Now let's see one thing. 595 45:15.030 --> 45:25.190 So over here I have inserted one record right I have inserted only one record into the EMP table, but 596 45:25.190 --> 45:32.000 now I get to know that this record I have inserted wrongly. 597 45:32.720 --> 45:33.290 Right. 598 45:33.290 --> 45:34.940 I have inserted wrongly. 599 45:35.390 --> 45:36.440 I want to. 600 45:37.910 --> 45:40.220 I want to rollback my transaction. 601 45:40.760 --> 45:43.700 I don't want to permanently commit this one. 602 45:43.700 --> 45:46.100 So can I use rollback over here? 603 45:48.400 --> 45:49.900 It will work or not. 604 45:52.540 --> 45:53.890 Let me see. 605 45:54.640 --> 45:56.080 It will not work. 606 45:56.620 --> 46:01.450 The rollback transaction request has no corresponding begin transaction. 607 46:02.680 --> 46:21.780 Because I will tell you in SQL server all the transactions, what whatever we have done is autocommit. 608 46:25.140 --> 46:27.540 In SQL server it is Autocommit. 609 46:28.380 --> 46:34.530 Whenever we have done HBase one, it is automatically permanently stored into the table. 610 46:34.530 --> 46:36.080 We cannot roll back. 611 46:36.440 --> 46:43.340 But now for that purpose, what we need to do for that purpose, what we need to do. 612 46:43.340 --> 46:44.990 I will show you again. 613 46:44.990 --> 46:45.920 Let me. 614 46:48.620 --> 46:49.100 Drop. 615 46:53.780 --> 46:54.770 Ah, yes. 616 46:57.380 --> 46:58.220 Okay. 617 46:58.220 --> 47:01.360 Yeah, yeah, that one I am showing you now. 618 47:01.540 --> 47:04.300 I have now what I have done. 619 47:10.690 --> 47:13.750 Okay, I, I have just created the table. 620 47:13.750 --> 47:17.050 Now I am doing the begin transaction now. 621 47:17.380 --> 47:17.770 Okay. 622 47:22.330 --> 47:23.020 Begin. 623 47:28.830 --> 47:29.880 Okay, now I have done. 624 47:29.880 --> 47:30.210 Begin. 625 47:30.210 --> 47:31.290 Transaction. 626 47:31.500 --> 47:32.040 Now. 627 47:32.130 --> 47:35.670 Now I have done the insert the record into the table. 628 47:36.210 --> 47:42.930 But now I got to know that I have inserted this record mistakenly. 629 47:42.930 --> 47:43.350 Right? 630 47:43.350 --> 47:49.340 I have inserted this record mistakenly, so it will showing me now, right? 631 47:49.340 --> 47:51.110 It will showing me now in the table. 632 47:51.110 --> 47:51.710 Right. 633 47:52.760 --> 47:54.710 You are able to see this record, right? 634 47:57.530 --> 48:08.060 But now if I do the rollback, if I do the rollback now, now is that error is coming. 635 48:09.920 --> 48:12.220 Previously that error is coming, right? 636 48:13.690 --> 48:17.920 The rollback transaction has no corresponding begin transaction. 637 48:17.920 --> 48:18.340 Now. 638 48:18.340 --> 48:19.300 Is it coming? 639 48:19.690 --> 48:21.250 It is not coming, right? 640 48:21.340 --> 48:22.120 Why? 641 48:22.150 --> 48:23.500 Because I have done. 642 48:23.500 --> 48:24.010 Over here. 643 48:24.010 --> 48:24.370 Begin! 644 48:24.370 --> 48:24.970 Tran. 645 48:25.570 --> 48:27.880 Now, if I do the rollback. 646 48:28.570 --> 48:30.280 Now, this is the purpose, okay? 647 48:30.280 --> 48:31.690 I have already done right. 648 48:31.930 --> 48:33.460 Now what? 649 48:33.820 --> 48:36.270 What this table will show me. 650 48:36.300 --> 48:37.650 Can anyone tell me? 651 48:41.670 --> 48:45.000 It will not show me that one record, right? 652 48:45.000 --> 48:45.930 Exactly. 653 48:46.470 --> 48:48.420 So this is the meaning of rollback. 654 48:48.420 --> 48:50.100 This is the meaning of rollback. 655 48:50.670 --> 48:52.320 But always remember. 656 48:53.280 --> 48:53.730 Yeah. 657 48:53.730 --> 48:54.480 Yes. 658 49:17.790 --> 49:18.570 Yeah. 659 49:18.570 --> 49:21.720 For every rollback we must need to do begin. 660 49:21.720 --> 49:22.260 Tran. 661 49:22.260 --> 49:24.560 Then only you will able to roll back. 662 49:24.590 --> 49:28.820 Otherwise everything will be autocommit in SQL server. 663 49:51.460 --> 49:54.070 No, no, uh, actually no no no. 664 49:54.070 --> 49:59.320 Firstly, I have done the begin run, but firstly I have created the table, right? 665 49:59.320 --> 50:01.150 Firstly, I have created the table. 666 50:01.690 --> 50:04.720 Then I want to do some data manipulation language. 667 50:04.720 --> 50:10.330 Right DML so for that DML statement in insert is a DML statement right. 668 50:10.650 --> 50:15.210 So you cannot directly insert before insert you need to do begin. 669 50:15.210 --> 50:15.570 Tran. 670 50:16.350 --> 50:18.660 So before insert I have done the begin Tran. 671 50:19.110 --> 50:22.860 Then I have done the insert statement and then I have rollback. 672 50:32.580 --> 50:34.290 But you know without okay. 673 50:34.290 --> 50:39.230 Yeah that also I have shown you without doing a begin run. 674 50:39.620 --> 50:40.460 This will. 675 50:40.460 --> 50:41.990 You cannot roll back. 676 50:43.760 --> 50:44.750 We have seen it. 677 50:44.750 --> 50:45.080 Right. 678 50:45.080 --> 50:46.010 We have seen it. 679 50:46.010 --> 50:46.550 Uh. 680 50:49.070 --> 50:49.550 We? 681 50:55.370 --> 50:55.940 Yes. 682 51:00.790 --> 51:01.240 Yeah. 683 51:01.240 --> 51:03.340 That you you can do a rollback again. 684 51:03.640 --> 51:04.240 Yes. 685 51:04.240 --> 51:08.770 But if you do not do the begin run then you cannot do the rollback. 686 51:16.510 --> 51:17.860 Yeah you got it right. 687 51:17.890 --> 51:22.270 If you do not do the begin run then you can not do the rollback right. 688 51:29.620 --> 51:30.040 Hello. 689 51:32.020 --> 51:32.320 Yeah. 690 51:34.960 --> 51:35.680 Okay okay okay. 691 51:37.270 --> 51:41.470 So this commit and rollback will be also be the part of. 692 51:43.750 --> 51:49.130 This transaction control transaction control statement. 693 51:53.450 --> 51:57.410 Now the final one is the data query language. 694 51:58.460 --> 52:06.020 And in most of the cases in this our course curriculum, we will see the most of the examples of data 695 52:06.020 --> 52:07.100 query language. 696 52:07.460 --> 52:16.280 You can say that data retrieval language as well DRL or Dxl that are the select statements. 697 52:22.790 --> 52:34.310 So now let me let me now let me tell if you have any of the doubt for today's session. 698 52:35.270 --> 52:38.980 These This timing will be fine, right? 699 53:08.520 --> 53:12.900 Okay, so 10 to 11 or 10 to 1130 will be fine for everyone, right? 700 53:18.900 --> 53:19.410 Okay. 701 53:19.410 --> 53:27.440 So we will keep uh, this one I will put the in the group also tomorrow's class link. 702 53:34.220 --> 53:34.550 Yeah. 703 53:34.550 --> 53:38.090 I will put in the group also for tomorrow's class link. 704 53:42.470 --> 53:44.960 How do you find the today's session? 705 54:01.270 --> 54:11.680 Yeah, we can say that, uh, 1 or 1 and a half month minimum, it will go or maybe up to two months, 706 54:11.880 --> 54:13.050 But we will try. 707 54:13.050 --> 54:13.920 Within two months. 708 54:13.920 --> 54:15.750 We will try to complete. 709 54:27.930 --> 54:28.620 Yeah. 710 54:28.620 --> 54:30.480 Uh, our focus on. 711 54:36.140 --> 54:36.650 Yeah. 712 54:36.650 --> 54:41.060 Our focus will be on, uh, queries. 713 54:41.060 --> 54:48.920 But first of all, I, we will get to understand all kind of the concepts like, uh, what are the sub 714 54:48.920 --> 54:52.070 queries are there, what are the different joins are there. 715 54:52.070 --> 54:54.290 What are the ranking functions are there. 716 54:54.290 --> 54:55.940 What is city's are there. 717 54:56.210 --> 55:02.890 Firstly we will understand all the concepts and then later on we will start with the queries. 718 55:12.400 --> 55:12.730 Yeah. 719 55:12.730 --> 55:13.720 Any other. 720 55:20.710 --> 55:21.130 Yeah. 721 55:21.130 --> 55:23.110 I will provide you all the notes. 722 55:23.110 --> 55:27.460 Uh, whichever we will, uh, write or practice over here. 723 55:27.460 --> 55:34.540 I will provide you everything like create table script, insert table script, update everything, delete 724 55:34.540 --> 55:36.190 whatever we will do in the session. 725 55:36.190 --> 55:38.140 I will provide all the notes. 726 55:42.730 --> 55:46.780 We are recording for right now I we will you will not get. 727 55:46.780 --> 55:52.380 But maybe after the course or maybe after one month I will provide. 728 56:05.100 --> 56:08.520 A Yama alternate day Monday, Wednesday, Friday. 729 56:08.520 --> 56:12.260 And if it is possible Saturday also we can connect. 730 56:16.250 --> 56:22.130 If everybody is fine with Saturday, then set same, same. 731 56:26.210 --> 56:26.780 Yeah. 732 56:26.780 --> 56:27.740 Saturday also we will. 733 56:27.740 --> 56:28.550 Same timing. 734 56:28.580 --> 56:30.110 10 or 11:00. 735 56:34.130 --> 56:34.580 Because. 736 56:35.390 --> 56:35.810 Yeah. 737 56:35.830 --> 56:42.760 Because after after after in the afternoon everybody is going maybe outside or somewhere. 738 56:42.760 --> 56:43.360 Right.