http://goo.gl/EmKxy0

Archive

Archive for the ‘ASE’ Category

SAP HANA: A Real-Time Challenge to the Oracle empire

December 15th, 2012 No comments

When Tom Cruise’s character in Top Gun exclaimed “I feel the need, the need for speed”, you’d be forgiven for mistaking it for a soundbite from a CIO discussing their transactional databases.

Read Full Article @ http://www.zdnet.com/sap-hana-a-real-time-challenge-to-the-oracle-empire-7000008177/

Planning to move Oracle to Sybase , You must Know !

December 11th, 2012 No comments

Oracle products vs. Sybase products

Both Oracle and Sybase provide a range of database-related products. The following list illustrates how the main high-level Oracle products compared to Sybase products. While this list is deliberately kept brief, it provides some basic guidance on how Oracle and Sybase can be aligned.

Oracle SAP Sybase
Oracle Database Server Sybase ASE (Adaptive Server Enterprise)
Oracle OLAP and DW Sybase IQ
Oracle Analytics Sybase IQ
Oracle RAC Sybase ASE Cluster Edition
Oracle Times Ten Sybase ASE In-Memory Database
Oracle Streams/Golden Gate Sybase Replication Server
Oracle Data Guard Sybase Mirror Activator/Sybase Replication Server

About Sybase ASE
Sybase ASE is the database that powers Wall Street. ASE has been delivering rock-solid reliability and top-level performance for the past 25 years. Sybase ASE has a lower total cost of ownership than Oracle, and delivers better performance on the same hardware. Sybase ASE is ready to be the database in any application that runs on Oracle today.

SAP D&T Academy Video: How to install sybsyntax db in ASE server

November 22nd, 2012 2 comments

Please follow the following video for installing the sybsyntax db in ASE server.

 

 

SAP D&T Academy Video:How to create login in Sybase ASE

November 22nd, 2012 No comments

Please follow the following video for creating login in Sybase ASE

 

SAP D&T Academy Video :How to set database options in sybase ASE

November 22nd, 2012 No comments

Please follow the following video for setting sybase database options.

 

Procter&Gamble’s plan to migrate their SAP ERP systems from Oracle to ASE

November 22nd, 2012 No comments

 

In the vein, SAP also announced Wednesday that high-profile customer Procter & Gamble is “planning to migrate its existing SAP ERP environment to ASE database.” P&G currently runs SAP on Oracle, and it also uses Oracle Exadata for data warehousing. If P&G follows through with this plan, it would be a financial blow and, more significantly, a big symbolic blow to the industry’s biggest database supplier.

 

They have migrated their SAP based Oracle driven Analytical Servers on to Sybase ASE 15.7. The POC has been done for migrating 13 TB of data and more to happen yet.

 

Source :

http://news.silobreaker.com/sap-innovation-halo-drives-strong-quarter-5_2266072367966978065

http://www.informationweek.com/software/enterprise-applications/sap-innovation-halo-drives-strong-quarte/240010579

 

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

Sybase CEO John Chen Left SAP After Successful Integration of Sybase

November 1st, 2012 1 comment

SAP AG (SAP) is losing a top executive from Sybase Inc., the largest acquisition in the German software company’s history, after fully integrating the maker of mobile applications for business management

Some Comments :

Chen, i started my career in 1999 as a Sybase consultant and from that time i am following Sybase and still continuing. You have  made a great company and it is a classic story of  rebirth. You deserve full credit to what Sybase is today. I still remember the stock price from $2 when you took over and reaching a peak of mid $30 and then subsequent sales to SAP. I am a optimimist and still believes “SAP & Sybase marriage is made in heaven” . All the best for you Chen ” You are a great leader , innovator , strategist  and a game changert and your story with Sybase  will be remembered in the history books as one of the classics”.  Good luck for your next venture.

 

Source : http://www.businessweek.com/news/2012-10-30/sap-loses-sybase-s-chen-after-gaining-blueprint-for-deals

http://www.bloomberg.com/article/2012-10-30/aElmqt8q7ntU.html

Categories: ASE, News, SAP Tags: , , , , ,

To Get all index size in a Database :sp__getallindexsize

October 17th, 2012 No comments

You can get all index size in a Database by using sp__getallindexsize as below :

I used the posted method to calculate index size : Calculating Table & Index Usage in ASE

Down load the stored proc here: sp_getallindexsize.sql (26)

