Archive for the ‘ASE’ Category

Stock Market Opening Timings With Reference To India Time

April 18th, 2012 1 comment

North and South America

S&P – US : 19:00 PM

Mexican Bolsa -Mexico : 18:00 PM

Brazil Bovespa : 19:30 PM

NASDAQ : 7:00 P.M.

NYSE: 8:00 P.M.
FTSE100 -UK : 21:10 PM
DAX – Germany : 21:00 PM
CAC 40 – France : 21:00 PM
Shanghai Composite – China : 07 :00 AM
Hang Seng – Hong Kong : 07 :00 AM
Nikkei – Japan : 07 :00 AM

Categories: ASE Tags:

Relation between sysdevices, sysdatabases and sysusages

April 15th, 2012 1 comment

Pre 15.x Version


1. Virtual Page Number: Virtual Page number is unique across the server, always in 2k size. Does not depend upon server page size.

2. Logial Page number : Unique across a database. Depends upon the page size of server ( 2k, 4k, 8k and 16k)

3. vdevno from sysdevice as vedno(low/2power24)&255

4. The high Order four bits of sysusage.vstart stores the virtual device number and can be calculated as vdevno=(vstart/2pow24)&255

sysdevices.low : Starting vitual page for a devices and generally calculated as vedvno*2power24

sysdevices.high : Last vitual page of the device allocation

Device Size: (sysdevices.high – sysdevices.low+1)

sysdatabase.dbid : Database Id for a database.

sysusages.vstart : is the vitual page number from where the database fragment starts

sysusages.lstart : Is the start of the logical page number

sysusages.size : Number of contiguous database (logical) pages

sysusages.dbid : Database id for  fragment.

 vstart of a database fragment is lying between the low and high of device used.


Version 15.x


1. Virtual Page Number: Virtual Page number is unique across the device, always in 2k size. It does not depend upon server page size.

2. Logial Page number : Unique across a database.

3. Now, device identification number is stored in the vdevno column and no longer as part of the high or low column.

and also no longer as part of the sysusage.vstart column.

sysdevices.low : Generally Zero , block offset of virtual page in 2K page if there is offset with vstart parameter of disk init.

sysdevices.high : Last virtual page of the device allocation

sysdevices.vdevno : Virtual device number for a device (for master device =0 and maximum value is defined by number of devices config parameter)

Device Size : (sysdevices.high – sysdevices.low+1)

sysdatabase.dbid : Database Id for a database.

sysusages.vstart : is the virtual page number from where the database fragment starts in a device specified by vdevno

sysusages.lstart : Is the start of the logical page number of the database.

sysusages.size : Number of contiguous database (logical) pages

sysusages.dbid : Database id for  fragment.

sysuages.vdevno : Vdevno of device on which database fragment is created.

These global variable always represents as

@@maxpagesize – logical page size

@@pagesize – virtual page size


Source : sybooks

Categories: ASE Tags:

Sybase ASE Indexes -2

April 11th, 2012 No comments


Creation of Indexes:

You can create the index either of two ways:

  • With Create index command
  • By specifying Integrity Constraints like Primary Key and Unique Key in create table command.

Integrity constraints (Primary and Unique Keys) have following restrictions for the indexes:

  • You cannot create non unique indexes.
  • You cannot set various setting provided by create index command like ignore_dup_key,ignore_dup_row etc.
  • You cannot drop these indexes without alter table command.

When we specify the Primary Key in create table command, it creates Unique Cluster Index and unique Key creates unique non clustered index on the column mentioned in keys.

Summarize as –

  • Primary Key in create table command ==> Creates Unique Clustered Index
  • Unique Key in create table command  ==> Creates Unique non clustered Index
  • If neither the clustered nor the nonclustered keyword is used ==> ASE will create non clustered indexes.
  • If unique keyword is not used in create index command ==> ASE will create non unique indexes.


Create Index Command Syntax:

create [unique] [clustered | nonclustered] index index_name
on [[database.]owner.]table_name
(column_expression [asc | desc]
[, column_expression [asc | desc]]…)
[with {fillfactor = pct,
max_rows_per_page = num_rows,
reservepagegap = num_pages,
consumers = x, ignore_dup_key, sorted_data,
[ignore_dup_row | allow_dup_row],
statistics using num_steps values}]
[on segment_name]

