See Also keystore, truststore. 

## startup 

 The process of starting the MySQL server. Typically done by one of the programs listed in Section 4.3, “Server and Server-Startup Programs” . The opposite of shutdown . 

See Also shutdown. 

## statement interceptor 

 A type of interceptor  for tracing, debugging, or augmenting SQL statements issued by a database application. Sometimes also known as a command interceptor . 

In Java  applications using Connector/J , setting up this type of interceptor involves implementing the com.mysql.jdbc.StatementInterceptorV2  interface, and adding a statementInterceptors  property to the connection string . 

In Visual Studio  applications using Connector/NET , setting up this type of interceptor involves defining a class that inherits from the BaseCommandInterceptor  class and specifying that class name as part of the connection string. 

See Also command interceptor, connection string, Connector/J, Connector/NET, interceptor, Java, Visual Studio. 

## statement-based replication 

 A form of replication  where SQL statements are sent from the source  and replayed on the replica . It requires some care with the setting for the innodb_autoinc_lock_mode  option, to avoid potential timing problems with auto-increment locking . 

See Also auto-increment locking, innodb_autoinc_lock_mode, replica, replication, row-based replication, source. 

## statistics 

 Estimated values relating to each InnoDB table  and index , used to construct an efficient query execution plan . The main values are the cardinality  (number of distinct values) and the total number of table rows or index entries. The statistics for the table represent the data in its primary key  index. The statistics for a secondary index  represent the rows covered by that index. 

The values are estimated rather than counted precisely because at any moment, different transactions  can be inserting and deleting rows from the same table. To keep the values from being recalculated frequently, you can enable persistent statistics , where the values are stored in InnoDB  system tables, and refreshed only when you issue an ANALYZE TABLE  statement. 

You can control how NULL  values are treated when calculating statistics through the innodb_stats_method configuration option. 

Other types of statistics are available for database objects and database activity through the INFORMATION_SCHEMA  and PERFORMANCE_SCHEMA  tables. 

See Also cardinality, index, INFORMATION_SCHEMA, NULL, Performance Schema, persistent statistics, primary key, query execution plan, secondary index, table, transaction. 

## stemming 

 The ability to search for different variations of a word based on a common root word, such as singular and plural, or past, present, and future verb tense. This feature is currently supported in MyISAM full-text search  feature but not in FULLTEXT indexes  for InnoDB  tables. 

See Also full-text search, FULLTEXT index. 

## stopword 

 In a FULLTEXT index , a word that is considered common or trivial enough that it is omitted from the search index  and ignored in search queries. Different configuration settings control stopword processing for InnoDB  and MyISAM  tables. See Section 12.10.4, “Full-Text Stopwords”  for details. 

