Not sure what you have read about LDAP, but as you refer to a SQL DB, you most likely think that LDAP is a kind of relational database which can be used as a data storage for everything.
The Lightweight Directory Access Protocol is a technology that
originated from the development of X.500 protocol specifications and
implementations. LDAP was designed as a means of rapidly searching
through X.500 information. Later LDAP was adapted as an engine that
could drive its own directory database. LDAP is not a database per se;
rather it is a technology that enables high-volume search and locate
activity from clients that wish to obtain simply defined information
about a subset of records that are stored in a database. LDAP does not
have a particularly efficient mechanism for storing records in the
database, and it has no concept of transaction processing nor of
mechanisms for preserving data consistency. LDAP is premised around
the notion that the search and read activity far outweigh any need to
add, delete, or modify records. LDAP does provide a means for
replication of the database to keep slave servers up to date with a
master. It also has built-in capability to handle external references
and deferral. [Source]
In other words, there are LDAP protocol and LDAP server. The protocol is used for accessing a directory, which can be external, such as Microsoft Active Directory, or internal, on LDAP server that has own application specific database. Read What is LDAP used for?, When to use LDAP over a database?, and many other similar topics.
P.S. it's called "lightweight" because it's a subset of another protocol (X.500) which is complex and heavyweight. See https://support.microsoft.com/en-us/kb/196455