Archive for February, 2013

How to unlock a single login or role if all logins are locked

February 24th, 2013 No comments

By passing a parameter in runserverfile that will allow to unlock single login or role at startup time.

Paramter: -u, and is followed by the name of a login or role that is presently locked.

Categories: ASE Tags:

How to lock last login with “sa_role” role

February 24th, 2013 No comments

By default ASE doesn’t allow  to lock last unlocked login that have sa_role/sso_role role. However, it can be locked if a role has explicit password set to enable the role while login.

If a role is altered to have a limitation on failed attempts, and a login attempts to enable the role and fails the required number of times, the role is locked for all holders of the role.  Likewise, since we can’t explicitly lock the last unlocked login with sa_role or sso_role, it is possible for failed login attempts to indirectly lock that login.


February 22nd, 2013 No comments

Sybase DBA Commands:  SybaseDBA_commands

Sybase DBA Notes: Sybase DBA ImportantNotes


Please let us know, if you have any query.

Categories: ASE, Database Tags:

What is SAP HANA?

February 18th, 2013 No comments

SAP HANA can be defined as an appliance that combines SAP software components optimized on hardware provided by SAP’s leading hardware partners.  It comes in a bundle of softwares along with the hardware (servers). SAP HANA servers are sold in “t-shirt” sizes ranging from Extra-Small (128GB RAM) all the way up to Extra Large (>2TB RAM) with multicore CPUs.

SAP HANA is both a database (in the traditional sense) and a database platform (in the modern sense).

In its current form SAP HANA can be used for four basic types of use case:

1. Agile Data Mart (Stand-alone database for reporting)

2. SAP business suite accelerator (secondary database for SAP business suite for reporting, calculation and analysis purpose)

3. A primary database for SAP Netweaver warehouse.

4. A development platform for new applications


Source: SAP

Categories: ASE, Database, Developement, HANA, SAP Tags: , , ,

Column Based Search

February 17th, 2013 No comments

To store a table in memory, two option exists: 1. Row based storage and 2. Column based storage.

In row based storage, A table is stored as a sequence of records, i.e. one full row in a data page/or consecutive data pages. It means all columns values of a table stored sequentially per row.

In column based storage, column values of a column are stoger in contiguous memory location.

Advantages of column based table storage in following circumstances

1. Calculations are typically executed on a single column or few columns only.

2. Table is searched based on values of a few columns.

3. Table has large number of columns.

4. Table has large number of rows, so that columnar operations are required (aggregate, scan etc)

5. High compression rates can be achieved because the majority of the  columns contain only few distinct values (compared to the number of rows)

Advantages of row based storage in following circumstances

1. The application needs to only process a single record at one time. (This applies to many selects and or updates of single record)

2. The application typically needs to access a complete record (or row)

3. The columns contain primarily distinct values so that compression rate would be low.

4. Neither aggregations nor fast searching is required.

5. The table has small number of rows (e.g. configuration tables)


Source: SAP

SAP Sybase ASE Customer Testimonials

February 13th, 2013 No comments




Categories: ASE Tags:

Top Five Reasons to Choose SAP Sybase ASE

February 13th, 2013 No comments




Categories: ASE, Database, HANA, SAP, Start Sybase Tags:

How to handle the database objects security in database through stored procedures

February 13th, 2013 No comments

Case: An user X owns a stored procedure that access a table owned by another user Y, and that table has a trigger that updates another table owned by user Z

Clumsy Solution –> Grant explicit permissions to user X on table1 and table2, similarly grant execute permissions and table access to users Y and Z. In a production environment think of many users available in a database and thousands of objects, it is not possible.

Good Solution –> Create all objects with dbo user and provide execute permission ONLY on stored procedures to user X, thus when user would execute the stored procedure, SP would be able to modify the table1 and trigger on table1 would be able to modify tabl2, though explicit access on tables have not been granted to user X. This is how stored procedure maintain the security features. User X shall not be able to access table1 and table2 explicity but stored procedure run by user X can modify those tables.

This is how objects gets created in production environment.

How to remove an user from public group

February 13th, 2013 No comments

There is no way to remove an user from “public” group. However, you can revoke the commands permissions on given objects from “public” and thus users belongs only to given group would be able to execute those commands on those objects.

Categories: ASE Tags:

Database user group – Way to remove an user from a group

February 13th, 2013 No comments

1. Group is a database  specific.

2. An user can’t be a part of 2 different groups

3. An user can be a part of 2 groups only in case of other group is “public”.

4. An user shall always be part of “public” group .

5. To remove an user from a group (not from public) change the group of user to “public”.

sp_changegroup “public”, X

Categories: ASE Tags: