> For the complete documentation index, see [llms.txt](https://www.pranaypourkar.co.in/the-programmers-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.pranaypourkar.co.in/the-programmers-guide/interview-guide/technical/sql-interview-companion/sql-practice-problems/set-1.md).

# Set 1

## Display 9th record from employees table

```
-- Solution 1 using rowid
select rowid, first_name from employees where rowid = 
(
    select rowid from employees where rownum <= 9 
    minus 
    select rowid from employees where rownum < 9
);

-- Solution 2 using rownum
select * from 
(
select rownum r, e.* from employees e where rownum <= 9 order by employee_id
) a where a.r = 9
```

## Display 5 TO 7 records from employees table

```
-- Solution 1 using rowid
select rowid, first_name from employees where rowid in 
(
    select rowid from employees where rownum <= 7 
    minus 
    select rowid from employees where rownum < 5
);

-- Solution 2 using rownum
select * from 
(
select rownum r, e.* from employees e where rownum <= 9 order by employee_id
) a where a.r >= 5 and a.r <= 7
```

## Delete The Repeated Rows from employees table

```
DELETE FROM employees WHERE rowid NOT IN 
(SELECT MIN(rowid) FROM employees GROUP BY ename);
```

## Display the names of the employees who earn highest salary in their respective departments

```
select * from employees where (DEPARTMENT_ID,salary) in 
(select DEPARTMENT_ID, max(salary) from employees group by DEPARTMENT_ID);
```

## Display the names of employees whose names have second alphabet A in their names

```
SELECT ename FROM emp WHERE ename LIKE ‘_A%’;
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.pranaypourkar.co.in/the-programmers-guide/interview-guide/technical/sql-interview-companion/sql-practice-problems/set-1.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.