Oracle SQL: Understanding RANK() and DENSE_RANK()
This article clarifies the key differences between the RANK()
and DENSE_RANK()
functions in Oracle SQL, focusing on their ranking behavior, particularly when dealing with ties and NULL values.
Key Differences:
Both functions assign ranks to rows within a dataset based on specified ordering. The crucial difference lies in their handling of ties:
-
RANK()
: Assigns the same rank to tied rows, resulting in gaps in the ranking sequence. If multiple rows share a rank, the next rank skips over the tied ranks. For instance, if three rows tie for second place, they'll all receive a rank of "2", and the next rank will be "5". -
DENSE_RANK()
: Assigns consecutive ranks without gaps, even with ties. There's no skipping of ranks; the ranking sequence remains continuous.
Practical Application: Finding the nth Highest Salary
To retrieve the nth highest salary from the emptbl
table using RANK()
, you could use a query similar to this (though more efficient methods exist):
SELECT empname FROM (SELECT empname, RANK() OVER (ORDER BY sal DESC) as sal_rank FROM emptbl) WHERE sal_rank = n;
This ranks salaries in descending order and filters for the row with the desired rank.
NULL Value Handling:
The treatment of NULL values depends on the ORDER BY
clause. If NULLs are ordered first (ORDER BY sal NULLS FIRST
), they'll receive the lowest rank. If ordered last (ORDER BY sal NULLS LAST
), they'll receive the highest rank.
Illustrative Example:
Let's examine this with sample data:
<code>DEPTNO EMPNAME SAL ------------------------------ 10 rrr 10000.00 11 nnn 20000.00 11 mmm 5000.00 12 kkk 30000.00 10 fff 40000.00 10 ddd 40000.00 10 bbb 50000.00 10 ccc 50000.00</code>
The query:
SELECT empname, deptno, sal, RANK() OVER (PARTITION BY deptno ORDER BY sal NULLS FIRST) as rnk, DENSE_RANK() OVER (PARTITION BY deptno ORDER BY sal NULLS FIRST) as drnk_first, DENSE_RANK() OVER (PARTITION BY deptno ORDER BY sal NULLS LAST) as drnk_last FROM emptbl;
Produces results clearly showing the difference: rnk
demonstrates rank skipping, while drnk_first
and drnk_last
show consecutive ranking with NULLs handled differently. The output table would visually represent the distinct ranking behaviors. (Note: The example assumes a table named emptbl
exists with the provided data; replace with your actual table name.)
The above is the detailed content of What's the Difference Between RANK() and DENSE_RANK() in Oracle SQL?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

The default user name of MySQL is usually 'root', but the password varies according to the installation environment; in some Linux distributions, the root account may be authenticated by auth_socket plug-in and cannot log in with the password; when installing tools such as XAMPP or WAMP under Windows, root users usually have no password or use common passwords such as root, mysql, etc.; if you forget the password, you can reset it by stopping the MySQL service, starting in --skip-grant-tables mode, updating the mysql.user table to set a new password and restarting the service; note that the MySQL8.0 version requires additional authentication plug-ins.

GTID (Global Transaction Identifier) ??solves the complexity of replication and failover in MySQL databases by assigning a unique identity to each transaction. 1. It simplifies replication management, automatically handles log files and locations, allowing slave servers to request transactions based on the last executed GTID. 2. Ensure consistency across servers, ensure that each transaction is applied only once on each server, and avoid data inconsistency. 3. Improve troubleshooting efficiency. GTID includes server UUID and serial number, which is convenient for tracking transaction flow and accurately locate problems. These three core advantages make MySQL replication more robust and easy to manage, significantly improving system reliability and data integrity.

There are three ways to modify or reset MySQLroot user password: 1. Use the ALTERUSER command to modify existing passwords, and execute the corresponding statement after logging in; 2. If you forget your password, you need to stop the service and start it in --skip-grant-tables mode before modifying; 3. The mysqladmin command can be used to modify it directly by modifying it. Each method is suitable for different scenarios and the operation sequence must not be messed up. After the modification is completed, verification must be made and permission protection must be paid attention to.

MySQL main library failover mainly includes four steps. 1. Fault detection: Regularly check the main library process, connection status and simple query to determine whether it is downtime, set up a retry mechanism to avoid misjudgment, and can use tools such as MHA, Orchestrator or Keepalived to assist in detection; 2. Select the new main library: select the most suitable slave library to replace it according to the data synchronization progress (Seconds_Behind_Master), binlog data integrity, network delay and load conditions, and perform data compensation or manual intervention if necessary; 3. Switch topology: Point other slave libraries to the new master library, execute RESETMASTER or enable GTID, update the VIP, DNS or proxy configuration to

The steps to connect to the MySQL database are as follows: 1. Use the basic command format mysql-u username-p-h host address to connect, enter the username and password to log in; 2. If you need to directly enter the specified database, you can add the database name after the command, such as mysql-uroot-pmyproject; 3. If the port is not the default 3306, you need to add the -P parameter to specify the port number, such as mysql-uroot-p-h192.168.1.100-P3307; In addition, if you encounter a password error, you can re-enter it. If the connection fails, check the network, firewall or permission settings. If the client is missing, you can install mysql-client on Linux through the package manager. Master these commands

InnoDB implements repeatable reads through MVCC and gap lock. MVCC realizes consistent reading through snapshots, and the transaction query results remain unchanged after multiple transactions; gap lock prevents other transactions from inserting data and avoids phantom reading. For example, transaction A first query gets a value of 100, transaction B is modified to 200 and submitted, A is still 100 in query again; and when performing scope query, gap lock prevents other transactions from inserting records. In addition, non-unique index scans may add gap locks by default, and primary key or unique index equivalent queries may not be added, and gap locks can be cancelled by reducing isolation levels or explicit lock control.

Toalteralargeproductiontablewithoutlonglocks,useonlineDDLtechniques.1)IdentifyifyourALTERoperationisfast(e.g.,adding/droppingcolumns,modifyingNULL/NOTNULL)orslow(e.g.,changingdatatypes,reorderingcolumns,addingindexesonlargedata).2)Usedatabase-specifi

The function of InnoDBBufferPool is to improve MySQL read and write performance. It reduces disk I/O operations by cacheing frequently accessed data and indexes into memory, thereby speeding up query speed and optimizing write operations; 1. The larger the BufferPool, the more data is cached, and the higher the hit rate, which directly affects database performance; 2. It not only caches data pages, but also caches index structures such as B-tree nodes to speed up searches; 3. Supports cache "dirty pages", delays writing to disk, reduces I/O and improves write performance; 4. It is recommended to set it to 50%~80% of physical memory during configuration to avoid triggering swap; 5. It can be dynamically resized through innodb_buffer_pool_size, without restarting the instance.
