background top icon
background center wave icon
background filled rhombus icon
background two lines icon
background stroke rhombus icon

Download "SQL Практикум. Урок 1. Создание базы данных в MS SQL"

input logo icon
Video tags
|

Video tags

CyberBionic
ITVDN
программирование
курсы программирования
Microsoft
Framework
.net
Видео урок
видеоурок
видеокурс
видеокурсы
видео обучение
создание базы данных
создание бд
создание таблиц в бд
создание таблиц в базе данных
создание базы данных в SQL Server 2014
этапы создания бд
этапы создания базы данных
create
create database
create table
SQL
itvdn
программррование
видео уроки баз данных
Subtitles
|

Subtitles

subtitles menu arrow
  • ruRussian
Download
00:00:00
[music]
00:00:05
Hello My name is Stanislav Zuko I
00:00:08
am a trainer consultant at the training
00:00:11
center p Bionic systematics I am glad to
00:00:14
welcome you to the information video
00:00:16
portal
00:00:18
itvdn in this video lesson we are starting a
00:00:21
series of classes on the course SQL workshop What is
00:00:24
this course the course
00:00:27
is intended for programmers
00:00:30
who have already mastered the theoretical
00:00:32
the basics of the SQL language, namely such an
00:00:35
extension as SQL proposed by
00:00:39
Microsoft in this course. We will not
00:00:42
create any final product, we
00:00:44
will also have assumptions, we will create a
00:00:47
database of an
00:00:49
online store that
00:00:51
will fully maintain the integrity of
00:00:54
information also a significant part of
00:00:56
the time we will devote time to working with data,
00:00:59
that is, presenting them in a consolidated,
00:01:02
generalized, easy-to-read
00:01:05
form. In the course materials, you will find
00:01:08
five folders corresponding to each
00:01:11
lesson in each folder you will find three
00:01:14
files, an assignment file, a file with answers and a
00:01:18
file with additional information
00:01:20
that you will also need in the
00:01:22
process completing the
00:01:24
tasks in the first video lesson, we will create a
00:01:28
database, define and create tables
00:01:31
in the database and begin to ensure the
00:01:35
integrity of the information in our
00:01:37
database, create keys, create connections,
00:01:41
provide
00:01:43
constraint links at the end of the lesson, we will
00:01:47
fill the table with
00:01:49
data, now return to the management
00:01:51
studio and begin completing our
00:01:55
tasks in first task We need to
00:01:58
create a database for the
00:02:02
online store Create
00:02:09
Database with the name Internet shop db and
00:02:14
we will also
00:02:16
set the
00:02:20
sorting settings, execute from the ninth to
00:02:23
eleventh lines and see that our
00:02:26
database has been successfully created. Let's
00:02:29
update the databases folder in object Explorer
00:02:33
and now we see in it database ine
00:02:38
Shop
00:02:39
db move on to the second task In the second
00:02:42
task We need to create
00:02:46
tables to complete this task
00:02:49
let's turn to the additional
00:02:51
file Here you will find two figures: a
00:02:54
diagram of tables and Figure 2 creating
00:02:58
tables in the database design process
00:03:01
You must determine What data
00:03:04
you will store in database of which
00:03:07
entities they will be part of and what
00:03:09
entities you will have in general. Let’s say we have
00:03:12
already analyzed the business processes
00:03:14
that are in our store and
00:03:17
determined the following set of
00:03:19
tables, we will have a table of
00:03:22
employees that we will store ID
00:03:25
surname first name patronymic of the employee
00:03:27
position salary and
00:03:30
additional bonus information about the employee
00:03:32
We
00:03:35
will put information about marital
00:03:37
status, date of birth, address and
00:03:41
telephone number into the emplo info table. We will also have a table of
00:03:44
buyers in which we will store the
00:03:46
buyer's ID, surname, middle name, address,
00:03:49
city, phone number and date of registration in the
00:03:54
system. The next entity is
00:03:58
products
00:04:00
in the main table of products we will
00:04:02
store only the name of the products
00:04:05
we will store the entire description in the
00:04:07
product
00:04:08
details table here we make an assumption and in the
00:04:11
description field we store the entire description of the
00:04:14
product of course in real life it
00:04:16
would be necessary to split the product description
00:04:19
into more fields for an
00:04:22
example we brought out Only the
00:04:25
color field to the products table, we
00:04:28
will also define a warehouse
00:04:30
inventory table in which we will store the
00:04:33
current balances of goods in the warehouse,
00:04:38
quantity fields, now we just need to create the
00:04:41
orders and orders details tables in the
00:04:44
orders table, we will store
00:04:46
information about the orders themselves in the
00:04:50
Order table details
00:04:52
information about orders will be revealed, that is, in the
00:04:54
orders table we will contain the order ID of
00:04:58
who placed the order and what date the
00:05:03
order was in the Order details table we
00:05:06
will store Which product In what
00:05:09
quantity at what
00:05:11
price We will also have a calculated
00:05:15
column here in In the second figure you will find
00:05:19
information about what data types
00:05:21
your fields should be and whether they support or do not
00:05:24
support
00:05:26
the purpose, but before that I recommend that
00:05:30
you think about defining the data types and whether
00:05:35
certain
00:05:37
fields of our
00:05:40
tables support or do not support the value. I will also add a few words about the
00:05:44
value of the Microsoft documentation, it
00:05:47
is recommended to avoid nal values
00:05:49
since they complicate the execution of
00:05:51
queries and
00:05:54
update procedures, on the other hand, if we
00:05:56
put a field in we name some
00:06:00
data there, in this case we can always
00:06:03
use the default
00:06:06
values. I
00:06:09
set the permission to nal values ​​for
00:06:12
those fields that may be
00:06:14
unknown to us. During the initial entry information
00:06:18
That is, for employees, for example, this field is
00:06:21
Middle name and PR
00:06:24
sary; for
00:06:27
buyers, we allow cash values ​​for all fields
00:06:30
except IDIN, since
00:06:32
the user can register but
00:06:35
not enter any of his
00:06:38
data. Now let's go back to the code and
00:06:42
write the code for creating
00:06:45
tables before creating tables.
00:06:48
in our database Internet
00:06:51
shop
00:06:53
db we will create a table
00:06:58
customers
00:07:01
Create Table customers and then
00:07:04
our fields will go I
00:07:06
recommend naming the tables and fields in
00:07:09
the tables identical to the names that
00:07:12
you see in the video lesson To avoid
00:07:15
confusion since
00:07:17
we will use the database created in the First lesson
00:07:19
throughout the
00:07:22
course and in this table we will have
00:07:25
the following fields
00:07:28
ID
00:07:34
not
00:07:37
identity All the dishes we will
00:07:40
auto-increment we will have them
00:07:43
automatically generated for this
00:07:45
we indicate the keyword
00:07:48
identity of course in real life the
00:07:51
dishes you have are
00:07:53
generics in another
00:07:56
way the next field F will be like
00:08:01
nvarchar for 20
00:08:03
[music]
00:08:05
characters And to support cash
00:08:10
values ​​we will specify the same properties for
00:08:13
the fields
00:08:17
MN Last
00:08:24
name address we will make for 50
00:08:28
characters
00:08:36
city for phone we use the
00:08:40
data type Char for 12 characters since our
00:08:44
phone
00:08:45
will consist of a constant length of 12
00:08:52
characters and
00:08:56
type and here we will indicate the knowledge
00:09:04
Get we will take the current
00:09:13
date we will execute the code from whose to the twenty-
00:09:16
fourth line and We have created the first
00:09:19
table in our database let's
00:09:23
check it We turn to the folder of our databases
00:09:28
given the table
00:09:33
customers the next table of
00:09:39
employees here we will also have ID
00:09:43
identity F Mid type for 20
00:09:49
characters
00:09:51
position salary and bonus type but
00:09:54
here for some fields we have indicated
00:09:58
as When we
00:10:00
fill out this table we will already have
00:10:03
information about our employees on hand the
00:10:06
following table employees
00:10:12
info here the continuation of
00:10:15
information about our
00:10:17
employees marital status date is stored
00:10:20
birth address and
00:10:24
telephone number, then we create a table of
00:10:28
products
00:10:31
ID and
00:10:41
name the next
00:10:43
table product
00:10:48
details ID we took out the color from the description and
00:10:52
the description of the type Ma since we will
00:10:58
store a large amount of
00:11:01
information here the warehouse
00:11:11
inventory table which we will
00:11:14
store current balances in the warehouse and by
00:11:17
default will be take the value
00:11:21
zero field type and If we had
00:11:25
some kind of weight product, of course we would
00:11:28
use a different data type, but we
00:11:32
will have a piece product. Therefore, the int
00:11:34
type is suitable for us. The
00:11:36
last two
00:11:39
tables are tables storing information about
00:11:42
orders, this is the orders and orders
00:11:57
details table in the ord table, the Order Date field
00:12:01
will by default store the current
00:12:07
date in the Order details table, we will have a
00:12:10
calculated Total Price column. I am
00:12:13
inclined to not
00:12:15
store calculated Columns in database tables.
00:12:18
But for the example, we will create it here
00:12:20
and a calculated column as a
00:12:23
result multiplying the quantity by
00:12:27
the price,
00:12:33
we will update the tables folder and see all of our
00:12:36
eight
00:12:39
tables. On this we
00:12:42
have completed the second task, we move on to the third task in the
00:12:46
third task. We need to
00:12:47
establish connections between the tables, and we also
00:12:50
need to provide
00:12:52
conditions for referential
00:12:54
integrity. Let's return to the figure about
00:12:58
and again. we have tables and
00:13:02
what connections should be between them, the
00:13:04
impe info table will be
00:13:08
connected as one to one, we just
00:13:11
put additional information in a
00:13:13
separate table The same applies to the
00:13:16
tables products and product details
00:13:20
products And their sts relationship will be
00:13:23
one to one and they will store
00:13:27
information about the
00:13:30
product; these tables will be linked by
00:13:33
fields
00:13:34
ID and ID product
00:13:38
ID; the
00:13:41
orders table stores two fields such as
00:13:44
cer and employe
00:13:47
ID; by these fields we will link to the
00:13:50
corresponding tables;
00:13:53
customers; the
00:13:56
Order table will be linked by ID to the
00:14:00
orders table; ID and by the product ID field with the
00:14:04
products table by the
00:14:06
ID field Let's return to the management studio And start
00:14:10
performing the third
00:14:12
task in order to establish connections
00:14:14
between the tables, we need to set
00:14:17
primary and foreign
00:14:19
keys Let's change the
00:14:23
custom table
00:14:29
and add a primary
00:14:34
key to the
00:14:42
ID field Let's do this one hundredth 103 rows and
00:14:47
on the customers table on the ID field we
00:14:50
will create a primary
00:14:53
key in the same way. We need to create a
00:14:56
primary key on the ID field of the
00:15:03
employees table. Now let’s move on to the
00:15:06
employees
00:15:07
info table. The employees table and employees info are
00:15:11
linked one to one and To ensure
00:15:14
this type of connection, we
00:15:18
need to ensure uniqueness of the
00:15:21
ID field in the employees info table, that is, we
00:15:25
will change the
00:15:30
employees
00:15:34
info table and add a Unique constraint to the
00:15:41
ID field. Now we can link the
00:15:44
employees and emplo info tables. To do this, we will again
00:15:47
change the
00:15:51
emplo
00:15:55
info table and
00:15:57
add a
00:16:01
foreign
00:16:06
key to the
00:16:10
ID field that will refer to the
00:16:16
employees table. the parent table
00:16:23
employees also on the ID field, in this case
00:16:30
we
00:16:32
must provide
00:16:43
a reference; we will not set conditions for
00:16:46
on update; this is our next
00:16:49
assumption; we will not update data in
00:16:52
our IDIN tables and set conditions
00:16:57
for Delete when deleting from a record from the
00:17:02
parent table employees. We will
00:17:04
cascade
00:17:05
delete records from the emplo info table Well,
00:17:09
we really don’t need
00:17:12
to store information in the impl info table
00:17:15
about a non-existent, unclear
00:17:19
employee. Let’s execute the codes for
00:17:23
creating keys and
00:17:27
restrictions
00:17:29
and now move on to the
00:17:33
products table. First, we’ll also set the primary
00:17:37
key on the product ID field.
00:17:44
I’ll change
00:17:48
the name of the table by copying the original
00:17:53
code. and on the ID field of the prods tables we hang
00:17:58
and execute the code from lines 121 to 124,
00:18:06
now we will change the product
00:18:12
details tables, the product and product
00:18:15
details table are connected one to one and To
00:18:19
ensure this type of connection, we
00:18:23
set UN conditions on the ID field of the
00:18:26
product details tables from the
00:18:31
employees table And now we can connect the
00:18:34
products and products details tables,
00:18:37
we change the product details table again
00:18:40
and in the ID field of the product
00:18:44
details table we hang a foreign key that
00:18:47
will refer to the products table in the
00:18:50
ID field. In this case, when we delete a record from the
00:18:54
products table, we will cascade delete
00:18:57
records from the product table
00:19:01
details the following warehouse
00:19:05
inventory table, similar to the previous
00:19:08
examples. We also set up a one-to-
00:19:11
one relationship, put UN on the product ID field of the
00:19:15
stocks table and
00:19:18
link the stocks table, put a foreign
00:19:21
key on the product ID field, which will
00:19:24
refer to the products table, ID field and
00:19:28
also on Delete cascad
00:19:32
conditions now we will change the
00:19:37
orders table we will set the primary key to the
00:19:43
ID field in the orders table We have two fields
00:19:47
customer ID and employees ID by these fields
00:19:51
we must contact the parent
00:19:53
tables customers and
00:19:57
employees
00:20:03
in the code on 153,157 lines we connect the
00:20:09
orders table with the customers table
00:20:12
we set a foreign key on the customer ID field
00:20:15
which will refer to the
00:20:17
customers table on the ID field. In this case, when
00:20:20
deleting a record from the parent table
00:20:24
customers in orders, we have no orders,
00:20:28
we just won’t know
00:20:30
which customer made the order, that is,
00:20:33
the field will be set to using the
00:20:37
same logic we We attach a foreign
00:20:41
key to the empe ID field for connection with the
00:20:46
parent table emplo. When deleting
00:20:49
an employee, we will not know which
00:20:52
employee issued this
00:20:57
order. Our order will remain and the information will not be
00:21:01
deleted. We will not
00:21:06
lose the following table, Order
00:21:11
details. Here we do not have a column that
00:21:14
would would uniquely identify the record,
00:21:17
so we set a composite primary
00:21:19
key using the Order ID and line item fields,
00:21:29
also using the Order ID field, we must
00:21:32
contact the parent table orders,
00:21:35
for this we will set a foreign key on the Order ID field of the
00:21:38
Order details table,
00:21:41
you see the code from line 170 to line 174 the
00:21:47
foreign key will refer to the
00:21:50
orders table on the ID field and when deleting an order
00:21:54
record from the orders table, we will delete the
00:21:58
records from the Order
00:22:07
details table. And the last thing we need
00:22:10
to do is add a foreign key to the
00:22:13
product ID field of the Order details tables to
00:22:16
connect with the parent table products
00:22:20
by
00:22:21
ID field in this case, when deleting a product, our
00:22:26
orders will not be lost, we will not know
00:22:28
which product was purchased, but information about the
00:22:31
quantity, price and other information
00:22:34
We will also retain, looking ahead,
00:22:37
I will say that we will slightly
00:22:40
redefine and
00:22:42
tighten the
00:22:44
rules for deleting products, we will
00:22:47
do this in the next lesson using
00:22:53
triggers, we will execute the code from lines 176 to 180,
00:22:57
and with that we have completed the third
00:23:01
task; we move on to the fourth task in
00:23:05
which we need to create
00:23:06
custom
00:23:09
restrictions; the first restriction will be on the
00:23:12
correctness of entering the phone number;
00:23:18
we will change the
00:23:24
customers table and add restrictions
00:23:30
on the background
00:23:35
phone field so
00:23:37
that our the phone matched
00:23:41
the following
00:23:46
pattern, we must first have an
00:23:50
opening bracket, then three
00:23:56
digits, a closing bracket, and then seven more
00:24:08
digits by executing the code from lines 190 to 193.
00:24:12
We have created a custom constraint
00:24:15
on the background field of the customers table;
00:24:19
we also have a background field in the
00:24:22
employees
00:24:25
info table; let's set a custom
00:24:27
constraint and in this table on the
00:24:40
background field in the second constraint we must
00:24:44
provide the logic according to which
00:24:47
candidates
00:24:50
aged from 18 to 50
00:24:55
years can be hired in our store. The age of our employees is stored in the
00:24:59
B Date field of the employees info table,
00:25:03
so we change the emplo
00:25:08
IO table and set the
00:25:11
following
00:25:13
constraint
00:25:15
field bos
00:25:20
Date must
00:25:22
be in the following
00:25:26
interval.
00:25:37
Thus,
00:25:39
we have created a condition under
00:25:43
which our date of birth must
00:25:46
be in the range 50 years ago to
00:25:50
18 years
00:25:53
ago, we execute the code line by
00:25:58
line and we have
00:26:01
completed the second
00:26:03
task of user
00:26:06
restrictions in the third task. We
00:26:08
need to create a restriction according to
00:26:10
which orders can be recorded from the
00:26:13
day the store opened and Until today,
00:26:18
let's agree here that the day the
00:26:21
store opened was 90 days
00:26:26
ago
00:26:28
to set this restriction. We
00:26:32
need to
00:26:33
change the
00:26:36
orders table so that the Order Date
00:26:41
is less than or equal to the current date and
00:26:45
greater than or equal to the date ninety days ago.
00:26:49
Then is when we opened
00:26:51
the store 90 days ago
00:27:01
in the fourth constraint
00:27:03
we must enter data into the
00:27:07
marital status column only the words Married Single Married
00:27:10
Single we change the
00:27:14
employees
00:27:16
info table and set restrictions on the
00:27:20
marital status field so that it
00:27:23
contains any of the values
00:27:26
presented
00:27:28
in brackets Married Single Married not
00:27:38
married Next we need to create a
00:27:40
restriction according to which a client
00:27:43
can be registered in the system
00:27:45
from the day it was opened until today, well,
00:27:48
this task is similar to the third. Now we
00:27:52
must change the
00:27:56
customers table and the Date in System field that
00:28:01
stores the registration date in the system must
00:28:04
have in our range more than 90 days
00:28:08
ago the store opening date
00:28:11
and less than or equal to the current
00:28:20
date
00:28:21
the following task We need to create a
00:28:24
constraint according to which the bonus
00:28:27
cannot be equal to or be greater than the
00:28:30
salary; the bonus and salary are
00:28:32
stored in the
00:28:35
employees table, change the
00:28:38
employees table and we set a
00:28:41
restriction so that the bonus
00:28:44
is less than the
00:28:50
salary.
00:28:52
And our last
00:28:55
restriction is fulfilled. According to this, the balance of
00:28:58
goods in the warehouse cannot be
00:29:01
negative. The balance of goods in the warehouse
00:29:03
is stored in the
00:29:05
stoks table. We change the
00:29:08
stocks table and set restrictions so that the
00:29:12
quantity field is greater than or equal to
00:29:19
zero. We're done here. completing the
00:29:22
fourth task, we move on to
00:29:24
completing the fifth task in the fifth
00:29:27
task We need to fill the tables with
00:29:30
data. Here you already see the code that
00:29:34
you only need to
00:29:38
execute. If you correctly named the
00:29:41
tables, the fields in the tables
00:29:45
created the tables correctly, then by executing the code from
00:29:53
lines 232 to 384, your tables will be filled correctly With
00:30:01
the data in the
00:30:04
orders table and the
00:30:09
customers tables, we
00:30:12
artificially entered
00:30:15
dates in this way in order to
00:30:17
model the training base and so that it
00:30:21
was always up to date. That is, we
00:30:24
will always have the date there 85 ago 45
00:30:28
Thus, we will fit into 3
00:30:34
months. Now let's make selections
00:30:38
from all
00:30:42
tables and see what data we
00:30:45
have entered in our table, the first table is the
00:30:49
customers table, here we
00:30:52
will have 11 customers, the next
00:30:57
employee table, we will have six
00:31:00
employees, then the
00:31:04
goods table, we will initially have
00:31:07
eight goods, here are our three Tables with
00:31:11
the name of the product with the remaining goods in the
00:31:18
warehouse and a table with a description of the product.
00:31:23
Here you see data on orders. We
00:31:27
will initially have 24 orders
00:31:30
distributed over all 3
00:31:35
months. Some orders were placed by the buyer
00:31:39
independently; the rest of the orders
00:31:42
were placed with the help of
00:31:48
employees and the latest data is from a
00:31:51
table of order details in some order there
00:31:56
was one item purchased in some
00:32:00
two and thus all our 24 orders
00:32:04
represent details about the products
00:32:08
quantity price at which the
00:32:11
goods were purchased and finally you
00:32:15
need to build a table diagram
00:32:18
for this in the Database diagrams folder We
00:32:21
select Database diagram select all
00:32:25
our tables
00:32:31
In In the end, we got this
00:32:35
table diagram. Let's summarize today's
00:32:38
lesson. We created a database,
00:32:41
defined tables, and began to
00:32:44
ensure the integrity of information in
00:32:46
our database. Data
00:32:48
integrity, we ensured the integrity of
00:32:52
entities, entity integrity, that is, we
00:32:55
set primary keys on the table fields
00:32:58
on the ID and fields. for child tables
00:33:02
that are related to the parent tables one-
00:33:06
to-one, we set a UN constraint. To
00:33:10
ensure this type of
00:33:13
connection, we also
00:33:15
set
00:33:22
referential
00:33:25
integrity
00:33:28
by setting default values ​​for some fields
00:33:32
and setting SEV user
00:33:37
restrictions. In the next lesson, we
00:33:40
will continue to ensure the integrity of
00:33:43
information in our database, this will be
00:33:47
ours. User define integrity using
00:33:50
triggers we will set additional
00:33:53
business
00:33:54
logic, this is the end of today's lesson
00:33:58
Thank you for your attention and see you again
00:34:01
[music]

Description:

Промокод на скидку 15% на все курсы ITVDN- H94BCAB Полный видеокурс: https://itvdn.com/ru/video/sql-workshop В данном видео уроке рассматривается процесс создания базы данных с помощью Microsoft SQL Server Management Studio. Благодарим всех за лайки, перепосты, добавление в избранное! https://itvdn.com/ – видеопортал по обучению технологиям Microsoft. А также подписывайтесь на нас в социальных сетях: https://vk.com/itvdn https://www.facebook.com/unsupportedbrowser https://twitter.com/ITVDN/media?lang=ru https://www.linkedin.com/company/6387... https://workspaceupdates.googleblog.com/2023/04/new-community-features-for-google-chat-and-an-update-currents%20.html Свои предложения присылайте на почту: [email protected]

Preparing download options

popular icon
Popular
hd icon
HD video
audio icon
Only sound
total icon
All
* — If the video is playing in a new tab, go to it, then right-click on the video and select "Save video as..."
** — Link intended for online playback in specialized players

Questions about downloading video

mobile menu iconHow can I download "SQL Практикум. Урок 1. Создание базы данных в MS SQL" video?mobile menu icon

  • http://unidownloader.com/ website is the best way to download a video or a separate audio track if you want to do without installing programs and extensions.

  • The UDL Helper extension is a convenient button that is seamlessly integrated into YouTube, Instagram and OK.ru sites for fast content download.

  • UDL Client program (for Windows) is the most powerful solution that supports more than 900 websites, social networks and video hosting sites, as well as any video quality that is available in the source.

  • UDL Lite is a really convenient way to access a website from your mobile device. With its help, you can easily download videos directly to your smartphone.

