MySQL (stands for Free Relational Database Management System) is a compact, multi-threaded database server that is fast, stable, and easy to use.

It was originally developed by TcX to solve internal problems - the fastest possible processing of large databases. Used internally since 1996 on a server with more than 40 databases that contain 10,000 tables, of which more than 500 have more than 7 million rows.

To date, MySQL is developed and supported by Oracle Corporation, which acquired Sun Microsystems on January 27, 2010, after which it included MySQL in its product line. Earlier (February 26, 2008), Sun Microsystems paid $1 billion to acquire MySQL AB. The product is distributed both under the GNU General Public License and under its own commercial license. In addition, developers create functionality on the order of licensed users, it was thanks to such an order that the replication mechanism appeared in almost the earliest versions.

MySQL is the most optimal solution for small and medium applications. Server sources are compiled on many platforms. The server's capabilities are most fully manifested on Unix servers, where there is support for multithreading, which gives a significant performance boost. Included in WAMP, AppServ, LAMP servers and in portable assemblies of Denver, XAMPP servers. MySQL is typically used as a server accessed by local or remote clients, but the distribution includes an internal server library that allows you to include MySQL in standalone programs.
With support for a huge number of table types, MySQL is quite flexible. Users can select both MyISAM full text search tables and transaction tables in individual InnoDB records. In addition, MySQL ships with a special EXAMPLE table type that demonstrates how to create new types of tables. Thanks to this, as well as open architecture and GPL-licensing, it is possible to add new types of tables to MySQL almost endlessly.

MySQL Server is free for non-commercial use. Otherwise, you need to purchase a license, the cost of which is currently 190 EUR.

The MySQL developer community has created various code forks such as Drizzle, OurDelta, Percona Server, and MariaDB. All of these offshoots already existed at the time of Sun's takeover by Oracle Corporation.

The rise of MySQL

Until 1994, the market was dominated by databases designed to work with significant amounts of data and complex relationships, which had different capabilities, but at the same time required significant computing resources. These databases include Oracle, Informix, and Sybase. There was no DBMS that would support SQL and be affordable at the same time.

Large corporations and universities could afford powerful computing systems, while small organizations and users used weak desktop databases such as Postgres, which used a variation of the QUEL language (PostQUEL), but which, unfortunately, required the same resources, like its counterparts, but did not provide the advantage of using SQL as a query language.

Then a certain David Hughes (later, after the publication of his work on the Internet, known as Bamby), who was writing a dissertation at that time at Bond University (Australia), started developing the Minerva Network Management System project - a monitoring and control system from one or more points for group of systems. The main element of the project was to be a database for storing information about all computers on the network. Hughes initially decided to use Postgres. However, colleagues suggested using SQL as the query language for Minerva, since SQL is the most common query language, and using it, Minerva could be available anywhere in the world where there is an RDBMS that supports SQL. This was the impetus for the creation of MySQL.

Hughes decided to create a program himself that would translate SQL into PostQUEL in real time. He called his program miniSQL, or mSQL. It intercepted the SQL statements sent by Minerva, converted them to PostQUEL, and sent the result to Postgres. For a while, this situation suited Hughes. However, as Minerva continued to grow, it became clear that with the limited resources available to it, neither Postgres nor any other large RDBMS would be able to support the small set of features that it needed. So, for example, in order to implement the ability to simultaneously connect Minerva to several databases at once, Postgres required several instances of the database server to be running simultaneously.

To solve these problems, Hughes analyzed the work of Minerva, and it turned out that the main queries generated by Minerva were: "insert", "delete" and "select". Since Hughes already had mSQL doing SQL translation, all he needed to do was build a database server to suit his needs.

This is where Michael Monty Widenius, credited as the inventor of MySQL, comes into play. In 1979 he developed a database management tool called UNIREG. UNIREG has since been extended to support large databases and has been rewritten in several languages. In 1994, TcX began developing applications for the www using UNIREG. However, due to high overhead, UNIREG could not be used successfully for dynamically generating Web pages. Therefore, Widenius decided to contact the mSQL author, Hughes, to suggest that he connect mSQL to the B+ ISAM handler in UNIREG. However, Hughes was well on his way to mSQL 2, and the company decided to create a database server for their needs.

TcX took UNIREG as a basis and used third-party mSQL utilities, wrote an API for their system, which initially closely coincided with the mSQL API. However, this allowed any mSQL user who wanted to migrate to the TcX database server to make minor changes to their code. The source code for the new database was completely original. Thus, in May 1995, the company had a MySQL 1.0 database that fully met the needs of the company.

In 1995, David Oxmark, who works for Detron HB and is a business partner of the firm, began actively encouraging TcX to distribute the MySQL database over the Internet. David even took part in the work on the documentation. As a result, version 3.11.1 of the MySQL DBMS was released in 1996 as a binary distribution for Linux and Solaris. Today, MySQL runs on many platforms and is available in both binary and source code.

MySQL has become the most popular database engine in PHP today. This is primarily due to the fact that support for this server is included in the delivery of PHP. In addition, the popularity of MySQL is facilitated by fairly good features and a wide range of standard interface functions that are extremely easy to use.

MySQL's licensing policy is more flexible than other database servers. Basically, MySQL is free unless you intend to sell it or sell the services you create with it.

MySQL has excellent portability and can just as well be used on commercial operating systems such as Solaris, Irix or Windows, and on any hardware up to powerful servers. Moreover, just like its more expensive rivals, it allows you to process large databases containing millions of records.

Name and logo

As for the name, there are several versions of its origin. The first version says that the use of the "my" prefix is ​​explained by the fact that in TcX the base directory, as well as a significant number of libraries and utilities, have been denoted by just such a prefix for a decade. Therefore, it was logical to use it in this case.

The second version, more sentimental, relies on the fact that Michael Monty Widenius named the new product MySQL after his daughter, My. The daughter of Widenius is really called My, and he himself does not refute either the first or the second version.

The MySQL dolphin logo is named "Sakila". It was chosen from a large list of user-suggested "dolphin names". The name "Sakila" was submitted by Open Source developer Ambrose Twebaze.

MySQL features

The main feature of MySQL is that it supports the SQL query language in the ANSI 92 standard, and in addition has many extensions to this standard that are not found in any other database management system.
A short list of MySQL features:

1. Efficient operation of an unlimited number of users simultaneously working with the database is supported.

2. The number of rows in tables can reach 50 million.

3. The fastest execution of commands. There is an opinion that MySQL is the fastest server in existence.

4. Simple and effective security system.

MySQL Chart Example

Disadvantages of MySQL

However, MySQL also has some drawbacks. This is mainly due to the fact that in order to achieve such a high speed, developers had to sacrifice some of the requirements for relational database management systems.

So, MySQL lacks:

1 . Support for nested queries like SELECT * FROM table1 WHERE id IN (SELECT id FROM table2) (in early versions).

2. Transaction support not implemented. Instead, it is suggested to use LOCK/UNLOCK TABLE.

3 . No support for foreign keys.

4 . No support for triggers and stored procedures.

5 . No support for views (VIEW). In version 3.23 it is planned to be able to create views.

According to the creators, it was points 2-4 that made it possible to achieve high performance. Their implementation significantly reduces the speed of the server. These features are not critical when creating Web applications, which, combined with high performance and low price, has allowed the server to become very popular.

Licensing

MySQL is dual licensed. MySQL may be distributed under the terms of the GPL license. However, under the terms of the GPL, if any program includes the MySQL source code, then it must also be distributed under the GPL license. This may be at odds with the plans of developers who do not want to open source their programs. For such cases, a commercial license is provided, which also provides high-quality service support.

Platforms

