#MaxDB

[verysharpfish]

I wish my dad had named a database management system after me, wouldn't that be sick

[uswanth-123]

Database Administration in SAP Basis

Database Administration in SAP Basis: A Vital Backbone for Your SAP Landscape

SAP Basis forms the administrative core of SAP systems. One of the most crucial aspects within Basis is database administration, ensuring the databases that power your SAP applications remain healthy, optimized, and secure. Let’s dive into the key concepts and tasks of database administration in the world of SAP Basis.

Understanding Database Options in SAP

SAP systems are compatible with a range of database platforms. Here are some of the most common ones you might encounter:

SAP MaxDB: A database management system (DBMS) developed by SAP, known for its ease of use and administration.

Oracle: A powerful and widely adopted commercial DBMS offering high performance and scalability.

IBM Db2: A popular database solution from IBM, recognized for its stability and reliability.

Microsoft SQL Server: A flexible DBMS from Microsoft commonly used in Windows-based environments.

SAP HANA: SAP’s in-memory database designed for lightning-fast analytics and real-time data processing.

Key Tasks for SAP Basis Database Administrators

The responsibilities of an SAP Basis database administrator (DBA) are extensive and critical. Here are some core areas:

Installation and Configuration:  Setting up new databases, applying patches, and configuring them to work seamlessly with your SAP landscape.

Performance Monitoring and Tuning: Keeping a close eye on crucial metrics like disk space, response times, and query performance. You’ll often need to troubleshoot bottlenecks and optimize settings to maintain a responsive system.

Backup and Recovery:  Developing and executing robust backup strategies to protect your valuable business data. In case of failures or disasters, you’ll be responsible for restoring your databases to ensure business continuity.

Security and Authorization Management:  Implementing security measures to prevent unauthorized access to sensitive data. This includes managing database users, roles, and access rights in line with your organization’s security policies.

Transport Management:  Handling the movement and synchronization of database objects like schemas and tables between different SAP environments (development, testing, production).

Problem Solving and Troubleshooting: Diagnosing and resolving database-related issues, such as performance degradation, errors, or connectivity problems.

Tools of the Trade

SAP Basis DBAs utilize a suite of tools to effectively carry out their duties:

BR*Tools: A set of utilities offered by SAP for Oracle, IBM DB2 and other databases. These tools are essential for tasks like backups, restores, reorganizations, and updates.

Database Management Tools: Native tools provided by the respective database vendors (e.g., SQL Server Management Studio, Oracle Enterprise Manager) offer comprehensive management capabilities.

SAP Solutions:

CCMS (Computer Center Management System): Integrated within SAP, CCMS provides monitoring, alerting, and some administrative functions.

Database Studio (for SAP MaxDB): A versatile tool for managing and monitoring SAP MaxDB databases.

Staying on the Cutting Edge

The field of database administration is constantly evolving. Here’s how to stay ahead of the curve as an SAP Basis DBA:

Continuous Learning: Explore new database technologies, best practices, and SAP updates.

Community Resources: Leverage resources like the SAP Community Network for peer advice and solutions.

Training and Certifications: Enhance your skills through official SAP training and pursue certifications to validate your expertise.

In Conclusion

Effective database administration is the bedrock of a smoothly running SAP system. SAP Basis DBAs hold a pivotal role in safeguarding the integrity, performance, and security of the data that drives business operations. By understanding the nuances of database administration and leveraging appropriate tools, you can ensure that your SAP landscape thrives.

You can find more information about SAP  BASIS  in this  SAP BASIS Link

 

Conclusion:

Unogeeks is the No.1 IT Training Institute for SAP  BASIS Training. Anyone Disagree? Please drop in a comment

You can check out our other latest blogs on  SAP  BASIS here – SAP BASIS Blogs

You can check out our Best In Class SAP BASIS Details here – SAP BASIS Training

 Follow & Connect with us:

———————————-

For Training inquiries:

Call/Whatsapp: +91 73960 33555

Mail us at: info@unogeeks.com

Our Website ➜ https://unogeeks.com

Follow us:

Instagram: https://www.instagram.com/unogeeks

Facebook:https://www.facebook.com/UnogeeksSoftwareTrainingInstitute

Twitter: https://twitter.com/unogeek

#Unogeeks #training #Unogeekstraining

[sololinuxes]

Diferencias entre MySQL y MariaDB

Diferencias entre MySQL y MariaDB. Al mencionar MySQL y MariaDB, hablamos de los sistemas de gestión de bases de datos más usados a nivel mundial. La competencia es sana siempre que sea constructiva, pero no siempre fue así, o tal vez si, lo explicamos un poco. Ulf Michael Widenius (conocido como Monty), lanzó en 1996 junto a otros colaboradores la primera versión de MySQL. Hablamos del primer sistema de gestión de bases de datos de código abierto, puedes imaginar que supuso un bombazo con rotundo éxito a nivel mundial. Poco tardaron en llover las ofertas de compra, pero en MySQL imponen sus condiciones. En 2008 MySQL se formaliza su venta a Sun Microsystems (1.000 millones de dólares), pero se obliga a Sun a comprometerse sobre la comercialización de MySQL, siempre será open source. Además, Monty y su equipo pasarán a formar parte de Sun Microsystem como responsables del desarrollo del sistema de gestión de bases de datos. Estamos en 2008. Poco duró la feliz alianza, muy poco. Apenas unos meses después, en enero de 2009, el gigante Oracle Corporation se hace con Sun Microsystem a cambio de 5.750 millones de dólares, al día siguiente Monty y su equipo de desarrolladores se marchan para montar su propia empresa. Ríos de tinta se han escrito sobre el porqué se marcharon de la nueva adquisición de Oracle, yo creo que es evidente. Oracle Corporation pagó un sobrecoste del 42% por acción del valor real, algo realmente sospechoso e inusual. El nuevo propietario tampoco quiso comprometerse sobre MySQL como 100% open, a la vista lo tenemos ya que actualmente las versiones mejoradas de MySQL tienen un alto coste. Mi opinión personal: Oracle no solo se quitó de un plumazo una competencia real, sino que se quedó con los desarrollos del sistema de gestión de bases de datos orientados a internet (sitios web). Poco después de la adquisición, Oracle lanzó la nueva versión de su base de datos Oracle con propiedades integradas específicas para sitios web. En la siguiente agregaron más de 400 funciones nuevas, que como denunció publicamente Ulf Michael provenían de MySQL y sus proyectos futuros. Monty y su equipo de desarrolladores crean una nueva empresa, y nace MariaDB, una bifurcación de MySQL de alto rendimiento en la que confían la gran mayoría de distribuciones linux actuales. Los creadores originales de MySQL expusieron sus motivos del porqué nace MariaDB. Los principales creadores de MySQL deben permanecer juntos, es la única forma posible de mantener un sistema de gestión de bases de datos, excelente. Fomentar la continuidad del desarrollo por parte de la comunidad. Garantizar que siempre esté disponible MySQL de forma gratuita. Una vez conocemos un poco de la historia de MySQL, vemos sus principales diferencias.  

Diferencias entre MySQL y MariaDB