mobile menu iconWhich format of "SQL Практикум. Урок 1. Создание базы данных в MS SQL" video should I choose?mobile menu icon

  • The best quality formats are FullHD (1080p), 2K (1440p), 4K (2160p) and 8K (4320p). The higher the resolution of your screen, the higher the video quality should be. However, there are other factors to consider: download speed, amount of free space, and device performance during playback.

mobile menu iconWhy does my computer freeze when loading a "SQL Практикум. Урок 1. Создание базы данных в MS SQL" video?mobile menu icon

  • The browser/computer should not freeze completely! If this happens, please report it with a link to the video. Sometimes videos cannot be downloaded directly in a suitable format, so we have added the ability to convert the file to the desired format. In some cases, this process may actively use computer resources.

mobile menu iconHow can I download "SQL Практикум. Урок 1. Создание базы данных в MS SQL" video to my phone?mobile menu icon

  • You can download a video to your smartphone using the website or the PWA application UDL Lite. It is also possible to send a download link via QR code using the UDL Helper extension.

mobile menu iconHow can I download an audio track (music) to MP3 "SQL Практикум. Урок 1. Создание базы данных в MS SQL"?mobile menu icon

  • The most convenient way is to use the UDL Client program, which supports converting video to MP3 format. In some cases, MP3 can also be downloaded through the UDL Helper extension.

mobile menu iconHow can I save a frame from a video "SQL Практикум. Урок 1. Создание базы данных в MS SQL"?mobile menu icon

  • This feature is available in the UDL Helper extension. Make sure that "Show the video snapshot button" is checked in the settings. A camera icon should appear in the lower right corner of the player to the left of the "Settings" icon. When you click on it, the current frame from the video will be saved to your computer in JPEG format.

mobile menu iconWhat's the price of all this stuff?mobile menu icon

  • It costs nothing. Our services are absolutely free for all users. There are no PRO subscriptions, no restrictions on the number or maximum length of downloaded videos.