Archive for the ‘ASE’ Category

SAP Recognized as a Market Leader by Gartner, Inc. in Operational Database Management Systems Magic Quadrant

November 17th, 2013 No comments

As per Gartner:


Located in Walldorf, Germany, SAP ( has several DBMS products that are used for transaction systems: SAP Sybase Adaptive Server Enterprise (ASE), SAP Sybase iAnywhere and SAP Hana. Both ASE and iAnywhere are available as software only, while SAP Hana is marketed as an appliance.

  • Vision leadership — Moving into DBMS technology, SAP has introduced SAP Hana as an in-memory platform for hybrid transaction/analytical processing (HTAP) and acquired Sybase to add to the DBMS product line.

  • Strong DBMS offerings — In addition to SAP Hana, SAP Sybase ASE continues to support global-scale applications and was first to introduce an in-memory DBMS (IMDBMS) version.

  • Performance — References cited performance (scalability and reliability) as a major strength (one of the highest scores), mostly for SAP Sybase ASE.

Source :




Trick to unhide the sqltext of a procedure

August 2nd, 2013 1 comment

One fine morning  you want to see the code for a stored procedure but what happen if the text of the proc is hideen through sp_hidetext ?
I am sure you guys know that, once a stored proc is hidden through sp_hidetext, this can not be reverse .

This will even get worse if you do not have a OS level file backup of that proc any where on your server machines or local machines . Even your DBA friends do not have the back up on their desktops/laptops.  This seems to be a very rare scenario but some times it happens 🙂
I was in this challenging  scenario … was able to find a crack to unhide the code for a hidden proc . Sharing on this forum.

Here you GO!

1>Shutodwn <sybase_server>

2>Start sybase server on diagnostic mode.

$SYBASE/ASE-15_0/bin>  diagserver -usa -s<sybase_server> -p”password” -d<Master_device_path>

3>use <database_name>

create table #m( id int)
insert into #m values(object_id(“proc_name”))

dbcc _unhide_text(‘#m’)
sp_helptext “proc_name”    ———You can see the proc text now !!! HURRY!!!

4> checkpoint
Shutdown the sybase_server

5>Start sybase_server in normal mode

 Note – Pls. do not try this on your production set up as this is not  documented…but you are open to load your production data on UAT/dev and explore.

Categories: ASE Tags:

SAP® Sybase® IQ Software Smashes Previous Results and Sets World Record for Fastest Loading of Big Data

July 27th, 2013 No comments

SAP® Sybase® IQ Software Smashes Previous Results and Sets World Record for Fastest Loading of Big Data

ASE 15.7 SP100: Sybase ASE’s version numbering goes the SAP way

June 25th, 2013 No comments

Need of In-memory Technology : SAP HANA

May 6th, 2013 No comments

Challenge 1: Massive Data Growth

Massive amounts of data is being created every year and as per he IDC EMC report data growth would be 40K Exabytes by 2020 :

Capture 2

Challenge 2: Fast access to business decision making information.

Business & People want fast exact and correct answer of all questions from this massive amount of data.

Challenge 3: Current Technologies Can not deliver with this massive data growth.

Historical DBMS :

Historically database systems were designed to perform well on computer systems with limited RAM, this had the effect that slow disk I/O was the main bottleneck in data throughput. Consequently the architecture of these systems was designed with a focus on optimizing disk access, e. g. by minimizing the number of disk blocks (or pages) to be read into main memory when processing a query.

New Hardware Architecture ( up to or more 128 Cores of CPU and 2TB of RAM)

Computer architecture has changed in recent years. Now multi-core CPUs (multiple CPUs on one chip or in one package) are standard, with fast communication between processor cores enabling parallel processing. Main memory is no-longer a limited resource, modern servers can have 1 TB of system memory and this allows complete databases to be held in RAM. Currently server processors have up to 80 cores, and 128 cores will soon be available. With the increasing number of cores, CPUs are able to process increased data per time interval. This shifts the performance bottleneck from disk I/O to the data transfer between CPU cache and main memory


Need of In-memory Technology SAP HANA :

From the discussion above it is clear that traditional databases might not use current hardware most efficiently and not able to fulfill current and future business need.

The SAP HANA database is a relational database that has been optimized to leverage state of the art hardware. It provides all of the SQL features of a standard relational database along with a feature rich set of analytical capabilities.

Using groundbreaking in-memory hardware and software, HANA can manage data at massive scale, analyze it at amazing speed, and give the business not only instant access to real time transactional information and analysis but also more flexibility. Flexibility to analyze new types of data in different ways, without creating custom data warehouses and data marts. Even the flexibility to build new applications which were not possible before.

HANA Database Features

Important database features of HANA include OLTP & OLAP capabilities, Extreme Performance, In-Memory , Massively Parallel Processing, Hybrid Database, Column Store, Row Store, Complex Event Processing, Calculation Engine, Compression, Virtual Views, Partitioning and No aggregates. HANA In-Memory Architecture includes the In-Memory Computing Engine and In-Memory Computing Studio for modeling and administration. All the properties need a detailed explanation followed by the SAP HANA Architecture.

Source : www, and emc and idc reports.


Migrating SAP Sybase ASE from AIX to Linux

May 1st, 2013 No comments

Always consider to migrate the Development environment first , then UAT. Before moving to production Perform Regression testing on UAT enviornment.

Please consider to create the script to perform update stats,xp_postload(drop and re create index) for each and every database.

Steps for an ASE Database( You can repeat same steps for other databases) :

Step 1: Run the consistency checks in ASE database in Source (AIX) environment, to make sure that everything is fine.

Step 2: Put the database in single user mode.

Step3: Make sure there is no user activity on the Source Database .

Step 4: Run the sp_flushstats in the database.

Step 5: Take the backup of the database in Source (AIX) environment.

Step 6: Ftp the Files to Target environment. (AIX to Linux)

Step 7: Create and build the dataserver and databases in target Linux environment with exactly same configuration.
You might require to change some of the config param in Linux environment for performance point of view. ( Lets not discuss it here, as it is out of context).

Step 8: Also migrate the Login, roles from source server to target server

Step 9: Load the database in Linux environment.
(If there were user activity during dump process, load will be fail.)

Step 10: Online the database. If the target ASE version is new with source, It will also perform upgrade in this step.

Step 11:  Fix the corrupt indexes using the xp_postload. If the Database size is more than 20G, try drop and re-create index , in this case xp_postload would not be effective.

Step 12: Update the stats on all tables.

Step 13:  If there is replication setup in your environment, please setup replication after that.

Issue Faced:

1. If there is any user online during backup process, your load will fail( in the step for cross platform conversion).

2. After online database, we seen the -ve values in sp_helpdb output for few databases. There are two ways to fix this :

i) Try to run dbcc

dbcc usedextents(<DB name or DB ID>, 0, 1, 1)

ii) Use the Traceflag  7408 and 7409 in Run Server file and reboot the instance. It will not take much time as compare first option.