1> use pubs3
2> go
1> sp__getallindexsize
2> go
table_name      index_name            size  reserved unused
————— ——————— —– ——– ——
authors         aunmind               2 KB  32 KB    30 KB
roysched        titleidind            2 KB  32 KB    30 KB
titleauthor     auidind               2 KB  32 KB    30 KB
salesdetail     titleidind            2 KB  32 KB    30 KB
titleauthor     titleidind            2 KB  32 KB    30 KB
salesdetail     salesdetailind        2 KB  32 KB    30 KB
titles          titleind              2 KB  30 KB    28 KB
blurbs          tblurbs               14 KB 16 KB    2 KB
sales           sales_8320029642      2 KB  16 KB    14 KB
stores          stores_7840027932     2 KB  16 KB    14 KB
titles          titles_6720023942     2 KB  16 KB    14 KB
authors         authors_5760020522    2 KB  16 KB    14 KB
publishers      publishers_6240022232 2 KB  16 KB    14 KB
store_employees store_empl_8960031922 2 KB  16 KB    14 KB

(14 rows affected)
(return status = 0)

Calculating Table & Index Usage in ASE

October 17th, 2012 No comments

sysindexes Contains

  • one row for each clustered index ( ie no row for table if CI is available)
  • one row for each nonclustered index,
  • one row for each table that has no clustered index,
  • one row for each table that contains text or image columns.
  • one row for each function-based index or index created on a computed column.

For Caluluating the size for each index and table we can use below table

First Row (indid >1) : For NCI , we will calculate index and reserved usage as below , it will not contain table size.
Second Row (indid=0) : For a table only, we can calculate usage as specified in below table
Third Row (indid =1) : As we know, CI resides tigtly couple with table so its size will also include table size.

 

indid Data Pages Index Page Reserved Pages
>1(NCI) data_pages(db_id(), tabid,indid) reserved_pages(db_id(), tabid, indid)
0(TBL) data_pages(db_id(), tabid,indid) reserved_pages(db_id(), tabid, indid)
1(CI) data_pages(db_id(), tabid,0) data_pages(db_id(), tabid,1) reserved_pages(db_id(), tabid, indid)+reserved_pages(db_id(), tabid, 0)

For calulating the Table size

1. If the table has CI

Add All NCI usages for each columns with CI usages i.e. Calulate row 1st for all NCI and add all with  3 rd row .

2. If the table does not has CI :

Add All NCI usages for each columns with Table Usage i.e Calulate 1st row for all NCI and add all with 2nd row.

Categories: ASE Tags:

Backup Server Traceflags

October 13th, 2012 No comments

Backup Server Traceflags

 Backup Server trace flag: 1 : Prints blocksize used during a dump or a load.
 Backup Server trace flag: 2 : Prints i/o optimization parameters used during a dump or a load.
 Backup Server trace flag: 3 : Allow dumping to the /dev/null device.
 Backup Server trace flag: 4 : Prints allocation percentage of the allocation units during dump.
 Backup Server trace flag: 5 : Prints the database pagesize used during a dump or a load.
 Backup Server trace flag: 6 : Sets tracing ON for the external API module.
 Backup Server trace flag: 7 : Disable locking on a file/device.

How Can we Enable:

SYB_BACKUP…qatraceon <traceflag> : Turn On a particuar trace flag
SYB_BACKUP…qatraceon 0 : Display the all enabled traceflags
SYB_BACKUP…qatraceoff <traceflag> : Turn Off a particuar trace flag
SYB_BACKUP…qatraceoff 0 : Turn Off all trace flags

1> SYB_BACKUP…qatraceon 1
2> go
Backup Server: 3.59.1.1: Turning on Backup Server trace flag: 1
(return status = 0)
1> SYB_BACKUP…qatraceon 2
2> go
Backup Server: 3.59.1.1: Turning on Backup Server trace flag: 2
(return status = 0)
1> SYB_BACKUP…qatraceon 3
2> go
Backup Server: 3.59.1.1: Turning on Backup Server trace flag: 3
(return status = 0)
1> SYB_BACKUP…qatraceon 4
2> go
Backup Server: 3.59.1.1: Turning on Backup Server trace flag: 4
(return status = 0)
1> SYB_BACKUP…qatraceon 5
2> go
Backup Server: 3.59.1.1: Turning on Backup Server trace flag: 5
(return status = 0)
1> SYB_BACKUP…qatraceon 6
2> go
Backup Server: 3.59.1.1: Turning on Backup Server trace flag: 6
(return status = 0)
1> SYB_BACKUP…qatraceon 7
2> go
Backup Server: 3.59.1.1: Turning on Backup Server trace flag: 7
(return status = 0)
1> SYB_BACKUP…qatraceon 0
2> go
Backup Server: 3.63.1.1: Backup Server trace flag: 1 is on. This flag does the following: Prints blocksize used during a dump or a load.
Backup Server: 3.63.1.1: Backup Server trace flag: 2 is on. This flag does the following: Prints i/o optimization parameters used during a dump or a load.
Backup Server: 3.63.1.1: Backup Server trace flag: 3 is on. This flag does the following: Allow dumping to the /dev/null device.
Backup Server: 3.63.1.1: Backup Server trace flag: 4 is on. This flag does the following: Prints allocation percentage of the allocation units during dump.
Backup Server: 3.63.1.1: Backup Server trace flag: 5 is on. This flag does the following: Prints the database pagesize used during a dump or a load.
Backup Server: 3.63.1.1: Backup Server trace flag: 6 is on. This flag does the following: Sets tracing ON for the external API module.
Backup Server: 3.63.1.1: Backup Server trace flag: 7 is on. This flag does the following: Disable locking on a file/device.
(return status = 0)

