http://goo.gl/EmKxy0

Archive

Archive for the ‘News’ Category

Configuring sqsh – Interactive database shell- replacement for isql

January 7th, 2014 No comments

Sqsh (pronounced skwish) is short for SQshelL (pronounced s-q-shell), it is intended as a replacement for the venerable ‘isql’ program supplied by Sybase.

Sqsh is much more than a nice prompt, it is intended to provide much of the functionality provided by a good shell, such as variables, aliasing, redirection, pipes,back-grounding, job control, history, command substitu-tion, and dynamic configuration. Also, as a by-product of the design, it is remarkably easy to extend and add functionality.

Sqsh was developped by Scott C. Gray, and is currently maintained by Michael Peppler (mpeppler@peppler.org) and also by Martin Wesdorp (mwesdorp@users.sourceforge.net).

You can download sqsh from Source Forge.

Sqsh is held under the GNU General Public License (GPL) and therefore may be freely distributed under the terms of this license.

Basic instructions for Setup :

1. Download the sqsh from here.
sqsh-1

2. Extract  the sqsh tar :
sqsh-2
3. After extract , you will have following directories :
sqsh-3
4.  Move to sqsh directory and create the installation dir with permission to sybase user (in my case installation dir /opt/sqsh). After that execute ./configure –prefix=”/opt/sqsh”sqsh-4
5. Run the make in same dir as below sqsh-5
6. Now finally run the make install sqsh-6
7. Install the manual pages for sqsh as
sqsh-7
8. Move to /opt/sqsh/bin and try to connect data server using sqsh
[sybase@LinuxServer ~]$ cd /opt/sqsh
[sybase@LinuxServer sqsh]$ cd bin
[sybase@LinuxServer bin]$ pwd
/opt/sqsh/bin
[sybase@LinuxServer bin]$ ls -ltr
total 588
-rwxr-xr-x. 1 sybase sybase 599071 Jan  7 15:51 sqsh
[sybase@LinuxServer bin]$ sqsh -v
sqsh-2.4
[sybase@LinuxServer bin]$ sqsh -U sa -S LINUX_PROD
sqsh-2.4 Copyright (C) 1995-2001 Scott C. Gray
Portions Copyright (C) 2004-2013 Michael Peppler and Martin Wesdorp
This is free software with ABSOLUTELY NO WARRANTY
For more information type ‘\warranty’
Password:
[4] LINUX_PROD.master.1> select @@servername,getdate();
 ———————————————————— ——————-
 LINUX_PROD                                                   Jan  7 2014  3:58PM

(1 row affected)
[5] LINUX_PROD.master.1>

You can configure sqsh prompt using /opt/sqsh/etc/sqshrc.  Like in sqshrc file I changed my prompt as ;
#\set prompt=’[$histnum] ${DSQUERY}.${database}.${lineno}> ‘
\set prompt=’${DSQUERY}.${database}.${lineno}> ‘

Now see the prompt of sqsh with history , also I suppressed the banner message using -b
[sybase@LinuxServer bin]$ sqsh -b -SLINUX_PROD -Usa
Password:
LINUX_PROD.master.1> select @@servername,getdate()
LINUX_PROD.master.2> go
———————————————————— ——————-
LINUX_PROD                                                   Jan  7 2014  4:06PM
(1 row affected)
LINUX_PROD.master.1>

Link from Rob Tricks with sqsh & Manual Page for sqsh

SAP® Sybase® Adaptive Server® Enterprise Gains Momentum With Rapid Customer Adoption

November 17th, 2013 No comments

 

In less than 18 months since the offering’s release in April 2012, more than 1,000 customers have chosen to run SAP Business Suite on SAP Sybase ASE and there are more than 2,000 customer installations. Both new and existing SAP customers can run a high-performance relational database management system (RDBMS) optimized for SAP Business Suite that helps improve operational efficiency and significantly reduce overall costs. The announcement was made at the SAP Database and Technology Partner Summit in Barcelona.

Source :: http://www.prnewswire.com/news-releases/sap-sybase-adaptive-server-enterprise-gains-momentum-with-rapid-customer-adoption-229819941.html

http://www.hispanicbusiness.com/2013/11/5/sap_sybase_adaptive_server_enterprise_gains.htm

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.

 

IQ16-Engine

 

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 @ http://www.theregister.co.uk/2013/02/28/hadoop_no_sql_dont_believe_the_hype/

 

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

 

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 (23)

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)

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)

 

 

sybaseblog.com completed 3 years !!

October 5th, 2012 No comments

Dear All,

It gives me an immense pleasure to share with you all that we have completed eventful journey of 3 years of sybaseblog.com. Though journey has been slow, it has been steady. We all know that steady and slow wins the race.

Since we started our blog 3 years before, then on world was going through turmoil of economic slowdown, lack of faith in technology etc. but at the same time Sybase was writing its success story differently. Sybase has been acquired by SAP as a preferred database for the ERP SAP, its growth directly/indirectly increased manifold. It got wings and reaching in new dimensions. New avenues have been opened for the Sybase.

In last three years, we started from a blog and grew to knowledge partner in Sybase Database world though trainings and seminars.
Since now we all are part of now SAP Sybase community, we have miles to go ahead and to achieve better things together.

At last I would like to thank once again to all of you for  support and the opportunity to serve you.

- Team, sybaseblog.com.