MySQL has been ported to a large number of platforms: AIX, BSDi, FreeBSD, HP-UX, Linux, Mac OS X, NetBSD, OpenBSD, OS/2 Warp, SGI IRIX, Solaris, SunOS, SCO OpenServer, UnixWare, Tru64, Windows 95, Windows 98, Windows NT, Windows 2000, Windows XP, Windows Server 2003, WinCE, Windows Vista and Windows 7. There is also a MySQL port to OpenVMS. It is important to note that on the official website of the DBMS, not only source codes are provided for free download, but also ready-made MySQL DBMS executable modules compiled and optimized for specific operating systems.

Programming languages

MySQL has APIs for Delphi, C, C++, Eiffel, Java, Lisp, Perl, PHP, Python, Ruby, Smalltalk, Component Pascal and Tcl, libraries for .NET languages, and provides support for ODBC through the MyODBC ODBC driver .

Version history

The first internal release of MySQL took place on May 23, 1995 [source unspecified 1224 days].
A version for Windows systems (Windows 95 and NT) was released on January 8, 1998.
Version 3.23: beta June 2000, release January 2001.
Version 4.0: beta August 2002, release March 2003.
Version 4.1: beta June 2004, release October 2004.
Version 5.0: beta March 2005, release October 2005.
Version 5.1: developed since November 2005, released in November 2008.
Version 5.4: April 2009 beta, has not been released.
Version 5.5: release in December 2010.
Version 5.6: in development (5.6.6 m9 August 7, 2012).

Version history


MySQL 4.0

Despite the fact that version 4.0 is outdated, it still has significant distribution. Main features of this version:

Nearly complete implementation of ANSI SQL-99, plus extensions;
cross-platform compatibility;
independent table types (MyISAM for fast reading, InnoDB for transactions and referential integrity);
transactions;
SSL support;
query caching;
replication: one master server per slave, many slaves per master;
full-text indexing and search using the MyISAM table type;
embedded database library;
support for Unicode (UTF-8);
InnoDB tables for ACID compliance;
an embedded server that allows you to include MySQL in standalone applications.

Nested queries and derived tables.
new coding and sorting system;
faster and more flexible client-server protocol with support for prepared queries, ensuring their optimal execution;
new installer and setup program for Microsoft Windows and Linux;
client-server connections secured via OpenSSL;
highly-optimized library that can be used in third-party programs;
full Unicode support (UTF-8 and UCS2);
standard GIS spatial data types, for storing geographic information;
improved full-text search and help system.

MySQL 5.0

MySQL 5.0 was released on October 24, 2005, with significant enhancements in functionality that puts MySQL on par with commercial DBMSs. If earlier the MySQL DBMS was accused of insufficient support for the SQL standard, then with the advent of the fifth version of this popular database, almost complete support for the SQL standard appeared. MySQL 5.0 contains the following innovations:
stored procedures and functions;
error handlers;
cursors;
triggers;
representation;
information schema (the so-called system dictionary containing metadata).

MySQL 5.1

MySQL 5.1 continues the path to the SQL:2003 standard. MySQL 5.1 contains the following innovations:

Sharding is the ability to split one large table into multiple parts located on different file systems based on a user-defined function. Under certain conditions, this can give a significant increase in performance and, in addition, it makes it easier to scale tables.
The behavior of a number of statements has been changed to be more compatible with the SQL2003 standard.
Row-based replication, in which only information about actually changed table rows will be written to the binary log instead of the original (and possibly slow) query text. Row replication can only be used for certain types of sql queries, in terms of MySQL - mixed replication (mixed replication).
Built-in scheduler of periodically launched jobs. In syntax, adding a task is similar to adding a trigger to a table; in ideology, it is similar to crontab.
An additional set of functions for XML processing, an implementation of XPath support.
New troubleshooting tools and performance analysis utilities. The possibilities for managing the contents of log files have been expanded, logs can now be saved in the general_log and slow_log tables. The mysqlslap utility allows you to perform load testing of the database with a record of the response time for each request.
To simplify the upgrade operation, the mysql_upgrade utility has been prepared, which will check all existing tables for compatibility with the new version and, if necessary, make the appropriate adjustments.
MySQL Cluster is now released as a standalone product based on MySQL 5.1 and the NDBCLUSTER repository.
Significant changes in the operation of MySQL Cluster, such as, for example, the ability to store table data on disk.
Reverted to using the built-in libmysqld library, which was missing in MySQL 5.0.
API for plugins that allows you to load third-party modules that extend functionality (for example, full-text search) without restarting the server.
Implementation of the full-text search parser as a plug-in.
New Maria table type (fault tolerant clone of MyISAM).

