Posts

Vicidial Installation Guide

  Vicidial scratch installation in Centos7 Asterisk-13     A Step by step guide for  vicidial scratch installation  in  centos 7  with  asterisk-13  or  asterisk-16  version and vicidial latest  SVN version . Vicidial scratch installation is the easiest and best way of installing vicidial in hosted servers where you don't have the option to install ISO image of vicibox.     Vicidial Scratch installation can also be used for Vicidial Cluster setup, same steps will be used for other Linux Distributions like  Rocky,alma,ubuntu  etc. Major Components of Vicidial 1.  Asterisk  - Telephony server 2. Mariadb  - Database 3. Apache  - Webserver Vicidial Scratch - Pre-Requisites Before proceeding with vicidial scratch installation steps , we must have below pre-requisites ready Centos 7 installed either full DVD or minimal OS installation Console access to the server or SSH access via putty . ...
Post a Comment
Read more
  18 Commands to Monitor Network Bandwidth on Linux server https://www.binarytides.com/linux-commands-monitor-network/ Follow the above link .
Post a Comment
Read more

PostgreSQL - CREATE & ALTER INDEX

CREATE INDEX To create a B-tree index on the column  title  in the table  films : CREATE UNIQUE INDEX title_idx ON films (title); ALTER INDEX ALTER INDEX distributors RENAME TO suppliers; ALTER INDEX name RENAME TO new_name
Post a Comment
Read more

MYSQL - PRIMARY KEY DESCRIPTION

A  PRIMARY KEY  is a unique index where all key columns must be defined as  NOT NULL . If they are not explicitly declared as  NOT NULL , MySQL declares them so implicitly (and silently). A table can have only one  PRIMARY KEY . The name of a  PRIMARY KEY  is always  PRIMARY , which thus cannot be used as the name for any other kind of index. If you do not have a  PRIMARY KEY  and an application asks for the  PRIMARY KEY  in your tables, MySQL returns the first  UNIQUE  index that has no  NULL  columns as the  PRIMARY KEY .
Post a Comment
Read more

MYSQL STORAGE ENGINE STATUS CHECK

MYSQL STORAGE ENGINE COMMANDS 1. How to check Global storage engine : SHOW GLOBAL VARIABLES LIKE 'storage_engine'; 2. How to check all table status/engine for Particular database : SHOW TABLE STATUS FROM 'DBNAME'; 3. How to Find out InnoDB tables of Particular database : SELECT TABLE_NAME FROM information_schema.TABLES     WHERE TABLE_SCHEMA = 'DBNAME' AND engine = 'InnoDB'; 4 Check Table Status with Condition : SHOW TABLE STATUS FROM 'DBNAME' WHERE ENGINE like 'MyISAM' 5 Modify or Update ENGINE of particular table in MYSQL ALTER TABLE tablename ENGINE = InnoDB; 6 Check data tables rows,size & engine details of selected/multiple database in MYSQL SELECT    engine,         count(*)    as    TABLES,         concat(round(sum(table_rows)/1000000,2),'M')    rows,         concat(round(sum(data_length)/(1024*1024*1024),2),'G')    DATA,  ...
Post a Comment
Read more

Some Common Attributes of Columns in MYSQL Tables

PRIMARY KEY   It is a unique index where all key columns must be defined as  NOT NULL . If they are not explicitly declared as  NOT NULL , MySQL declares them so implicitly (and silently). A table can have only one  PRIMARY KEY . The name of a  PRIMARY KEY  is always  PRIMARY , which thus cannot be used as the name for any other kind of index. If you do not have a  PRIMARY KEY  and an application asks for the  PRIMARY KEY  in your tables, MySQL returns the first  UNIQUE  index that has no  NULL  columns as the  PRIMARY KEY . AUTO_INCREMENT The initial  AUTO_INCREMENT  value for the table. In MySQL 5.0, this works for  MyISAM  and  MEMORY  tables. It is also supported for  InnoDB  as of MySQL 5.0.3. To set the first auto-increment value for engines that do not support the AUTO_INCREMENT  table option, insert a  “ dummy ”  row with a value one ...
Post a Comment
Read more

Physical Representation of MYSQL Tables

MySQL represents each table by an  .frm  table format (definition) file in the database directory. The storage engine for the table might create other files as well. For  InnoDB  tables, the file storage is controlled by the  innodb_file_per_table  configuration option. When this option is turned off, all  InnoDB  tables and indexes are stored in the  system tablespace , represented by one or more  ibdata* files . For each  InnoDB  table created when this option is turned on, the table data and all associated indexes are stored in a  .ibd file  located inside the database directory. For  MyISAM  tables, the storage engine creates data and index files. Thus, for each  MyISAM  table  tbl_name , there are three disk files. File Purpose tbl_name .frm Table format (definition) file tbl_name .MYD Data file tbl_name .MYI Index file
Post a Comment
Read more