Quien usa MariaDB y MySQL Vemos algunos de los principales clientes de los dos sistemas de bases de datos. MariaDB Grandes corporaciones y los gigantes de linux utilizan MariaDB, podemos señalar las más conocidas: Google, Craigslist, Wikipedia, archlinux, RedHat, CentOS, Fedora, Suse, Ubuntu, AWS, 1and1, BlaBlaCart, Nokia, Samsung, y muchos más. MySQL Muchas de las grandes empresas que usan MySQL, no tienen fácil su migración a otro sistema. La lista es larga: GitHub, US Navy, NASA, Tesla, Netflix, WeChat, Facebook, Zendesk, Twitter, Zappos, YouTube, Spotify, y muchos más.   Compatibilidad entre MySQL y MariaDB MySQL: MySQL es un sistema de gestión de bases de datos relacionales (RDBMS). Al igual que otros sistema similares usa tablas, restricciones, disparadores, roles, procedimientos almacenados y vistas como componentes centrales de trabajo. Cada tabla se compone de filas, y cada fila contiene un mismo conjunto de columnas. MySQL utiliza claves primarias para identificar cada fila (llamado registro) de la tabla, y claves externas para verificar la integridad referencial de dos tablas relacionadas. MariaDB: Como MariaDB es una bifurcación de MySQL, la estructura de la base de datos y los índices son los mismos. Esto permite migrar de MySQL a MariaDB sin tener que modificar nuestras aplicaciones, los datos y estructuras serán los mismos. La conclusión es: Los archivos de configuración de datos y las tablas son compatibles. Las estructuras, protocolos y las API de cliente son las mismas. Los conectores MySQL también trabajan con MariaDB. El equipo de desarrollo de MariaDB intenta mantener una compatibilidad directa, mensualmente se compara y combina el código MariaDB con el código MySQL. Incluso la mayoría de comandos son los mismos, como mysqldump o mysqladmin.Aun así, existen diferencias entre MariaDB y MySQL que podrían llegar a causar problemas de compatibilidad mínimos. La migración de MySQL a MariaDB por parte de potencias empresariales como, Samsung o Google, no sentó nada bien en el seno de Oracle. Ahora mismo intentan diferenciarse de forma gradual, y un buen ejemplo lo encontramos en el diccionario de datos internos que se desarrolló para MySQL 8, que altera la forma en que los metadatos se guardan y utilizan. MariaDB no tiene esa función, y esto puede ser el principio del fin de la compatibilidad a nivel de archivo de datos entre MySQL y MariaDB.

Principales diferencias entre MariaDB y MySQL   Rendimiento y los índices Es evidente que el sistema de índices mejoran el rendimiento de la base de datos, ya que permite al servidor localizar y recuperar filas de manera mucho más rápida. Pero ojo, los índices pueden llegar a sobrecargar el servidor de bases de datos, se deben usar con prudencia. A pesar de lo dicho, el índice es indispensable. Si no tuviéramos índice, una búsqueda comenzaría por la primera fila de una tabla y correlativamente seguiría buscando hasta encontrar el objeto. El tiempo de espera se podría demorar en exceso. Como norma general los índices MySQL y MariaDB (PRIMARY KEY, UNIQUE, INDEX y FULLTEXT) se guardan como B-trees (Árbol-B). Existen excepciones como índices para tipos de datos espaciales, estos usan Árboles-R. También se admiten índices hash, y el motor InnoDB que utiliza listas invertidas para los índices FULLTEXT.   Diferencias en la sintaxis Las consultas son exactamente las mismas, en este apartado no tenemos nada que reprochar. Como ejemplo vemos cómo seleccionar registros de la tabla clientes. # MariaDB SELECT * FROM clientes; # MySQL SELECT * FROM clientes;   Sistemas compatibles con MariaDB y MySQL Dónde y cómo instalar MySQL El sistema MySQL está escrito en C y C ++, y tiene binarios para los sistemas: Microsoft Windows, OS X, Linux, AIX, BSDi, FreeBSD, HP-UX, IRIX, NetBSD, Novell Netware y otros. Puedes descargar MySQL desde su página oficial de descargas. Existe mucha documentación e instrucciones para los sistemas operativos más utilizados, puedes descargarlos aquí. Dónde y cómo instalar MariaDB MariaDB está escrito en C, C ++, Bash y Perl, y tiene soporte para los siguientes sistemas: Microsoft Windows, Linux, OS X, FreeBSD, OpenBSD, Solaris, y muchos más. Puedes descargar MariaDB desde su página oficial, pero al ser un sistema tan extendido en la comunidad linux, seguro que la encontraras en los repositorios de tu distribución linux. Su documentación oficial es amplia, pero mi recomendación es que acudas a la comunidad de tu distro, seguro que podrás aclarar tus dudas, ademas y no menos importante en tu idioma materno. Recuerda que MariaDB se diseño para ser el reemplazo comunitario de MySQL, el proceso de desinstalar MySQL e instalar MariaDB es bastante simple. Nunca olvides que después de ejecutar la operación debes usar mysql_upgrade.   Agrupación y replicación Qué es la agrupación La agrupación en clúster de bases de datos, es el uso de almacenamiento compartido y más servidores front-end. Los servers front-end comparten una dirección IP y el nombre de la red del clúster, que los usuarios utilizan. Se calcula cual de ellos atiende la solicitud de clientes actual. Qué es la replicación La replicación es el proceso que nos permite tener varias copias generadas automáticamente, de las bases de datos. Se conocen como "maestras" y "esclavas" y sus beneficios son importantes. Mejor soporte. Mejora considerable del rendimiento al tener la carga distribuida. Permite operar en una bases de datos esclava, sin reducir el rendimiento de la base de datos principal (cargas intensivas o de larga duración). MySQL La replicación en MySQL es asincrónica y unidireccional, un servidor actúa como maestro y otros como esclavos. Permite replicar todas las bases de datos, bases de datos específicas, e incluso una sola tabla. MySQL Cluster proporciona el soporte para los clústeres compartidos, incluye la auto-fragmentación para un correcto mantenimiento del sistema de gestión MySQL. MariaDB MariaDB también ofrece replicación maestro-maestro y maestro-esclavo. A partir de MariaDB 10.1, Galera se incluye como clúster en MariaDB. Habilitar la agrupación es muy fácil, tan solo debemos configurar unos pocos parámetros.   Conectores de bases de datos Los conectores son estándares de acceso, que tienen como objetivo hacer posible el acceso a un dato de la de de datos. Conectores de MySQL MySQL ofrece una variedad de conectores de bases de datos, se incluyen: C, C ++, Delphi, Perl, Java, Lua, .NET, Node.js, Python, PHP, Lisp, Go, R, D y Erlang. Conectores de MariaDB MariaDB también tiene una gran variedad de conectores, como: ADO.NET, C, C ++, D, Java, JavaScript, ODBC, Perl, PHP, Python, Ruby y Visual Studio.   De donde viene el nombre de MySQL, MariaDB y MaxDB Curiosa anécdota, jajaj. Todo es idea del creador original, está claro que hablamos de Michael Widenius (Monty) y de sus hijos. MySQL: la primera hija de Monty se llama "My", un curioso nombre tailandés. MaxDB: MaxDB es otro sistema de gestión creado por el mismo autor, el nombre se debe a su hijo "Max". MariaDB: así se llama la hija de Monty (de su segundo matrimonio), "Maria".   Canales de Telegram: Canal SoloLinux – Canal SoloWordpress Espero que este articulo te sea de utilidad, puedes ayudarnos a mantener el servidor con una donación (paypal), o también colaborar con el simple gesto de compartir nuestros artículos en tu sitio web, blog, foro o redes sociales.   Read the full article

[hackgit]

​jSQL Injection Lightweight application used to find database information from a distant...

​jSQL Injection Lightweight application used to find database information from a distant server. It's free, open source and cross-platform for Windows, Linux and Mac and it works with Java from version 11 to 17. Kali Linux logo jSQL Injection is also part of the official penetration testing distribution Kali Linux and is included in various other distributions like Pentest Box, Parrot Security OS, ArchStrike and BlackArch Linux. ▫️ Automatic injection of 33 database engines: Access, Altibase, C-treeACE, CockroachDB, CUBRID, DB2, Derby, Exasol, Firebird, FrontBase, H2, Hana, HSQLDB, Informix, Ingres, InterSystems-IRIS, MaxDB, Mckoi, MemSQL, MimerSQL, MonetDB, MySQL, Neo4j, Netezza, NuoDB, Oracle, PostgreSQL, Presto, SQLite, SQL Server, Sybase, Teradata and Vertica ▫️ Multiple injection strategies: Normal, Error, Blind and Time ▫️ Various injection processes: Default, Zip, Dios ▫️ Database fingerprint: Basic error, Order By error, Boolean single query ▫️ Script sandboxes for SQL and tampering ▫️ List to inject multiple targets ▫️ Read and write files using injection ▫️ Create and display Web shell and SQL shell ▫️ Bruteforce password hash ▫️ Search for admin pages ▫️ Hash, encode and decode text ▫️ Authenticate using Basic, Digest, NTLM and Kerberos ▫️ Proxy connection on HTTP, SOCKS4 and SOCKS5 https://github.com/ron190/jsql-injection

-

[johncloud]

All You Need to Know About SAP HANA Community Cloud

What is a Community Cloud?

The term ‘community cloud’ specifies that the design of the cloud is exactly as per the norms and standards of a particular community. Community clouds are nothing but the hybrid forms which are particularly built for a niche and specific target group. All of these communities are working on similar standards and hence they have matching requirements. They need to work together to achieve their business goals.

Community clouds are tailor-made for organizations and businesses which work on common projects, researches, or applications and so they need a central cloud computing system. A central community cloud helps in creating, managing and implementing such projects, irrespective of the solutions which they rent from the service providers.

The cloud consumers are the members of the community who share the responsibility of cloud definition and evolution.

The community membership not always guarantees the access or control of all the IT resources. The outside parties can get access only if the community allows them.

What is ESDS’ SAP HANA Community Cloud?

From the above explanation, now you can somewhat understand what can be the meaning of SAP Community Cloud. The community which follows the compliances and regulations of the SAP systems, has the same requirements and totally works on SAP is the SAP community cloud.

ESDS Software Solutions Pvt. Ltd has been the first ever company to provide SAP HANA Community Cloud. ESDS has designed and set this community cloud especially for the SAP members who work on the commonly standards set by SAP. This SAP HANA community cloud is made such that any client can set up his/her HANA instances with desired redundancy and flexibility.

We abide by all the SAP compliances to provide a user everything he needs at one place. Users can choose from several options of deployment for Commercial Data Centers and on-premise cloud infrastructure. We also provide Tailored Data Center Integration (TDI) to our customers so that they can leverage their current infrastructure and hardware components for HANA environment. Our SAP community cloud provides different server types. Our cloud solutions let users experience speedy and elastic operation services, as we focus on SAP HANA instances on the cloud. We provide our users a Single-Sign-On (SSO) login for every service, with the help of eNlight 360. Because of this SSO feature, the user can access every service at one place and take benefits of all our solutions like gDNS, MTvScan 2.0, WAF, and so on.

We have a robust team of technicians which configures and handles SUSE/HANA failover systems with high RPO/RTO rates, in-detail reports, and continuous drills. The in-house support team comprises of certified specialists who have a large experience base of serving huge organizations, over 120 SAP HANA customers and more than 10,000 SAP users.

Generally, the users have to call several technical/customer support members for their issues and they get irritated. Hence, for user convenience, we provide a Single Point of Support with their respective account manager. This system ensures there is no time wasted and the customer gets solutions in time. All the managed services viz., Infrastructure, BASIS support, and DR, achieve a better turn-around time.

Due to all these services we provide, ESDS is the proud partner of choice on SAP’s APJ portal, for SAP S/4 HANA infrastructure hosting services.

What features does ESDS offer?

There are several features like cloud and SAP Managed Services that we offer. Consider the following-

1. Onboarding Services

One Time SAP Infrastructure     setup as per final sizing

2. SPLA License

VMware

SLES/RHEL/Win

Veritas NetBackup/Commvault

3. SAP Managed Services

SAP Basis Support

HANA Administration Service

Sybase/MaxDB etc.

SAP HANA/SUSE Failover-Cluster     Service (Configuration, Daily Monitoring & Management)

4. Infra Managed Services

24x7 Advanced Monitoring     Service

OS, Storage, backup, Network     & Security

5. DR Setup

 One Time DR infra setup

 DR Drills &     Reporting

 RTO/RPO monitoring

 Replication Monitoring     & Configuration

6. Compute/Storage

 Certified SAP Cloud

 SAP HANA on TDI     (Physical/Cloud) & Certified Appliance Model

 Performance Disk space     (SAS) – 300 IOPS/TB

 High-Performance Disk     space (SSD) – 3000 IOPS/TB

 Backup solution –     Data/Snapshot

7. Network and Security

 Physical/Virtual     Firewalls

 SIEM, DDoS Service

 IPSec/SSL VPN,     Internet/MPLS Link/Shared P2P Links

Which are the SAP HANA Managed Services that ESDS provides and for whom these services are?

There are three services- SAP Basis Services, SAP DR Services, and SAP Infrastructure Management Services. Let’s get to know about each one of them-

SAP Basis Services-

Our SAP experts are always there to assist you with everything related to BASIS administration. We provide all the technical support, be it the pre-installation planning, monitoring tools, sizing of the resources, and much more so that you have to pay less cost.

We cater the BASIS support immediately after the SAP implementation is over and therefore you don’t have to worry about it.

SAP DR Services-

Did you know that your instances can recover with 100% availability and high scalability and that too with a very low cost? Yes, now you can with ESDS.

We know the cost of hiccups in your website or the cost of a few seconds of black-out. In case there are some disasters, your IT resources and assets need protection because such disasters can cause big losses. Hence, there is a need for data copies in several places so that you don’t lose your valuable data.

With ESDS, you don’t have to worry! You can get comprehensive security and disaster recovery plans, policies, tools, and technologies with an exuberant support from us.

SAP Infrastructure Management Services-

We know the importance of managing and monitoring the IT infrastructure in a timely manner. It increases the availability of operational and applications services. There are several tools to monitor IT resources which are highly time-consuming, expensive, and need extra resources because there is a demand for skilled personnel who can handle these tools. For these problems, ESDS again provides a solution in terms of eMagic, a tool to manage and monitor infrastructure from A to Z. If you want a robust, cost-saving and highly-efficient solution for your SAP environments, then this is the one. eMagic helps you to fix root causes of infrastructure damage by immediate resolving action on the issue.

Why should you deploy your SAP HANA instances on SAP HANA Community Cloud by ESDS?

