SAP Sybase ASE Q&A Bank
Wait is over Now !!
Please download the Complete ebook for SAP Sybase ASE Q&A Bank Version 1.0 as below:
Wait is over Now !!
Please download the Complete ebook for SAP Sybase ASE Q&A Bank Version 1.0 as below:
SAP Sybase ASE | SAP Sybase IQ | SAP HANA |
High performance, reliable, scalable and resource-efficient OLTP database. Heavily optimize ASE for virtualized and cloud infrastructure | Aims to provide maximum performance and efficiency when running both OLTP and OLAP workloads on the SAME DATA and at the SAME TIME | |
Capability to handle transactional workloads. It is good to chose in case of budgetary constraints. | In- memory database, very high capability to handle transactional workloads. | |
SAP Sybase ASE is planned to be the preferred transactional database in the SAP Real-Time Data Platform for running SAP applications, SAP partner applications and custom applications | SAP HANA is planned to be the preferred database in the SAP Real-Time Data Platform for applications that need to run analytic and transactional workload on the same data at the same time | |
Sybase IQ is planned to focus on evolving columnar compression capabilities for effectively storing and processing data | SAP HANA is planned to leverage IP from Sybase IQ, such as in-database algorithms, Hadoop integration, index optimizations, and ELT capabilities for performing transforms in the Hana database | |
Plan to leverage Sybase IQ as near-line storage for SAP BW as well as leverage the technology in SAP ILM portfolio for archiving from the Business Suite | Plan to leverage SAP HANA as database for native applications, SAP BW, as well as the Business Suite | |
High-performance analytics server planned to deliver cost effectively for large volume data scenarios
Open platform for large scale data warehouse Analytical data mart for aged data in a BW+HANA+IQ scenario Cost effective data management scaling to extreme data volumes
|
Real-time platform for analytics and applications that simplified data management approaches to deliver real-time results
Operational / agile data mart for real-time scenarios Analytical data mart for complex real-time calculations Database for BW powered by SAP HANA |
SAP Sybase ASE | SAP Sybase IQ | SAP HANA |
High performance, reliable, scalable and resource-efficient OLTP database. Heavily optimize ASE for virtualized and cloud infrastructure |
|
Aims to provide maximum performance and efficiency when running both OLTP and OLAP workloads on the SAME DATA and at the SAME TIME |
Capability to handle transactional workloads. It is good to chose in case of budgetary constraints. | In- memory database, very high capability to handle transactional workloads. | |
SAP Sybase ASE is planned to be the preferred transactional database in the SAP Real-Time Data Platform for running SAP applications, SAP partner applications and custom applications
|
SAP HANA is planned to be the preferred database in the SAP Real-Time Data Platform for applications that need to run analytic and transactional workload on the same data at the same time
|
|
Sybase IQ is planned to focus on evolving columnar compression capabilities for effectively storing and processing data
|
SAP HANA is planned to leverage IP from Sybase IQ, such as in-database algorithms, Hadoop integration, index optimizations, and ELT capabilities for performing transforms in the Hana database
|
|
Plan to leverage Sybase IQ as near-line storage for SAP BW as well as leverage the technology in SAP ILM portfolio for archiving from the Business Suite | Plan to leverage SAP HANA as database for native applications, SAP BW, as well as the Business Suite | |
High-performance analytics server planned to deliver cost effectively for large volume data scenarios
Open platform for large scale data warehouse Analytical data mart for aged data in a BW+HANA+IQ scenario Cost effective data management scaling to extreme data volumes
|
Real-time platform for analytics and applications that simplified data management approaches to deliver real-time results
Operational / agile data mart for real-time scenarios Analytical data mart for complex real-time calculations Database for BW powered by SAP HANA
|
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?
Follow the below video for “How to start and stop replication server”
Follow the below video for “How to Rename Sybase ASE server”