Maria table type

Maria (since version 5.2.x - Aria) is an extended version of the MyISAM repository, with the addition of means of maintaining data integrity after a crash.
Maria's main features:

In case of a crash, the results of the current operation are rolled back or return to the state before the LOCK TABLES command. Implementation through logging operations.
Ability to restore state from anywhere in the activity log, including support for CREATE/DROP/RENAME/TRUNCATE. Can be used to create incremental backups by periodically copying the activity log.
Support for all MyISAM column formats, extended with a new "rows-in-block" format that uses a paginated way of storing data, in which data in columns can be cached.
In the future, two modes will be implemented: transactional and without reflection in the transaction log, for non-critical data.
The data page size is 8Kb (in MyISAM 1Kb), which allows you to achieve better performance for indexes on fixed-size fields, but slower in the case of indexing variable-length keys.

MySQL 5.5

The MySQL 5.5 branch builds on the unreleased MySQL 5.4 series and contains a number of significant scalability and performance improvements, including:
Using the default InnoDB engine.
Support for a semi-synchronous replication mechanism based on patches to InnoDB from Google.
Improvement of data partitioning functions. Extended syntax for splitting large tables into several parts located in file systems (partitioning). Added RANGE, LIST operations and "partition pruning" optimization method.
New optimization mechanism for nested queries and JOIN operations.
The internal blocking system has been redesigned.
Integrated Google patches with InnoDB optimization on processors with a large number of cores.

MySQL 6.0

MySQL 6.0 has been frozen in alpha testing. Initially, it was decided to create version 5.2, soon this version was renamed to 6.0. However, later MySQL 6.0 information disappeared from the site, and the developers focused on version 5.5 and version 5.6 following it.
One of the main innovations of version 6.0 was a new type of Falcon table, developed as a potential replacement for InnoDB by Innobase, acquired by Oracle. In connection with the acquisition of Sun Microsystems by the same Oracle in 2010, the fate of Falcon remains in question.

Specifications

The maximum size of tables in MySQL 3.22 is up to 4 GB, in subsequent versions the maximum size is up to 8 million TB (263 bytes).
The size of a table is limited by its type. In general, the MyISAM type is limited by the file size limit of the operating system's file system. For example, in NTFS this size can theoretically be up to 32 exabytes. In the case of InnoDB, one table can be stored in several files representing a single tablespace. The size of the latter can reach 64 terabytes.

Unlike MyISAM, InnoDB has a significant limit on the number of columns that can be added to a single table. The default memory page size is 16 kilobytes, of which 8123 bytes are reserved for data. The size of the pointer to dynamic fields is 20 bytes. Thus, in the case of using the dynamic row format (ROW_FORMAT=DYNAMIC), one table can contain a maximum of 409 blob or text columns.

Starting with version 4.1, a new encoding and sorting system has been introduced in the MySQL DBMS. When using the Windows-1251 encoding, before executing SQL statements, you must configure the connection encoding using the operators:

SET character_set_client="cp1251";
SET character_set_results="cp1251";
SET character_set_connection="cp1251";

These three statements are equivalent to calling a single statement:

SET NAMES "cp1251"

The character_set_client variable sets the encoding of data sent from the client, the character_set_results variable sets the encoding of data sent to the client, the character_set_connection variable sets the encoding into which the information received from the client is converted before the request is executed on the server.