Looking at all the above factors – features, cloud, and SAP managed services which ESDS provides, it is quite clear why ESDS can be the best choice.

ESDS strives to provide exuberant support and a great level of service satisfaction to its customers. Our products are specifically tailored to serve your needs and wishes.

[desconofficial]

Job Title: SAP Basis Engineer Job Responsibilities • Conducts moderately complex analysis including planning, designing, and evaluating a variety of information technology tools. • Serves as the back up to respond to user requests for system needs and upgrades or handles request that are more complex. • Troubleshoots and resolves complex problems in an efficient manner with little to no supervision. • Implements standards for computer operations for compatibility between hardware and software, according to specifications and parameters. • Administers, runs tests on, and maintains operating system and related software. • Schedules, performs, and monitors system backups and, when necessary, performs data recoveries. • Performs root cause analysis, diagnostics, and monitoring on various production systems. • Actively engaged in the planning and designing of new platforms and integrating new technologies into existing infrastructure. Evaluates new technologies and releases. • Creates and reviews technical systems recovery plans to reduce time if a system outage were to occur. Minimum Qualifications • Bachelor's Degree in Information Technology, Computer Science or a related field or equivalent relevant experience. • Requires at least 2-3 years of experience in the field or in a related area. Familiar with a variety of the field's concepts, practices, and procedures. Relies on extensive experience and judgment to plan and accomplish goals. Other Job Specific Skills (any 5) • Skills/Experience: Experience implementing and supporting SAP ECC with a specialism in one or more components such as ECC, BI, Business Objects, PO, Portal, Content Server, Trex , HANA • Experience as an SAP BASIS system administrator in software testing, installation, configuration, and system problem resolution of computer operating systems. Experience in deploying new SAP solutions to include system start up, configuration, and upgrades • Knowledge of Linux (Red Hat Linux, Oracle Enterprise, SUSE, Windows), database administration (Oracle, SQL Server, MaxDb, Sybase, Hana), network and SAN, Change Management • SAP Certification is a plus, prior experience in SAP Performance Tuning • Hands-on experience in backup tool NetBackup etc. is an added advantage.. • Experience in configuration of CTS+ for non-ABAP Transports and SSO and SSL configurations. Deadline: 26th September 2021 Email: Recruitment@descon.com

[dsi-guia3]

6. ¿Cuáles son los motores de bases de datos relacionales Open Source?

Respuesta: Los motores de bases de datos relacionales Open Source son:

MySQL PostgreSQL MaxDB Firebird MonetDB LuciDB MariaDB CockroachDB ClickHouse Neo4j

[dichvumobilevn]

Cách hủy gói MAXDB của nhà mạng Vinaphone

Khách hàng đăng ký gói MAXDB Vinaphone nhưng không còn nhu cầu sử dụng nữa thì hãy hủy gói cước tránh bị nhà mạng trừ tiền oan. Vậy cách hủy gói cước như thế nào? Nếu có quan tâm hãy cùng đi theo dõi bài viết dưới đây nhé.

Hướng dẫn hủy gói 3G MAXDB Vinaphone chỉ bằng 1 tin nhắn

Một lưu ý cần cân nhắc cho mọi khách hàng khi muốn thực hiện hủy một gói cước 3G Vinaphone bất kỳ đó chính là tra thông tin chi tiết của gói cước đó. Việc làm này sẽ giúp quý khách nắm chi tiết tên gói cước, thời hạn sử dụng cũng như số lưu lượng data tốc độ cao còn lại, từ đó đưa ra quyết định hay tiếp tục sử dụng cho hết tài nguyên để tránh lãng phí.

Cú pháp tra cứu: Soạn DATA gửi 888

Sau khi đã kiểm tra thông tin, nếu khách hàng vẫn giữ quyết định thực hiện hủy gói cước MAXDB Vinaphone, thì chỉ cần thao tác duy nhất một cú pháp tin nhắn sau đây:

HUY MAXDB gửi 888

Ngay sau đó, tổng đài Vinaphone sẽ gửi tin nhắn thông báo thuê bao đã hủy thành công gói cước MAXDB, đồng thời toàn bộ ưu đãi từ gói cước này sẽ bị mất hoàn toàn và không thể khôi phục lại..

Chúc quý khách hàng hủy thành công gói MAXDB Vinaphone.

Xem thêm về huy 4G Vinaphone đơn giản nhất. 

[globalmediacampaign]

Tips for Upgrading to from MySQL 5.7 to MySQL 8

