Archive

Author Archive

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 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:

SAP Hana With Free Sybase Database

January 17th, 2013 No comments

“Customers could choose to deploy ASE or Hana in whatever mix of configurations they want,” explained Prakash Darji, SAP’s global VP for data warehouse solutions & SAP Hana platform. SAP customers could use Hana to accelerate certain Business Suite processes while leaving other processes on ASE”

Source : http://www.informationweek.com/software/enterprise-applications/sap-sweetens-hana-deal-with-free-sybase/240146282?goback=.gde_4634032_member_204773060

Categories: ASE, Database Tags: , , ,

Wishing Everyone a Very Merry Christmas and a Very Happy New Year 2013!

December 25th, 2012 No comments

Wishing Everyone a Very Merry Christmas and a Very Happy New Year 2013!


Team, sybaseblog.com

Categories: ASE Tags:

ASE 15.7.0.030 (ASE 15.7 ESD#3) Released & Its New Features !

December 24th, 2012 3 comments

New features of ESD#2 and ESD#3 here:

  • Fixes: With ESD#3 you get all of the fixes for database issues that have been made available since the initial release of release 15.7.
  • In-row LOB compression: ASE can store LOB data in-row or off-row (on special LOB pages). Data compression was introduced with ASE 15.7, but in-row LOBs have not been compressed. With the new version you will get in-row LOB compression. For some SAP tables this can make a big difference. For an example, please have a look at this blog from Hüseyin Bilgen who shares his experiences.
  • Hash-based statistics: This feature helps speed up the updating of index statistics.
  • Plan sharing: In the past a database query that was executed more than once in parallel would result in multiple query plans which could be different (depending on the values provided at compilation time). When you are running ESD#3, plans for queries running in parallel are cloned, saving the cost of recompilation and ensuring that the queries use the same plan.
  • Enhanced monitoring: You will see more metrics on several screens of the DBA Cockpit. Since we are using early versions of the ESDs in our development systems, we have already been able to include some of these in the DBA Cockpit versions released during summer 2012 (such as SAP_BASIS 7.02 SP12). For example: enhanced SQL statement statistics, spinlock monitoring, separation of I/O time in read time and write time… There are also new monitoring features that are going to be used in future versions of the DBA Cockpit. One example is the new history of database and transaction dumps.
  • Talking about database and transaction dumps: There are several new features here that will make your life as a DBA easier. You can now run the dump transaction while a dump database is running. There is a new tool ‘sybrestore’ available with ESD#3 that will help you to restore the database when needed. We already updated our backup and recovery SAP Notes when ESD#2 was released to make use of the new features.
  • Reorg rebuild can be run online. I don’t think I need to say more.
  • The maximum size of a database is now 64TB. Just in case your compressed database was close to the 32TB limit before…
  • Asynchronous DB initialization: If you are expanding your database, the database is now available immediately and initialization is done in the background.

Source : http://scn.sap.com/community/sybase-ase/blog/2012/12/21/sap-on-sybase-ase-news-week-51-2012-ase-1570030-released

Categories: ASE, Database, SAP Tags: , , ,

Replication Server Interview Questions

December 20th, 2012 No comments

Guys,
Came across below Replication Server Questions, might help you for yours interview preparation. It also includes few ASE questions.
Also Updated the Interview Question Page.
Thanks,

1. What is the difference between MSA and Warm standby ?

2. How can we perform fail over in Case of Warm Stand by and MSA?

3. What will happen, if the queue has data in case of fail over to warm standby?

4. For standby point of view which one is better warm standby or MSA?

5. How can we sync the warm standby database ? If there is some data in queue, what will you do?

6. What is the config parameter you can use to tune a rep agent?

7. Suppose there are 20,000 trans which are getting fail and you need to skip all these trans using error class. Please let me know high level overview to setup
error class?

8. How the multiple replication server can improve the performance as compare to single replication server ?

9. Suppose the query is running slow , how will you investigate?

10. Suppose tempdb log segment is full, how will you troubleshoot?

11. Suppose for a very big database , backup takes 4 hrs to complete . During the backup, due to heavy activity from user log is full, after 2 hours ? What will you do now?

12. How can we guess, in how much time queue will be drain?

13. Suppose queue is getting full, what can be point of bottleneck and why?

14. Suppose log for a database is getting full, how will you trouble shoot? Why log increase is not a better idea? ( Server version is below 15.7)

15. How will you check the latency and what is the latency ?

16. Suppose you want to sync a table in a warm stand replication , How will you do?

17. What are the various factor which can effect rep agent performance?

18. How can you make sure rep agent is running fine ( means scanning is going well in Primary site)?

19. How can we see the number of commands in a transaction in queue?

20. Suppose you have 5000 locks at primary side , and your one delete statement ( which is effecting 7000 rows)went fine. Now in case of Replicate dataserver ( has same number of locks), you are getting out of lock situation? Why it was successful at primary side , what it did not go well in replicate side, despite of primary and replicate have same number of locks?

21. What are the situations when we require to drain the queues?

22. In unix , suppose one dba modifies some of files including dataserver binary to non sybase user, and you want to fix this situation asap? What you will do?

23. Suppose there is thread down issue in replication for target side, and you fetched that its down due to duplicate row? How can we make sure , is it due to duplicate row or duplicate key?

SAP D&T Academy Video – How to Create/Add a Disk Partition in SAP Sybase Replication Server?

December 20th, 2012 No comments

SAP D&T Academy Video – How to Check the Health of a SAP Sybase Replication Server?

December 20th, 2012 No comments

SAP D&T Academy Video- How to Log Trans in the Replication Exception Table?

December 20th, 2012 No comments