When using Unicode UTF-8, this statement looks like this:
SET NAMES "utf8"

ISO 8859-5 encoding is not supported.

In MySQL select version()- a query that returns the name of the package being used and its version. The name can be MySQL itself or its self-developed fork - MaraiDB. The difference between the packages when solving most problems is not noticeable. MySQL 5.6 corresponds to MaraiDB 10.

MySQL select version and how to know MySQL version

There are several ways to find out the version. The simplest one does not require you to know the password of the database server user. It is enough to log in via SSH and execute mysql --version

mysql Ver 14.14 Distrib 5.5.55, for debian-linux-gnu (x86_64) using readline 6.3

To use the method given in the title, you need to send an SQL request, for this you need to log in to the console (you can also do this with a script).

Enter password:
Welcome to the MySQL monitor. Commands end with ; or\g.
Your MySQL connection id is 41
Server version: 5.5.55-0ubuntu0.14.04.1 (Ubuntu)

Copyright (c) 2000, 2017, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type "help;" or "\h" for help. Type "\c" to clear the current input statement.

The necessary information is available in the output that appears after successful authorization. In this case, MySQL Server version 5.5.55-0 is used.

Also, once in the database server console, you can query the version as follows:

+————————-+
| version() |
+————————-+
| 5.5.55-0ubuntu0.14.04.1 |
+————————-+
1 row in set (0.00 sec)

In all cases considered, equally complete information was obtained.

Read a series of articles describing the basics of working with MySQL ().

If the site scripts that work with the database are written for a specific version of the software on the server and it is not used, the version, as well as the package itself, can be changed. This is done quite simply in Debian, below is the algorithm.

Changing the database server version to Debian

1) using the mysqldump utility, a dump of all tables (including service ones) is created

2) the package is removed apt-get remove mysql-server* && apt-get purge mysql-server*, you also need to delete /var/lib/mysql and /etc/mysql before making a copy

3) the repository listed on the official website is added to /etc/apt/source.list (for example, for MariaDB 10 on Debian 8), the information is updated apt-get update

3) also through apt-get a new package is installed, after which the database dumps are loaded

Copies should always be kept in case of emergencies. Different versions use different directives in the configuration files and may require manual editing.

Read about, with the help of it the version of the package was displayed, it is the selection that is the most frequent operation.

Release of the stable release of MySQL version 5.6. A lot of work has been done in the new version. The main efforts were aimed at improving performance, scalability and flexibility. The InnoDB engine has undergone major changes.

Key improvements include: support for full-text search tools, the ability to access data via the memcached API, increased performance with intensive data recording, and increased scalability when processing a large number of simultaneous requests.

Another innovation of version 5.6 is the ability to execute DDL (Data Definition Language) operations without taking the DBMS offline and interrupting access to tables. Administrators get the ability to perform operations related to resetting the schema, adding or removing data columns, or renaming columns without shutting down the DBMS. Previously, these features were only available in NoSQL products.

Compared to version 5.5, the novelty can now work on 48-core servers, against 32-core servers in MySQL 5.5

A little more about the key features:

• Implemented an interface for direct access to InnoDB tables in the style of NoSQL systems using an API that manipulates key/value pairs and is compatible with memcached.
• Now it is possible to create full-text indexes in InnoDB to organize a quick search by word forms among text content stored in InnoDB tables. Previously, full-text search was only available for MyISAM tables.
• Improving the efficiency of the query optimizer, optimizing the process of selecting the result set of values, sorting and query execution. New Index Condition Pushdown (ICP) and Batch Key Access (BKA) optimizations allow up to 280x throughput for certain queries. The efficiency of executing queries like "SELECT... FROM single_table... ORDER BY non_index_column LIMIT N;" has been increased. Improved performance of "SELECT... LIMIT N" queries that display only a portion of rows from a large selection.
• The optimizer's diagnostic tools have been expanded, EXPLAIN support has been added for INSERT, UPDATE, and DELETE operations. EXPLAIN results can now be output in JSON format. The new optimizer tracing mode allows you to trace every decision made in the query optimization process.
• Additional optimizations for subquery execution, in which nested queries of the form "SELECT ... FROM table1 WHERE ... IN (SELECT ... FROM table2 ...))" are translated into a more optimal representation at the stage before the query is directly executed, for example, they are replaced by a more efficient JOIN.
• Extension of the implementation of the PERFORMANCE_SCHEMA diagnostic system, which provides low-level tools for monitoring the execution of queries and various events during the operation of the DBMS. PERFORMANCE_SCHEMA allows you to evaluate in detail bottlenecks when executing long-running queries, as well as present summary statistics grouped by queries, threads, users, hosts, and objects.
• The implementation of the InnoDB engine has been improved, there is an increase in performance when performing transactions and during activity with a predominance of data reading operations - in some situations, the acceleration reaches 230%.
• Lazy replication mode, which allows data to be replicated not immediately, but with a certain delay, which allows you to provide protection against operator errors (for example, accidental deletion of table contents).
• Increasing the maximum size of files with change logs (InnoDB Redo Log) from 4 GB to 2 TB.
• Improved security: support for specifying authentication parameters in the .mylogin.cnf file in encrypted form; adding the sha256_password plugin for storing password hashes using the SHA-256 algorithm; adding a field to the mysql.user table with a password expiration time; new SQL function VALIDATE_PASSWORD_STRENGTH() to evaluate password strength.
• Support for starting the server in read-only mode (option --innodb-read-only, for InnoDB only).
• Support for specifying fractional seconds in the TIME, DATETIME, and TIMESTAMP functions to specify microseconds.
• Dropped support for options "--log", "--log-slow-queries", "--one-thread", "--safe-mode", "--skip-thread-priority", "--table- cache".

You can learn more about the innovations at

• Safety
• Quality
• Price
• Reliability
• Simplicity
• Stability
• Support
• Speed
• Control Panel

FAQ help section

Video hosting review

How to upload a server to FTP

ATTENTION: You only need to upload 3 folders ( filterscripts,gamemodes,scriptfiles) and 1 file server.cfg, then in server.cfg add the line (if it is not present) plugins streamer.so sscanf.so CRP.so mysql.so You also need to make sure that the mod in .amx format exists in the gamemodes folder, and the mod name is correctly spelled server.cfg (config).

FileZilla Client
Enter host Example: 194.58.88.74 - login *****- password******** IN THE PORT FIELD YOU DO NOT NEED TO ENTER ANYTHING!!!

ATTENTION: If you can't connect to FTP via FileZilla, download Total Commander and connect via it!

Total Commander- to upload your samp files to FTP
Enter host Example: 194.58.88.74 - login 173104911- password g1KdN7D3q

Where to enter? Answer: run Total Commander > Network > Connect to FTP Server > Add and then enter your data as shown in the screenshot in the example:

Mod Unknown

If you have "unknown" in the gamemode field, then do the following:
1. Shut down your server first
2.Go to the control panel in the tab Server Options > Settings
3.Add below line plugins streamer.so sscanf.so CRP.so mysql.so
Change the name of the plugins if the mod is unknown, for example: plugins streamer.so sscanf.so CRP.so mysql.so on pluginsstreamer2.7.2.so sscanf.so CRP.so mysqlR34.so
*The plugins folder is installed initially by default, it contains all the necessary plugins.
*You can install any of your plugins on ftp, then register in the control panel in the Settings section the desired plugin for the server.
*Use PAWNO to compile and update streamer
4.In a folder plugins there must be plugins with the .so extension for Linux: select the desired plugin for your server and write its name in the panel settings in the plugins line EXAMPLE: plugins streamer.so
5. Do not forget that We use OC Linux, which means that in the Panel Settings
write a line for plugins plugins: streamer.so sscanf.so CRP.so with extension .so otherwise your server will not work correctly.