MySQL 8.0 has been with us already for quite some time and many MySQL users have already upgraded to this version. For those who are still using older MySQL versions, we would like to present this blog where we will share some tips and information that help in the upgrade process for MySQL 8.0. Mind Your Version Software versions are quite important in the upgrade process. For starters, only one major version difference is supported. You have to be running MySQL 5.7 before you can upgrade to MySQL 8.0. This is quite important to keep in mind given that MySQL 5.6 is approaching its End-of-Life and it won’t be supported anymore. For all of you who use MySQL 5.6 you have to make sure you upgrade it to MySQL 5.7 first and then, eventually, to MySQL 8.0. What’s strongly recommended is that you upgrade to the latest version available for MySQL 5.7. At the time of writing this blog it was 5.7.31 but this will eventually change, you can always look it up at MySQL website. Please also note that upgrades from non-GA (and to non-GA) versions are not supported. Not that it makes any sense to run non-GA versions in production but we wanted to make this one clear as well. It’s a One Way Ticket Whenever you decide to perform the upgrade, please be aware that, once the upgrade is complete, there is no coming back. The changes are not compatible and you just simply cannot use the data directory from MySQL 8.0 on MySQL 5.7. Make sure that you take a backup of your MySQL 5.7 data directly before the upgrade - you would be able to restore it on MySQL 5.7 instance should you need to revert the change. Please also keep in mind, as it may come as a surprise, that upgrade from MySQL 8.0.x to MySQL 8.0.x+1 may also be not compatible and, even though it is a minor version upgrade, you should not expect that downgrade would be possible. This is the result of Oracle’s deployment cycle - instead of doing feature-freeze for the latest GA branch, as it was the case with previous versions, new features, sometimes incompatible ones, are pushed as new releases of 8.0 branch. In-Place Upgrade is a Go In the past it was not always possible to perform an in-place upgrade of MySQL. In some cases you were forced to dump the data into SQL format and then load it back up to the new version. Luckily, MySQL 8.0 is more admin-friendly and in-place upgrade is supported. All you need to do is to run apt upgrade or yum update and you are all set. The upgrade is even more convenient - in the past one had to keep in mind to run mysql_upgrade to ensure all system tables are properly upgraded to the format required by the new version of MySQL. In MySQL 8.0, starting from MySQL 8.0.16, this is no longer needed - all you have to do is to start MySQL process, mysqld, and, by default, the upgrade will be performed over the data dictionary and other system schemas whenever it’s determined to be required. It is possible to change this behavior by passing different parameters to --upgrade server option but in the majority of the cases you would like to benefit from this improvement. Am I Safe to Upgrade? Of course, there are prerequisites for the safe upgrade. Let’s take a look at some methods that should help you to ensure you can safely upgrade to MySQL 8.0. Sanity Checks Before you attempt anything, you should double-check that your existing MySQL 5.7 setup ticks all the boxes on the sanity checklist before upgrading to MySQL 8.0. MySQL documentation presents an extensive list of things to test. It doesn’t make sense to go over the list here as it’s covered in the MySQL documentation, but here are a couple of points you may want to keep in mind. First, partitioning is now supported only in engines that implement it on their end, which are NDB and InnoDB only. Please make sure that all the partitioned tables use one of those storage engines or that you remove the partitioning before the upgrade. You May Want to Run mysqlcheck -u root -p --all-databases --check-upgrade to double-check that tables are in the proper format. There are also other checks that you should perform - almost every new MySQL version comes with an updated list of reserved words and you should check that you don’t use them in your database. You need to check foreign key constraint names, they cannot be longer than 64 characters. Some options for sql_mode have been removed thus you should make sure you do not use them. As we mentioned, there’s an extensive list of things to test. MySQL Shell to the Rescue Testing all of those conditions is quite time-consuming therefore Oracle created an option in the MySQL Shell that is intended to run a series of tests to verify if your existing installation is safe to upgrade to MySQL 8.0. For starters, if you do not have MySQL Shell installed, you should do that. You can find downloads on Oracle’s website. Once you set it up, you can connect to your MySQL 5.7 and run the test. Let’s see how it can look like: root@vagrant:~# mysqlsh MySQL Shell 8.0.21 Copyright (c) 2016, 2020, Oracle and/or its affiliates. All rights reserved. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. Type 'help' or '?' for help; 'quit' to exit. MySQL JS > c root@localhost Creating a session to 'root@localhost' Please provide the password for 'root@localhost': **** Save password for 'root@localhost'? [Y]es/[N]o/Ne[v]er (default No): Fetching schema names for autocompletion... Press ^C to stop. Your MySQL connection id is 71 (X protocol) Server version: 5.7.31-log MySQL Community Server (GPL) No default schema selected; type use to set one. We connected to the MySQL instance on the localhost using MySQL Shell. Now we can run the check. We’ll pass the path to the configuration file for more extensive tests: MySQL localhost:33060+ ssl JS > util.checkForServerUpgrade({"configPath":"/etc/mysql/my.cnf"}) Then we have a long output. The MySQL server at localhost:33060, version 5.7.31-log - MySQL Community Server (GPL), will now be checked for compatibility issues for upgrade to MySQL 8.0.21... 1) Usage of old temporal type No issues found 2) Usage of db objects with names conflicting with new reserved keywords No issues found 3) Usage of utf8mb3 charset No issues found 4) Table names in the mysql schema conflicting with new tables in 8.0 No issues found 5) Partitioned tables using engines with non native partitioning No issues found 6) Foreign key constraint names longer than 64 characters No issues found 7) Usage of obsolete MAXDB sql_mode flag No issues found 8) Usage of obsolete sql_mode flags No issues found 9) ENUM/SET column definitions containing elements longer than 255 characters No issues found 10) Usage of partitioned tables in shared tablespaces No issues found 11) Circular directory references in tablespace data file paths No issues found 12) Usage of removed functions No issues found 13) Usage of removed GROUP BY ASC/DESC syntax No issues found 14) Removed system variables for error logging to the system log configuration No issues found 15) Removed system variables Error: Following system variables that were detected as being used will be removed. Please update your system to not rely on them before the upgrade. More information: https://dev.mysql.com/doc/refman/8.0/en/added-deprecated-removed.html#optvars-removed log_warnings - is set and will be removed, consider using log_error_verbosity instead query_cache_size - is set and will be removed query_cache_type - is set and will be removed 16) System variables with new default values Warning: Following system variables that are not defined in your configuration file will have new default values. Please review if you rely on their current values and if so define them before performing upgrade. More information: https://mysqlserverteam.com/new-defaults-in-mysql-8-0/ back_log - default value will change character_set_server - default value will change from latin1 to utf8mb4 collation_server - default value will change from latin1_swedish_ci to utf8mb4_0900_ai_ci event_scheduler - default value will change from OFF to ON explicit_defaults_for_timestamp - default value will change from OFF to ON innodb_flush_neighbors - default value will change from 1 (enable) to 0 (disable) innodb_max_dirty_pages_pct - default value will change from 75 (%) 90 (%) innodb_max_dirty_pages_pct_lwm - default value will change from_0 (%) to 10 (%) innodb_undo_log_truncate - default value will change from OFF to ON innodb_undo_tablespaces - default value will change from 0 to 2 log_error_verbosity - default value will change from 3 (Notes) to 2 (Warning) max_error_count - default value will change from 64 to 1024 optimizer_trace_max_mem_size - default value will change from 16KB to 1MB performance_schema_consumer_events_transactions_current - default value will change from OFF to ON performance_schema_consumer_events_transactions_history - default value will change from OFF to ON slave_rows_search_algorithms - default value will change from 'INDEX_SCAN, TABLE_SCAN' to 'INDEX_SCAN, HASH_SCAN' transaction_write_set_extraction - default value will change from OFF to XXHASH64 17) Zero Date, Datetime, and Timestamp values No issues found 18) Schema inconsistencies resulting from file removal or corruption No issues found 19) Tables recognized by InnoDB that belong to a different engine No issues found 20) Issues reported by 'check table x for upgrade' command No issues found 21) New default authentication plugin considerations Warning: The new default authentication plugin 'caching_sha2_password' offers more secure password hashing than previously used 'mysql_native_password' (and consequent improved client connection authentication). However, it also has compatibility implications that may affect existing MySQL installations. If your MySQL installation must serve pre-8.0 clients and you encounter compatibility issues after upgrading, the simplest way to address those issues is to reconfigure the server to revert to the previous default authentication plugin (mysql_native_password). For example, use these lines in the server option file: [mysqld] default_authentication_plugin=mysql_native_password However, the setting should be viewed as temporary, not as a long term or permanent solution, because it causes new accounts created with the setting in effect to forego the improved authentication security. If you are using replication please take time to understand how the authentication plugin changes may impact you. More information: https://dev.mysql.com/doc/refman/8.0/en/upgrading-from-previous-series.html#upgrade-caching-sha2-password-compatibility-issues https://dev.mysql.com/doc/refman/8.0/en/upgrading-from-previous-series.html#upgrade-caching-sha2-password-replication Errors: 3 Warnings: 18 Notices: 0 3 errors were found. Please correct these issues before upgrading to avoid compatibility issues. As you can see, 21 tests in total have been performed, the check has found 3 errors related to the configuration options that will not exist in MySQL 8.0.21. The tests are quite detailed. Among other things you will learn about changes in the default values for variables that you do not have configured in your MySQL configuration (so, those settings will change once you install MySQL 8.0). Rolling Back a Failed Upgrade As we mentioned before, you cannot downgrade from MySQL 8.0 once upgrade is complete. Luckily, it doesn’t mean you cannot rollback the upgrade if it fails in the middle. Actually, it happens semi-automatically should one of the issues we discussed in the previous section is detected. The only manual action that is required would be to remove redo logs and start MySQL 5.7 to address the problems detected during the upgrade. Then you should perform a slow shutdown (innodb_fast_shutdown=0) to ensure everything is written to the tablespaces and then you are all good to attempt the upgrade once more. Final Tips There are two, quite important changes in the default behavior that comes with MySQL 8.0 we would like to highlight. Caching_sha2_password as the default Please make sure that you double-check if your applications and proxies will work properly with caching_sha2_password authentication plugin as it becomes the default one in MySQL 8.0. Older applications might be impacted and not able to connect to the database. Of course, you can change this to whatever authentication plugin you want (like mysql_native_password for example, as it was the default in previous MySQL versions) so it is not a blocker by any means. It’s just something to remember to test before the upgrade so you won’t end up with MySQL 8.0 and apps that cannot connect to it unless you reconfigure your database to use an older authentication mechanism. UTF8mb4 as the default charset This shouldn’t come as a surprise given how widely changed to UTF8 was discussed in the community, but that’s the fact - MySQL 8.0 comes with UTF8mb4 charset as the default one. This has some additional impact that you should be aware of. First, your dataset’s size might increase if you will use UTF8mb4 charset. This leads to memory buffers being able to store smaller amounts of data than for data with latin1 charset. Second, the performance of MySQL is expected to be reduced. Sure, Oracle did a great job of minimizing the impact of this change, but you cannot expect that there will be no performance impact whatsoever - it will be some. We hope this blog post will help you to go through the process of upgrading from MySQL 5.7 to MySQL 8.0. If you have your thoughts on the process, we encourage you to share them in the comments below this post. Tags:  MySQL database upgrade upgrades https://severalnines.com/database-blog/tips-for-upgrading-mysql-5-7-to-mysql-8

