How to change SAP Hana Sql Output results are limited to 5000 Records

How to change SAP Hana Sql Output results are limited to 5000 Records

These are quick fixes that are often overlooked because the products come with standard configurations.

The SAP Hana SQL Output results in ECLIPSE, for example, have a limit of 5000 records.

With the following setup, you can change this number to a higher one.

Windows Tab - > Preference -> General - > Runtime - > Result -> Maximum number of rows displayed in results. 

2147483647 is usually the maximum record that can be achieved.

How I Start and Stop SAP HANA Tenant Databases — My Go-To Methods

 Managing SAP HANA tenant databases is something I’ve had to do regularly, especially during system maintenance or troubleshooting. Whether you're using command-line tools or graphical interfaces, the process is pretty straightforward once you get the hang of it.

🖥️ Using the Command Line

When I’m working directly on the server, I prefer using the HDB command. It’s quick and reliable.

• To start a tenant database, I use:

  Code

  hdbsql -i <instance number> -u SYSTEM -p <password> "ALTER SYSTEM START DATABASE <tenant_name>"
  

• To stop a tenant database, I run:

  Code

  hdbsql -i <instance number> -u SYSTEM -p <password> "ALTER SYSTEM STOP DATABASE <tenant_name>"
  

These commands are executed via hdbsql, SAP’s SQL command line tool. You’ll need the correct instance number and credentials, of course.

🧪 Using SAP HANA Studio

If I’m in a GUI mood or working remotely, SAP HANA Studio makes it easier:

• I right-click on the system database connection, then navigate to the “Configuration” tab.

• Under the “Landscape” view, I can see all tenant databases listed.

• From there, I right-click on the tenant I want to manage and choose either “Start” or “Stop”.

It’s visual, intuitive, and great for monitoring the status of multiple tenants at once.

🧭 SAP HANA Cockpit (Optional)

In some setups, I’ve also used SAP HANA Cockpit — a web-based interface. It allows you to:

• View tenant status

• Start/stop tenants

• Monitor performance and alerts

Though not always available in every environment, it’s a solid option when configured.

What I Learned About Inactive Objects in SAP (SE80 / SE11)

When I first started working with ABAP development in SAP, I kept running into something called “inactive objects.” At first, I didn’t think much of it — but during system upgrades and transports, they became a real headache. Here’s how I came to understand and manage them.

🔍 What Are Inactive Objects?

Inactive objects are basically unfinished or unactivated changes in the system. They show up when you:

• Modify a program, table, or structure

• Save your changes but don’t activate them

Sometimes it’s because the object has syntax errors, or maybe you got pulled into another task and forgot to activate. Either way, these objects sit in the system and can cause issues later — especially during upgrades or transports.

🛠️ How I Found Them Using SE80

In SE80 (Object Navigator), there’s a handy way to search for inactive objects:

• Go to the Repository Browser

• Use the dropdown to select “Inactive Objects”

• By default, it filters by your username — but you can remove that to see all users’ inactive items

You’ll see a list organized by object type (Programs, Tables, Classes, etc.). Just a heads-up: the nodes don’t expand automatically, so I had to manually click and use the arrow keys to open them.

🧪 SE11 and Other Transactions

You can also spot inactive objects in SE11 (Data Dictionary), SE38 (ABAP Editor), or SE24 (Class Builder). If you’ve saved changes but haven’t activated them, the system will show a warning or highlight the object as inactive.

⚠️ Why They Matter

Inactive objects aren’t always a problem — until they are. For example:

• During an SAP system upgrade, all inactive objects must be cleaned up

• If a report or function module is called, the system uses the last activated version, not the latest saved one

• This can lead to confusion if your changes aren’t reflected in runtime

✅ What I Did to Fix Them

When I needed to clean up inactive objects:

• I reviewed the list in SE80 and activated the ones I recognized

• For objects with errors, I fixed the syntax and reactivated

• If I wasn’t sure who created them, I checked the assigned user and reached out to the developer

In some cases, I had to delete old or unused objects from the DWACTIV table — but only after confirming they weren’t needed.

How I Kill SAP HANA Sessions When Things Get Stuck

There was a time when our SAP HANA system started lagging badly — CPU usage spiked, memory was maxed out, and users were getting frustrated. After digging into the performance dashboard, I found a few long-running sessions hogging resources. That’s when I learned how to properly terminate them.

🛠️ Method 1: Using SQL Command Line (hdbsql)

This is my go-to method when I’m working directly on the server. I use the following command to cancel a session:

sql

ALTER SYSTEM CANCEL SESSION '<connection_id>';

You just need the connection ID of the session you want to kill. It’s fast and works well for most cases.

🧪 Method 2: SAP HANA Studio

If I’m using the graphical interface, I go to:

• Performance → Sessions

• Right-click on the session that’s causing trouble

• Select Cancel Session

It’s intuitive and gives you a clear view of what each session is doing.

🧭 Method 3: SAP GUI via DBACOCKPIT

In some setups, I use transaction code DBACOCKPIT:

• Navigate to Performance → Threads

• Find the problematic thread

• Click Cancel Threads

This method is useful if you’re working from SAP GUI and want to avoid command-line tools.

🧱 Method 4: Using hdbcons (Advanced)

For deeper control, I sometimes use:

bash

hdbcons 'connection c <conn_id>'

This is more technical and usually reserved for system administrators who need to dig into the internals.

Prince 2 Agile approach on SAP enterprise projects

 It's strange that in SAP projects, SAP Activate are the content to be used in a guided way to conduct,engage into a project or execute BAU activity that are similar to a project. 