For OS Linux write in server.cfg as: plugins streamer.so sscanf.so CRP.so mysql.so antiattack.so
One of the plugins libmysqlclient.so.15 libmysqlclient.so.16 libmysqlclient_r.so.16 must be located in the server folder.

Attention: if the server works correctly on Windows OS, this does not mean that it will work correctly on Linux.

What to do if after filling there are no icons, houses, businesses, etc.?

Write streamer2.5.so in the config, save and reboot the server.
Example:

plugins streamer2.5.so sscanf.so CRP.so mysql.so regex.so

How to find the plugin version?
On the local computer, start the server, then look in the log, the version of the plugin will be indicated there, this version and register on the hosting in the server config.
Example:

Server Plugins
--------------
Loading plugin: streamer.so
*** Streamer Plugin v2.6.1 by Incognito loaded ***

So in the server config you need to register the version streamer2.6.1.so

Help - Connecting mod to mysql server

Open the mod (.PWN file) with the PAWNO program, specify your data from the MYSQL section

Example:

#define mysql_host "host.site"
#define mysql_db "s20000"
#define mysql_user "s20000"
#define mysql_pass "lazyrich"

After compiling the mod in .AMX and importing the sql query into the database

Attention! If unknown appears during the compilation process, the mod will not be determined.
Exit to look for a scripter to fix the error.

To change the name of the mod, or rather the hostname parameter, you need to enter the server control panel in the -Settings section (this is the sever.cfg server config) and in the hostname line with the right to register your server name, for example: *** Our Server is the Best * **
Save the data in the panel and be sure to restart the server for the new settings to take effect.
If after all of the above the name has not changed for you, then you need to change the name in the mod itself with the PAWNO program, and this is a completely different story available on the Internet.

Server.cfg

query 1 - do not change.

maxnpc 10 - Do not change.
onfoot_rate 40 - Do not change.
incar_rate 40 - Do not change.
weapon_rate 40 - Do not change.




- standard line of plugins for samp config

How to give yourself an admin

Log in to the server folder scriptfiles, find your NICK
example: Aldo_Mangano , open file with Notepad ,
find a line AdminLevel specify 1999 then save the file and restart the server.

Server.cfg

echo Executing Server Config…
lanmode 0 - 0 - game over the Internet, 1 - game over a local network.
rcon_password 123 - "123" - password from the admin panel on the server.
maxplayers 50 - As you already understood, the maximum number of players. In version 0.3a, maximum 500.
port 7777 - The port displayed at the end of your server address. (On the hosting exposes itself)
hostname NameServer - The name of your future server.
gamemode0 mode - Game mode, your future server. More on that below...
announce 0 - 1 server is visible in the Internet tab / 0 is not visible.
query 1 - do not change.
weburl site - Server site, if any.
maxnpc 10 - Do not change.
onfoot_rate 40 - Do not change.
incar_rate 40 - Do not change.
weapon_rate 40 - Do not change.
stream_distance 300.0 - Do not change.
stream_rate 1000 - Do not change.
password - your_password (Server with a password)
language Russia - map at 0.3.7 to place map
plugins streamer.so sscanf.so CRP.so mysql.so regex.so dc_cmd.so CVector.so nativechecker.so- standard line of plugins for samp config

First, you need to decide whether you need the latest experimental release or the latest stable version:

• If you are going to be using MySQL for the first time, or are trying to port MySQL to some system that does not have a binary distribution, we generally recommend starting with the stable version (currently version 3.23). Keep in mind that all MySQL releases are tested with MySQL benchmarks and a comprehensive test suite before each release (even for experimental releases).
• If you are working on an old system and want to upgrade, but want to avoid possible upgrade inconsistencies, then you should upgrade to the newest version in the same branch you are using (where only the latest version number is newer than yours). In such versions, we try to fix only critical bugs and make only small, relatively safe changes.

Second, you need to decide whether you want to use a source distribution or a binary distribution. In most cases, it's best to opt for a binary distribution if one exists for your platform, as it's usually easier to install than a source distribution.

Installing from source may be preferable in the following cases:

• If you need to install MySQL in some explicit location (the standard binary distributions are ``ready to run'' anywhere, but you may need even more flexibility).
• To meet different user requirements, we provide two different binary versions: one is compiled with non-transactional table handlers (small, fast binary code), and the second one is configured with the most important extensibility features such as transaction-aware tables. Both versions are compiled from the same source code. All native MySQL clients can connect to both versions. The extended MySQL binary distribution is marked with the -max suffix and configured with the same options as mysqld-max . See section 4.7.5 mysqld-max , the extended mysqld server. If you want to use the MySQL-Max RPM package, you must first install the standard MySQL RPM package.
• If you need to configure mysqld with some extra features not found in the standard binary distributions. The following is a list of the most common additional options you might want to use:
  • --with-innodb
  • --with-berkeley-db
  • --with-raid
  • --with-libwrap
  • --with-named-z-lib (This is done for some binary distributions)
  • --with-debug[=full]
• By default, a binary distribution is usually compiled with support for all encodings and should run on different processors from the same processor family. If you want a faster MySQL server, you can recompile it to support only the one encoding you need, use a better compiler (like pgcc), or use compiler options that are better optimized for your processor.
• If you find a bug and report it to the MySQL development team, you should be sent a patch that should be applied to the source distribution to fix the bug.
• If you want to read (and/or modify) the MySQL source code (in C and C++), you must have a distribution of the source code. Source code is always the best documentation. Source distributions also contain more tests and examples than binary distributions.

MySQL's naming system uses release numbers, which consist of three numbers and a suffix. For example, the mysql-3.21.17-beta release is interpreted as follows:

• The first number (3) is used to describe the file format. All version 3 releases share the same file format.
• The second number (21) represents the output level. Usually there is a choice of two possibilities. One represents the release of the stable branch (currently 23) and the second represents the experimental branch (currently 4.0). Usually both branches are stable, but an experimental version may have some quirks, may lack documentation on new features, or may not compile on some systems.
• The third number (17) is the version number within the release level. This number increases for each new distribution. It usually makes sense to prefer the most recent version for the selected release level.
• The (beta) suffix indicates the stability level of a given release. The following suffixes are possible:
  • alpha indicates that the release contains large sections of new code not 100% tested. Bugs found (usually none) should be documented in the ``News'' section. See See section D History of MySQL Changes and Updates . Most releases of alpha also include new commands and extensions. While working on an alpha release, there may be active development involving significant code changes, but everything is tested before release. Any release of MySQL should be free of known bugs.
  • beta means all new code has been tested. No new properties are added that could cause damage to the old code. There should be no known bugs. The version changes from alpha to beta when no fatal bugs have been reported in the alpha version for at least a month and we don't plan to add any new features that could make the old commands less reliable.
  • gamma is a beta version that is almost finished and seems to be working well. Only minor fixes are added. This is exactly what many other companies call a release.
  • If there is no suffix, it means that the version has run on many different computer systems with no error messages other than platform-specific errors; only critical bug fixes are allowed for it. That is why we call such a release stable.

All versions of MySQL are run through our standard tests and benchmarks to ensure they are reliable in use. Since the standard tests are updated periodically to include checking for new bugs that are found and the situations that might cause them, the test suite gets better and better over time.

Note that all releases are tested with at least the following tests:

Internal Test Suite The test suite is part of the production system for the customer. This set includes many tables with hundreds of megabytes of data. MySQL Performance Test Suite These tests work on a set of commonly used queries. In addition, they allow you to see if the latest optimization package actually makes the code faster. See section. crash-me Test The test attempts to determine what functionality the database supports and what its capabilities and limitations are. See section 5.1.4 The MySQL Benchmark Suite .

There is another test. It is that we use the latest version of MySQL in our internal production environment on at least one machine. To work with this version, we have more than 100 gigabytes of data.