Before executing create index, turn on select into: sp_dboption,’select into’, true

The simplest form of create index is: Create index index_name on table_name (column_name)


Viewing Indexes:

  • Using sp_helpindex we can view indexes of a table. E.g. sp_helpindex ‘tablename’
  • sp_statistics also  returns a list of indexes on a table. E.g. sp_statistics ‘tablename’
  • In addition, if you follow the table name with “1”, sp_spaceused reports the amount of space used by a table and its indexes. E.g. sp_spaceused ‘tablename’,1

Dropping indexes

  • The drop index command removes an index from the database.
  • Only the owner of an index can drop it. drop index permission cannot be transferred to other users. The drop index command cannot be used on any of the system tables in the master database or in the user database.
  •  You cannot drop indexes using drop index command which were created using Integrity constraint. To drop the same indexes you should use alter table command.

Index Option ( for Create Index Command):

 i)ignore_dup_key  :

  • This option is only for unique clustered and non clustered indexes.
  • If you try to insert a duplicate value into a column that has a unique index, the command is canceled. You can avoid this situation by including the ignore_dup_key option with a unique index. Your command would be successful and it will ignore that key value (It means, finally no insert on the table).
  • You cannot create a unique index on a column that already includes duplicate values, whether or not ignore_dup_key is set.

ii) ignore_dup_row and allow_dup_row:

  • These options are only for the non unique clustered index.
  • These options are not relevant when creating a nonclustered index. Since an Adaptive Server nonclustered index attaches a unique row identification number internally, duplicate rows are never an issue—even for identical data values.
  • A nonunique clustered index allows duplicate keys, but does not allow duplicate rows unless you specify allow_dup_row. If allow_dup_row is set, you can create a new nonunique, clustered index on a table that includes duplicate rows, and you can  insert or update duplicate rows.
  • The ignore_dup_row option eliminates duplicates from a batch of data. When you enter a duplicate row, Adaptive Server ignores that row and cancels that particular insert or update with an informational error message.
  • If a table has duplicate rows and you are creating non unique clustered index with ignore_dup_key, it will delete all the duplicate rows from the table.

iii)Sorted Data:

  • The sorted_data option of create index speeds index creation when the data in the table is already in sorted order. sorted_data speeds indexing only for clustered indexes or unique nonclustered indexes.
  • Creating a nonunique nonclustered index is, however, successful, unless there are rows with duplicate keys. If there are rows with duplicate keys, an error message appears and the command is aborted.


Source :                                                                                                                                  Continue…

SAP Press Conference – April 10, 2012

April 11th, 2012 No comments


Categories: ASE Tags:

SAP Unveils Unified Strategy for Real-Time Data Management to Grow Database Market Leadership!!!

April 10th, 2012 No comments

Finally the curtain is up :

SAP today provided the following road map details and areas of strategic innovation and investment of its database portfolio to increase its database market leadership by 2015:

  • SAP HANA platform: This state-of-the-art in-memory platform is planned to be the core of the SAP real-time data platform, offering extreme performance and innovation for next-generation applications.
  • SAP Sybase ASE: SAP Sybase ASE is intended as a supported option for SAP Business Suite applications while SAP HANA is planned to augment the extreme transactions of SAP Sybase ASE with real-time reporting capabilities.
  • SAP® Sybase IQ® server: SAP Sybase IQ is planned to deliver data management for “big data” analytics, offering extreme total cost of ownership (TCO). Progressive integration with SAP HANA is intended to provide a smart store for aged/cold data. SAP Sybase IQ is envisioned to share common capabilities and life-cycle management with the SAP HANA platform.
  • SAP® Sybase® SQL Anywhere: This market-leading mobile and embedded database with millions of deployments is planned to be the front-end database for the SAP HANA platform, extending its reach to mobile and embedded applications in real time.
  • SAP® Sybase® PowerDesigner software: This flagship data modeling, information architecture and orchestration software is envisioned to become the foundation of the modeling solution for the SAP real-time data platform, offering a large base of experts to customers. Ford Motor Company recently selected the software to drive its data modeling and management and centralize all logical and physical modeling functions.
  • SAP® Sybase® Event Stream Processor (ESP) software, SAP® Sybase® Replication Server and SAP solutions for EIM: Combined, these offerings are intended to provide data assessment and integration of batch, real-time change data capture and streaming data into the SAP real-time data platform.
  • SAP real-time data platform integrated with Hadoop: SAP HANA and SAP Sybase IQ are planned to extend support for accessing “big data” sources such as Hadoop, and offer a deeply integrated pre-processing infrastructure