[siberguvenlikwebtr]

Profesyonellerin Kullandığı 10 Penetrasyon Testi Aracı

Sızma Testi Nedir?

Sızma Testi (Penetrasyon testi), profesyonel beyaz şapkalı bilgisayar korsanlarının, kötü niyetli siyah şapkalı korsanlar saldırı yapmadan önce zayıf yönleri bulmak için kurumsal ağlara girdiği bir siber saldırıdır. Örneğin; Saldırganlardan önce zayıf yönleri bulmak için beyaz şapkalı etik hackerların şirket ağlarına girdiği Sneakers filminde olduğu gibi. Pentester veya etik korsanların kötü niyetli korsanların kullanabileceği araç ve teknikleri kullandığı simüle edilmiş bir siber saldırı da denebilir.

Eskiden hack yapmak zordu ve çok fazla kod yazma gerektiriyordu. Bugün ise, tam otomatik test araçları paketi, bilgisayar korsanlarını her zamankinden çok daha fazla saldırabilen ve yetenekli  bilgisayar destekli insanlara yani cyborglara dönüştürüyor. Neden bir jet uçağında uçağına binme olanağınız varken bir yere ulaşmak için bir at veya at arabası kullanıyorsunuz? İşte modern bir pentester'ın işini daha hızlı, daha iyi ve daha akıllı yapan süpersonik araçların bir listesi.

1. Kali Linux

Eğer Kali işletim sistemini pentesting üssü olarak  kullanmıyorsanız, ya başka bir dağıtıma (Parrot OS gibi) özel bir ilginiz var ya da büyük bir yanlış yapıyorsunuz. Daha önce BackTrack Linux olarak bilinen ve Offensive Security'dekiler (OSCP sertifikasını yayınlayan Offsec)  tarafından hazırlanan Kali, penetrasyon test cihazı olarak kullanım için iyi bir  şekilde optimize edilmiştir. Kali'yi kendi donanımınızda çalıştırabilirken, OS X veya Windows'ta Kali sanal makinelerini kullanan pentesterleri görmek çok daha yaygındır. Kali, burada sözü geçen araçların çoğuyla birlikte gelir ve çoğu kullanım durumları için varsayılan  işletim sistemidir. Ancak, uyarmalıdır ki  Kali, savunma için değil, hücum için optimize edilmiştir ve kolayca hack amaçlı kullanılabilir. Süper ekstra gizli dosyalarınızı Kali VM'nizde saklamayın.

2. nmap

Port tarayıcılarının atası, nmap , en iyi ve en çok kullanılan bir pentest aracıdır. Hedef sistemde hangi portlar açık? Bu portlarda ne var? Bu, keşif aşaması sırasında pentester için vazgeçilmez bir bilgidir ve nmap genellikle bu iş için en iyi araçtır. Nmapla tarama yaparken çok dikkatli olmalısınız. Size izin verilmemiş bir sistemde tarama işlemi yapmak, mahallede evlerin hepsinin kapısını tek tek çalmaya benzer ki hoş bir davranış değildir. Bazı durumlarda da izinsiz port taraması işlemi hukuki sorunlar oluşturabilmektedir. Nmap İle Ağ Keşfi-En Çok Kullanılan Etik Hacking Aracı eğitiminde anlattığımız gibi scanme.nmap.org sitesine tarama yapabilirsiniz.  

3. Metasploit

Metasploit zafiyetleri istismar edip sistemlere sızmak için kullanılan en önde gelen araçlardan biridir. Uygun şekilde ayarlanan Metasploit bir  yay gibidir: Hedefinize nişan alın, istismarınızı seçin, bir yük seçin (payload) ve ateş edin. Çoğu penster için vazgeçilmez olan metasploit, daha önceki zor ve sıkıcı aşamaların çoğunu otomatik hale getiriyor.

Rapid7 tarafından ticari desteğe sahip, açık kaynaklı bir proje olan Metasploit , mavi takımların sistemlerini saldırganlardan korumak için sahip olması gereken bir araçtır.

4. Wireshark

Wireshark bir  ağ protokolü analizörüdür. Wireshark, ağınızdan geçen trafiği yakalayıp incelemek için kullanılan bir araçtır. Gündelik TCP / IP bağlantı sorunlarını gidermek için yaygın olarak kullanılırken, Wireshark, gerçek zamanlı analiz ve bu protokollerin çoğu için şifre çözme desteği de dahil olmak üzere yüzlerce protokolün analizini destekler. Pentesting konusunda yeniyseniz, Wireshark mutlaka öğrenilmesi gereken bir yazılımdır.

5. John the Ripper

Bu yazılım (John) adaşından farklı olarak,  Victoria’da Londra’daki insanları seri olarak öldürmez, ancak GPU’nuzun gidebildiği kadar hızlı bir şekilde şifrelemeyi kırar. Bu şifre kırıcı açık kaynaklı ve çevrimdışı şifre kırma amaçlıdır. John muhtemel şifrelerden oluşan bir kelime listesi kullanabilir ve “a” ile “@” ve “s” ile “5” ve benzeri şeyleri değiştirmek için onları mutasyona uğratır veya bir parola bulunana kadar güçlü donanımla sonsuza kadar çalışabilir. İnsanların büyük çoğunluğunun, karmaşıklığın çok az olduğu kısa şifreler kullandığını göz önünde bulunduran John, çoğu zaman şifre kırmada başarılı olur.

6. Hydra

John'un arkadaşı Hydra , SSH veya FTP girişi, IMAP, IRC, RDP ve daha fazlası  çevrimiçi bir şifreyi kırmanız gerektiğinde devreye girer. Hydra'yı açmak istediğiniz servise yönlendirin, isterseniz bir kelime listesi iletin ve tetiği çekin. Hydra gibi araçlar, hız sınırlayıcı parola girişimlerinin birkaç giriş denemesinden sonra kullanıcıların neden bağlantıyı kesmeye çalıştığını ve kullanıcıların bağlantılarını kesmelerinin neden saldırganlara karşı savunmada hafifletici olabileceğini hatırlatır.

7. Burp Suite