However there's always this craving where Programme Manager whom is in charge of the project managers and would always wants to report to the board or rather the PM itself would like to report to the Board / Stakeholders using Prince 2 framework, reporting structure and its methodology. Although since prince 2 carries Agile word in it, that does not differ so much on SAP Activate. But on a broader audience the world outside SAP  likes Prince 2 Agile approach and mostly merging them with SAP Activate approach. 

This also could be because the board or stakeholder might not live or use SAP, since SAP is mostly related to IT projects. However Prince 2 are applicable broadly on any non IT projects as well. that's the reason why such preference are adapted. 

Having said such , SAP Activate is always the key for running SAP projects regardless implementation, migration, BAU and others. 

In a single word SAP Activate methodology in Agile meaning flexibility to deliver your projects and not getting locked into waterfall methodology.

What i know about SAP Patch day

When I first started managing SAP systems, I quickly learned that SAP Patch Day is a big deal. It’s basically the day when SAP releases its latest security updates—kind of like a monthly health check for your system. It usually happens on the second Tuesday of every month, and it’s when SAP publishes what they call Security Notes. These notes contain fixes for vulnerabilities that could be exploited if left unpatched.

I think of it like this: just like your phone gets software updates to fix bugs and improve security, SAP systems need the same kind of attention. But because SAP is used for critical business operations—finance, HR, supply chain—you can’t afford to ignore these updates. A missed patch could mean exposing sensitive data or opening the door to cyberattacks.

What I usually do is check the list of new Security Notes released on Patch Day, figure out which ones apply to the systems I manage, and then prioritize them based on how severe the issues are. Some are labeled as “Hot News,” which means they’re urgent and need to be addressed immediately. Others are less critical but still important.

The key is not just knowing that Patch Day exists, but having a process in place to review, test, and apply these patches regularly. It’s part of keeping the SAP environment secure and compliant with industry standards.

How I Handle SAP HANA Database Restore and Track Its Progress

Restoring a SAP HANA database isn’t just about clicking “recover” and walking away — it’s a process I monitor closely, especially during critical system recovery or migration. Here’s how I typically approach it.

🧰 Step-by-Step: How I Perform the Restore

When I need to restore a HANA tenant or system database, I usually:

• Log into SAP HANA Studio or Cockpit using the SYSTEM user.

• Right-click on the database (either SYSTEMDB or tenant) and choose “Recover”.

• Select the appropriate backup image from the catalog — either file-based or Backint.

• Choose the restore type (complete recovery, point-in-time, etc.).

• Confirm and start the recovery process.

I always make sure the target instance is in a ready state and that the backup catalog is accessible before initiating anything.

📊 How I Monitor Restore Progress

SAP HANA doesn’t show a flashy progress bar during restore — so I rely on log files and trace directories to track what’s happening behind the scenes.

Here’s what I do:

• Navigate to the trace directory:

  Code

  /hana/shared/<SID>/HDB<instance>/hostname/trace/
  

• Look for the file named backup.log — this is where all restore activity is recorded.

• Use commands like:

  bash

  more backup.log | grep 'RECOVERY'
  

  to filter entries related to the restore process.

In the log, I can see entries like:

Code

RECOVERY progress of service: indexserver, volume: 3, 31% 59/189
RECOVERY progress of service: indexserver, volume: 3, 34% 65/189

These tell me exactly how far along the restore is — both in percentage and data blocks.

⏱️ How I Check Restore Duration

To calculate how long the restore took:

• I look for the start and end timestamps in the same backup.log file.

• For example:

  Code

  #####START OF THE RECOVERY##### 2025-09-15T11:32:16
  #####END OF RECOVERY##### 2025-09-15T17:48:10
  

• From this, I know the restore took just over 6 hours.

This helps me estimate future restore windows and plan downtime more accurately.

SAP Hana Numeric Error Codes, How I Understand SAP HANA Error Codes

When I first started working with SAP HANA, I quickly realized that the system communicates problems through numeric error codes. These codes aren’t just random numbers—they’re like shorthand messages that tell you what went wrong and where to look.

🔍 How I Understand SAP HANA Error Codes

Each numeric code in SAP HANA represents a specific type of issue. Instead of giving long descriptions, the system throws out a number, and it’s up to us to interpret it. Over time, I’ve learned to group these codes based on the nature of the problem:

🧩 Common Categories I’ve Encountered

1. General Warnings and Errors

• These are the mild ones. A warning might mean something didn’t go perfectly, but it’s not a showstopper.

• A general error usually means the system hit a snag, but it’s not clear exactly what caused it—so you need to dig deeper.

2. Memory and Resource Issues

• If you see an error about memory, it means the system tried to do something but didn’t have enough RAM or disk space.

• These are serious because they can crash processes or slow everything down.

3. Invalid Inputs or Arguments

• These errors pop up when you feed the system something it doesn’t expect—like a wrong data type or an out-of-range value.

• It’s like trying to fit a square peg in a round hole; the system just says “nope.”

4. Authentication and Permissions

• If you’re not allowed to do something—like access a table or run a query—you’ll get an error code related to security.

• It’s the system’s way of saying, “You don’t have the keys to this door.”

5. Transaction Failures

• These are more complex. They happen when something goes wrong during a database transaction—like a deadlock, a timeout, or a rollback.

• It’s like trying to save a file while someone else is editing it at the same time—conflicts arise.

6. File and Disk Errors

• These codes show up when the system can’t read or write to a file, or when storage runs out.

• It’s a reminder to check your infrastructure, not just your code.

🧠 Why These Codes Matter to Me

Understanding these codes has saved me countless hours. Instead of guessing what went wrong, I can look at the number, match it to the category, and start troubleshooting with purpose. It’s like having a map in a maze—still tricky, but way better than wandering blind.