1> dump database model to “/tmp/model.dmp”
2> go
Backup Server session id is: 42. Use this value when executing the ‘sp_volchanged’ system stored procedure after fulfilling any volume change request from the Backup Server.
Backup Server: 4.173.1.1: The database pagesize is ’2048′ bytes.
Backup Server: 4.41.1.1: Creating new disk file /tmp/model.dmp.
Backup Server: 6.28.1.1: Dumpfile name ‘model122871499A  ‘ section number 1 mounted on disk file ‘/tmp/model.dmp’
Backup Server: 4.166.1.1: Using dbiosize of 262144 bytes for device /tmp/model.dmp.
Backup Server: 4.165.1.1: Using iocount of 1 for device /tmp/model.dmp.
Backup Server: 4.166.1.2: Using zonesize of 262144 bytes for device /tmp/model.dmp.
Backup Server: 4.166.1.3: Using blocksize of 65536 bytes for device /tmp/model.dmp.
Backup Server: 4.165.1.2: Using numzones of 3 for device /tmp/model.dmp.
Backup Server: 4.155.1.1: Using maximum block size of 65536 bytes for device /tmp/model.dmp.
Backup Server: 4.169.1.1: Dumping entire allocation unit of virtual disk /opt/sybase/new15/ASE/data/master_PROD_ASE_DS.dev, allocation page number 0 having reserved percentage 56% and cumulative allocation percentage 43%.
Backup Server: 4.169.1.1: Dumping entire allocation unit of virtual disk /opt/sybase/new15/ASE/data/master_PROD_ASE_DS.dev, allocation page number 0 having reserved percentage 56% and cumulative allocation percentage 43%.
Backup Server: 4.169.1.1: Dumping only allocated pages of virtual disk /opt/sybase/new15/ASE/data/master_PROD_ASE_DS.dev, allocation page number 256 having reserved percentage 56% and cumulative allocation percentage 22%.
Backup Server: 4.169.1.1: Dumping only allocated pages of virtual disk /opt/sybase/new15/ASE/data/master_PROD_ASE_DS.dev, allocation page number 512 having reserved percentage 56% and cumulative allocation percentage 21%.
Backup Server: 4.169.1.1: Dumping only allocated pages of virtual disk /opt/sybase/new15/ASE/data/master_PROD_ASE_DS.dev, allocation page number 768 having reserved percentage 56% and cumulative allocation percentage 16%.
Backup Server: 4.169.1.1: Dumping only allocated pages of virtual disk /opt/sybase/new15/ASE/data/master_PROD_ASE_DS.dev, allocation page number 1024 having reserved percentage 56% and cumulative allocation percentage 0%.
Backup Server: 4.169.1.1: Dumping only allocated pages of virtual disk /opt/sybase/new15/ASE/data/master_PROD_ASE_DS.dev, allocation page number 1280 having reserved percentage 56% and cumulative allocation percentage 0%.
Backup Server: 4.188.1.1: Database model: 820 kilobytes (100%) DUMPED.
Backup Server: 3.43.1.1: Dump phase number 1 completed.
Backup Server: 3.43.1.1: Dump phase number 2 completed.
Backup Server: 3.43.1.1: Dump phase number 3 completed.
Backup Server: 4.188.1.1: Database model: 828 kilobytes (100%) DUMPED.
Backup Server: 3.42.1.1: DUMP is complete (database model).

1> SYB_BACKUP…qatraceoff 0
2> go
(return status = 0)
1> SYB_BACKUP…qatraceon 0
2> go
(return status = 0)