Şimdiye kadar bahsedilen diğer araçların aksine, ne ücretsiz ne de free ayrıca pahalı bir araç olan web güvenlik açığı tarayıcısı Burp Suite'ten bahsetmeden olmaz Burp Suite topluluk sürümü Kali'de varken, işlevselliğin çoğundan yoksundur ve Burp Suite kurumsal sürümü yılda ortalama 3.999 dolar'a mal olur. Yine de, bu tür dudak uçuklatan fiyatları kabul etmenin bir nedeni var. Burp Suite, inanılmaz derecede etkili bir web güvenlik açığı tarayıcısıdır. Test etmek istediğiniz web sitesine gelin ve hazır olunca ateş edin. Bumm... Bug bounty avcıları genelde bu aracı kullanır ve aldıkları ödüllerle Burp Suite ödedikleri parayı fazlasıyla çıkarırlar.

8. Zed Attack Proxy

Burp Suite'in bir kopyası için para ödemek istemeyenler, OWASP'ın Zed Attack Proxy'sini ( ZAP ) neredeyse aynı derecede etkili bulacaklar ve hem de özgür yazılıma sahip olacaklar. Adından da anlaşılacağı gibi ZAP, tarayıcınız ve test ettiğiniz web sitesi arasında durur ve teftiş ve değişiklik yapmak için trafiği engellemenize (yani ortadaki adam saldırısı) izin verir. Burp'un birçok eklentisinden yoksun, ancak açık kaynaklı lisansı, ölçeklendirmeyi kolay ve ucuz hale getiriyor ve web trafiğinin gerçekte ne kadar hassas olduğunu öğrenmek için iyi bir başlangıç ​​aracıdır ZAP.

9. sqlmap

Biri SQL enjeksiyon mu  var dedi? İşte, sqlmap . İnanılmaz derecede etkili olan bu SQL enjeksiyon aracı açık kaynak kodlu ve web sitesinde dediği gibi "SQL enjeksiyon hatalarını tespit etme ve kullanma ve veritabanı sunucularını ele geçirme işlemini otomatik hale getiriyor" . Sqlmap, MySQL, Oracle, PostgreSQL, Microsoft SQL Server, Microsoft Access, IBM DB2, SQLite, Firebird, Sybase, SAP MaxDB, Informix, HSQLDB ve H2 dahil olmak üzere tüm olağan hedefleri destekler.

10. aircrack-ng

İş yerinizdeki veya evinizdeki  wifi ne kadar güvenli? Aircrack-ng ile öğrenin . Bu wifi güvenlik denetim aracı ücretsiz / serbest, ancak USB kablosuz antenli ağ kartı eklemek zorunda kalabilirsiniz ki bu daha iyi çekim gücü demektir. Bugün wifi kırma, genellikle kötü yapılandırma, basit şifreler veya eski şifreleme protokolleri nedeniyle mümkündür. Bu Araçları Nasıl Öğreneceğim? Burada bahsedilen araçların nasıl kullanıldığını öğrenmek için Kali İle Ofansif Güvenlik Kitabını alabilir veya Udemy Kali ile Penetrasyon Testleri Eğitimine kayıt olabilirsiniz   Read the full article

[dichvuvinaphonevn-blog]

Cách đăng ký gói MAXDB Vinaphone

Với cước phí vỏn vẹn chỉ là 25.000 đồng/lần đăng ký, khách hàng đăng ký gói cước MAXDB Vinaphone thành công sẽ nhận ngay được ưu đãi cực hấp dẫn về data lên đến 2GB thả ga sử dụng trong vòng 1 tháng liên tục mà không lo lắng về cước phí phát sinh. Đây là gói cước đặc biệt mà Vinaphone triển khai dành tặng cho khách hàng đang sử dụng thuê bao may mắn nằm trong danh sách khuyến mãi.

Vậy nếu có quan tâm về gói cước MAXDB Vinaphone này thì cùng đi theo dõi bài viết dưới đây nhé.

Gói cước 3G khuyến mãi MAXDB Vinaphone có gì?

– Đối tượng tham gia: Thuê bao Vinaphone trả trước đang hoạt động 02 chiều, đồng thời nhận được tin nhắn khuyến mãi mời tham gia gói cước MAXDB từ tổng đài.

– Cách tra cứu thông tin hưởng gói: Để chủ động kiểm tra thuê bao có nằm trong danh sách được tham gia sử dụng gói cước MAXDB hay không, thuê bao thực hiện cú pháp: *091#OK.

– Phạm vi áp dụng: Trên toàn quốc.

– Cước phí đăng ký: Chỉ 25.000đ/tháng trừ vào tài khoản chính.

– Chu kỳ gói cước: 30 ngày kể từ lúc đăng ký 3G Vina thành công và gói cước tự gia hạn mỗi khi bước sang chu kỳ mới.

Hướng dẫn đăng ký gói MAXDB Vinaphone

Cú pháp đăng ký: Soạn DK MAXDB gửi 888. Sau khi đăng ký thành công gói cước. thuê bao sẽ nhận về cho mình 2GB data dùng để truy cập 3G tốc độ cao. Đặc biệt, khi sử dụng hết dung lượng gói, khách hàng tiếp được truy cập internet miễn hoàn toàn cước phát sinh.

Lưu ý thuê bao: Khách hàng được hưởng ưu đãi từ gói cước MAXDB Vinaphone trong vong 5 tháng liên tiếp , khi hết thời gian này, gói cước sẽ tự động gia hạn về gói MAX Vina thông thường với cước phí 70.000đ/tháng – 600MB tốc độ cao, miễn cước phát sinh.

Đừng bỏ lỡ cơ hội tuyệt vời này! Nếu may mắn lọt vào danh sách hưởng gói, hãy thực hiện đăng ký sử dụng gói cước 3G Vinaphone: MAXDB ngay hôm nay để được trải nghiệm một mùa hè sôi động và trọn vẹn nhất.

Xem thêm về đăng ký 3g của vinaphone tại đường link https://4gvinaphone.com.vn/cach-dang-ky-3g-vinaphone.html

Chúc quý khách hàng đăng ký thành công và có một ngày nhiều niềm vui.

[jobswzayef]

Data Warehousing amp Quality Engineer

Data Warehousing amp Quality Engineer

Expert in operational source system data extract< p>

Expert in Data staging area< p>< li>

Data servicing Cleaning standardizing etc… < p>< li>

Data Stores Flat files Relational Tables XML data bases < p>< li>

Data processing Sorting sequencing < p>< li>

Expert in data Marts amp DW BUS conformed dimensions data mart ing techniques< p>< li>

Expert in ETL Extract Transform amp Loading data integration tools< p>< li>

Familiar with ESB Enterprise Service Buss data integration for Online applications< p>< li>

Expert in various data mining methods Clustering analysis prediction decision trees Sequential patterns neural networks < p>< li>

Experienced in multi dimensional analysis OLAP Online Analytical Processing < p>< li>

Experienced in Data Modeling Dimensional Tables < p>< li>

Expert in DBS Database Administration < p>< li>

Expert in Data Quality ISO 8000< p>< li>

Profound experience in Data operations < p>< li>

Data Acquisition< p>< li>

Data Move< p>< li>

Data Cloud storage< p>< li>

Data cleansing< p>< li>

Data Use< p>< li>

Data recovery< p>< li>

Expert in Data Operations < p>< li>

Operational Master data< p>< li>