Source ::

Sybase ASE Indexes

April 9th, 2012 No comments


Indexes are the most important physical design element in improving database performance:

Indexes help to avoid table scans. A few index pages and data pages can satisfy many queries without requiring reads on hundreds of data pages.

Indexes in ASE:

We can divide ASE indexes in two categories by : i) Physical Order of Data with index key  ii) Uniqueness of the index column

Based on the physical order of data, Adaptive Server provides two general types of indexes that can be created at the table or at the partition level:

Clustered indexes, where the data is physically stored in the order of the keys on the index:

• For all pages-locked tables, rows are stored in key order on pages, and pages are linked in key order.

• For data-only-locked tables, indexes are used to direct the storage of data on rows and pages, but strict key ordering is not maintained.

Non clustered indexes, where the storage order of data in the table is not related to index keys

Based on index column uniqueness, indexes can be unique and non unique.

So following types of indexes present in ASE with permutation and combination with above two properties:

1. Unique Clustered Indexes

2. Non unique Clustered Indexes

3. Unique Non-clustered Indexes

4. Non unique Non-clustered indexes


Clustered Index Non Clustered Indexes
Unique Unique Clustered Index Unique Non Clustered Index
Non – Unique Non Unique Clustered Index Non Unique Non Clustered Index

So, all the indexes come under above 4 types:


In case of more than one index column, we can add prefix composite in above types.

Means Composite indexes are those indexes, which are created on more than on one column. Above four types of index can be composite as well.

In the case of partitions, we can categories above types as local and global indexes.Local indexes get created at partition level and table level index called as Global indexes.

Global indexes with one index tree cover the whole table, or local indexes with multiple index trees, each of which covers one partition of the table.

Function-based indexes are a type of non clustered index which use one or more expressions as the index key.


What is “going concern” concept and how it relates to Kingfisher Airlines nowadays?

April 9th, 2012 No comments

A “going concern” refers to a company’s ability to continue functioning as a business entity in the near future. It is extremely rare that auditors make such mention in the passing.

However, Kingfisher Airline auditors asked if Kingfisher Airlines could be even described as a ‘going concern’. Means auditors were suspicious about that company would able be survive in near future, that’s why it was possible that KFA could even be described as ‘going concern’


Categories: ASE Tags: , ,

Business Exposed To Risks

April 9th, 2012 2 comments

Every business is exposed to 3 types of risks.

1. Market Risk

2. Credit Risk

3. Operational Risk


Market Risk: Market risk is referred to as decline in value of investment over a given period of time due to economic slowdown, policy changes or any other event that may impact the market.


Credit Risk: Credit risk is basically an investment risk of lose incurred from borrower’s default.


Operational Risk: Operational risk arises from failed or inadequate internal process, people or any other external event.


If we take latest example of Kingfisher Airlines, I would consider it exposed to primarily operational risk and secondary market risk.


Primarily Operational Risk is because since it’s inception in 2006 it has never made any profit and in-spite of that extra services have been provided continuously, without strengthen it’s presence in domestic market and gaining experience in aviation industry, it has been opened for international routes and etc.


Secondary Market Risk because of rise in fuel prices and taxes, however these are valid for all aviation  industry but other companies are still making profit. So I have consider these elements as secondary.

Categories: ASE Tags: ,

Leverage Sybase with Finance

April 9th, 2012 No comments

As we all aware of the fact that Sybase is a preferred database in finance industry. Hence, we are leveraging this Sybase blog with finance relating posting.

So enjoy and contribute.



Sybanva & Sybanurag

Categories: ASE Tags:

Structural changes at SAP presage major database push

April 6th, 2012 No comments

When SAP bought Sybase back in 2010, it appeared that the main target was its mobility software. Sybase’s core and original business – database – was widely perceived as a ‘nice to have.’ It was making money and it had some very loyal customers – and a good position in financial services, a vertical SAP is targeting for growth. But the mobility piece was the jewel in the crown: everyone wanted mobile-enabled SAP (or was expected to).


by Philip Carnelley


Full Story  & Source ::

Categories: ASE, News Tags: