Studio Press

Please pay attention to the MySQL SQL Insert Into Ststement below :


insert into `m_statis`(`idstatis`,`jenisstatis`) values (1,'Sambutan');
insert into `m_statis`(`idstatis`,`jenisstatis`) values (2,'Visi dan Misi');
insert into `m_statis`(`idstatis`,`jenisstatis`) values (3,'Roadmap penelitian Unud');
insert into `m_statis`(`idstatis`,`jenisstatis`) values (4,'Kebijakan penelitian Unud');
insert into `m_statis`(`idstatis`,`jenisstatis`) values (5,'TOR penelitian Unud');
insert into `m_statis`(`idstatis`,`jenisstatis`) values (6,'Tatalaksana penelitian');
insert into `m_statis`(`idstatis`,`jenisstatis`) values (7,'Kontak');

and MySQL SQL Insert Into Ststement below :

insert into `m_statis`(`idstatis`,`jenisstatis`) values (1,'Sambutan'),(2,'Visi dan Misi'),(3,'Roadmap penelitian Unud'),(4,'Kebijakan penelitian Unud'),(5,'TOR penelitian Unud'),(6,'Tatalaksana penelitian'),(7,'Kontak');

The First Statement is Call Non Bulk SQL Insert Statement, and The Second is Bulk SQL Insert Statement. This Bulk SQL Insert Statement can increase potential of Restore Database Error. A big size of database can cause a out of memory while Execute BULK Insert Statement. A Non Bulk Insert Statement can reduce potential of Restore Database Error, because it execute using smaller memory size and per single Table Row.

So I Recommend you to use Non Bulk SQL Insert Statement, even if the SQL Filesize can be bigger, the safety is more Important.

How can we provide a SQL File that contain Non Bulk SQL Insert Statement,
the simple way can be found Here