Operational Meta Data< p>< li>

Reference data< p>< li>

Transactional Data< p>< li>

Expert in Data Quality and Data security standards< p>< li>

Strong understanding for data architecture data modeling.< p>< li>

Expert in DW technologies < em>< p>< li>

Big Data software such as Hadoop Pig Hive< p>< li>

Data warehousing platforms such as TeraData MS Azure MS SQL Server Amazon Redshift Cloudera< p>< li>

Streaming data engines such as AKKA Spark kafka< p>< li>

Programming language such as Python and R< p>< li>

Data Modeling tool such as Erwin< p>< li>

RDBMS Relational Database Management System such as MySQL MS Access oracle RDB SAP MaxDB< p>< li>

Data Management Quality platforms such as < em>< p>< li>

MS MicroSoft SQL Server Data quality Services< p>< li>

Cloudingo.< p>< li>

Data Ladder.< p>< li>

IBM InfoSphere QualityStage.< p>< li>

Informatica Master Data Management.< p>< li>

OpenRefine.< p>< li>

SAS Data Management.< p>< li>

Syncsort Trillium.< p>< li>

Talend Data Quality.< p>< li>

15 in data management< p>< li>

Mid to senior level DW Engineer< p>< li>

7 years of Core experience in DW Big Data< p>< li>

5 years in Data Quality< p>< li>

Should be resident in Saudi Arabia.< p>< li>

Holding a Transferable Iqama is a must.< p>< li> < ul>< li> < ul> * راتب مجزي جداً. * مكافأت و حوافز متنوعة. * توفير سكن مؤثث أو بدل سكن. * أنتقالات أو توفير بدل عنها. * توفير تذاكر السفر لمن يشغل الوظيفة و عائلته. * نسبة من الأرباح الربع سنوية. * أجازات سنوية مدفوعة الراتب بالكامل. * مسار وظيفي واضح للترقيات. * بيئة عمل محفزة و مناسبة لحالة الموظف. * تأمين طبي للموظيف و عائلته. * تأمينات أجتماعية. التقدم و التواصل مباشرة دون و سطاء عند توافر الألتزام و الجدية التامة و المؤهلات المطلوبة علي: jobswzayef@gmail.com

[rajasekharn-blog]

SAP HANA ADMINISTRATION INTRODUCTION

SAP Hana Administration is the synthesis of three separate products

It began in 1996 as a student project at SAP in collaboration with DFKI. TREX became a standard component in SAP NetWeaverin 2000. In-memory attributes were added in 2002 and columnar data store was added in 2003, both as ways to enhance performance.

2. In 2005 SAP acquired Menlo Park based Transact in Memory, Inc. With the acquisition came P*Time, an in-memory light-weight online transaction processing (OLTP) RDBMS technology with a row-based data store.

3. MaxDB (formerly SAP DB), a relational database coming from Nixdorf via Software AG (Adabas D) to SAP, was added to TREX and P*Time to provide persistence and more traditional database features like backup.

In 2008, SAP CTO Vishal Sikka wrote about Hana Administration Administration “…teams working together with the Hasso Plattner Institute and Stanford University demonstrated how a new application architecture is possible, one that enables real-time complex analytics and aggregation, up to date with every transaction, in a way never thought possible in financial applications”. In 2009 a development initiative was launched at SAP to integrate the three technologies above to provide a more comprehensive feature set. The resulting product was named internally and externally as NewDB until the change to Hana Administration Administration DB was finalized in 2011.

SAP Hana Administration Administration is not SAP’s first in-memory product. Business Warehouse Accelerator (BWA, formerly termed BIA) was designed to accelerate queries by storing BW infocubes in memory. This was followed in 2009 by Explorer Accelerated where SAP combined the Explorer BI tool with BWA as a tool for performing ad-hoc analyses. Other SAP products using in-memory technology were CRM Segmentation, By Design (for analytics) and Enterprise Search (for role based search on structured and unstructured data). All of these were based on the TREX engine.

Taking a different approach Advanced Planning and Optimization (APO) used LiveCache for its analytics.

Versions, service packs

SAP co-founder (and Chairman of the SAP Supervisory Board as of 2012) Hasso Plattner advocated a “versionless” system for releases. The support packages to date have been:

SP0 – released 20 November 2010; Hana Administration Administration first public release

SP1 – released 20 June 2011; Hana Administration Administration general availability (GA); focus is as an operation data mart

SP2 – released 27 June 2011; more data mart functions

SP3 a.k.a Hana Administration Administration 1.5 – released 7 November 2011); focus is on Hana

SP4 – projected Q2, 2012; will resolve a variety of stability issues and add new features for BW

Administration as the underlying database under Business Warehouse (BW); also named Project Orange

[dichvumobilevn]

Huong dan cach dang ky goi MaxDB cua mang Vinaphone

Sở hữu ưu đãi cực hấp dẫn về data lên đến 2GB chỉ với 25.000 đồng/lần đăng ký, khách hàng đăng ký gói MAXDB Vinaphone ngay từ khi mới ra đời đã nhận được rất nhiều sự quan tâm từ phía khách hàng. Chi tiết về gói cước này hãy cùng đi theo dõi bài viết dưới đây nhé.

Gói cước 3G khuyến mãi MAXDB Vinaphone có gì?

– Đối tượng tham gia: Thuê bao Vinaphone trả trước đang hoạt động 02 chiều, đồng thời nhận được tin nhắn khuyến mãi mời tham gia gói cước MAXDB từ tổng đài.

– Cách tra cứu thông tin hưởng gói: Để chủ động kiểm tra thuê bao có nằm trong danh sách được tham gia sử dụng gói cước MAXDB hay không, thuê bao thực hiện cú pháp: *091#OK.

– Phạm vi áp dụng: Trên toàn quốc.

– Cước phí đăng ký: Chỉ 25.000đ/tháng trừ vào tài khoản chính.

– Chu kỳ gói cước: 30 ngày kể từ lúc đăng ký 3G Vinaphone thành công và gói cước tự gia hạn mỗi khi bước sang chu kỳ mới.

Hướng dẫn đăng ký gói MAXDB Vinaphone

Cú pháp đăng ký: Soạn DK MAXDB gửi 888.

Sau khi đăng ký thành công gói cước. thuê bao sẽ nhận về cho mình 2GB data dùng để truy cập 3G tốc độ cao. Đặc biệt, khi sử dụng hết dung lượng gói, khách hàng tiếp được truy cập internet miễn hoàn toàn cước phát sinh.

Lưu ý thuê bao: Khách hàng được hưởng ưu đãi từ gói cước MAXDB Vinaphone trong vong 5 tháng liên tiếp , khi hết thời gian này, gói cước sẽ tự động gia hạn về gói MAX Vina thông thường với cước phí 70.000đ/tháng – 600MB tốc độ cao, miễn cước phát sinh.

Đừng bỏ lỡ cơ hội tuyệt vời này! Nếu may mắn lọt vào danh sách hưởng gói, hãy thực hiện đăng ký sử dụng gói cước 3G Vinaphone: MAXDB ngay hôm nay để được trải nghiệm một mùa hè sôi động và trọn vẹn nhất.

Xem thêm về cách đăng ký gói max vinaphone nhận ưu đãi data hấp dẫn

Chúc quý khách hàng đăng ký thành công và có một ngày nhiều niềm vui.