Traceflag 7408 : Force the server to scan *log segment* allocation pages; to recalculate free log space rather than use saved counts at boot time.
Traceflag 7409 : Force the server to scan *data* segment allocation pages; to recalculate free data page space rather than use saved counts at boot time.

Please let me know if you are planning for migration and need any assistance.

SAP Sybase ASE Q&A Bank

April 29th, 2013 1 comment

Wait is over Now !! 

Please download the Complete ebook for SAP Sybase ASE Q&A Bank Version 1.0  as below:















Perl Interview Questions And Answers

April 1st, 2013 2 comments

Perl Interview Questions And Answers: [Download not found]

Categories: ASE Tags:

Introducing SAP Sybase IQ 16 : Extreme Delivery

March 3rd, 2013 No comments

Newest Features

For those who are familiar with earlier versions of Sybase IQ, here are the new features added to from SAP Sybase IQ 15.

  • Performance enhancements: The column store engine has been enhanced with extreme compression capabilities that improve I/O rates and reduce the amount of data to be stored on disk.
  • High-speed data loading: High-performance data loading ingests large amounts of data faster than ever — from terabytes to petabytes — making big data available to applications and people faster.
  • Improved scalability: Key improvements maintain high performance and efficiency for the growing volume of unpredictable, user-driven analytic workloads.
  • Data protection: Administrators have further options for protecting the security of enterprise systems.
  • Heightened availability: Enhancements help ensure that enterprise data is always available to business-critical analytics and dashboards.




Big Data tools cost too much, do too little:SHOCKING REVELATION!!!

March 3rd, 2013 No comments


Big data is a necessity at scale: if you’re trying to listen to every transatlantic phonecall, you need to use MapReduce. … if you need to search the entire internet in milliseconds you need to use MapReduce, if you need to run the largest social network in the world you need to use MapReduce. If you don’t you can probably scale with a database.

Full Story @