Database FAQs - SQL Server

Database FAQs - SQL Server Kony Platform Release 5.0

Copyright 2013 by Kony, Inc. All rights reserved. August, 2013 This document contains information proprietary to Kony, Inc., is bound by the Kony license agreements and may not be used except in the context of understanding the use and methods of Kony software without prior, express, written permission. Kony and Empowering Everywhere are trademarks of Kony, Inc. Microsoft, the Microsoft logo, Internet Explorer, Windows and Windows Vista are registered trademarks of Microsoft Corporation. Apple, the Apple logo, itunes, iphone, ipad, OS X, Objective-C, Safari and Xcode are registered trademarks of Apple, Inc.. Google, the Google logo, Android and the Android logo are registered trademarks of Google, Inc. Chrome is a trademark of Google, Inc. BlackBerry, PlayBook, Research in Motion, and RIM are registered trademarks of BlackBerry. All other terms, trademarks or service marks mentioned in this document have been capitalized and are to be considered the property of their respective owners. Copyright 2013 Kony, Inc. All Rights Reserved. Page 2 of 11

Table of Contents 1. Overview 5 1.1 Intended Audience 5 1.2 Typographical Conventions 5 1.3 Reference Documents 6 1.4 Contact Us 6 2. Kony Database Frequently Asked Questions 7 2.1 General FAQs 7 2.2 FAQs On Replication 8 2.3 FAQs on Reports 9 2.4 FAQs on Performance and Availability 9 Copyright 2013 Kony, Inc. All Rights Reserved. Page 4 of 11

1. Overview KonyOne Platform provides an integrated approach in the mobile application design, development and management. The Platform facilitates the design and development of mobile applications in a device independent manner and delivers them in different formats that run on all the major device platforms. The KonyOne Platform consists of three main components: KonyOne Studio: Used to design and develop the mobile applications. KonyOne Server: Provides server side functionality for the applications, common data integration and device support services. Client Runtime component for each major device platform that enables the same mobile application to execute directly on the device. KonyOne Server The application functionality developed and generated by the Kony Studio is enabled and delivered using the KonyOne Server. The SMS and Mobile Web channels are hosted on the KonyOne Server and the Native App binaries are deployed to the server, to be downloaded by the device. KonyOne Server has the following features: A sophisticated device database that enables it to detect and deliver the appropriate binary to a requesting device. Inbuilt backend data services integration capability, with out-of-the-box support for Web Services, XML feeds and HTML extraction. Integration with optional third party connector libraries that offer access to a large number of ERP, database and legacy systems. Built in usage tracking and analysis capability that provides a wide range of reports on system and application use. Kony Database FAQs This document provides the Frequently Asked Questions (FAQs) on Kony Database. 1.1 Intended Audience This document is intended for engineers or system administrators who are responsible for installing and deploying KonyOne Server and its related databases. We assume that the reader of this document is familiar with deploying software on Java application servers. The reader of this document must understand how to install the SQL Server Database software on the Windows platform. 1.2 Typographical Conventions Following are the typographical conventions used throughout the document: Copyright 2013 Kony, Inc. All Rights Reserved. Page 5 of 11

Convention Explanation User input text, system prompts and responses File Path Monospace Commands Program Code File Names Emphasis Italic Names of Books and Documents New Terminology Windows Menus Bold Buttons Icons Fields URL Note: Important! Tabs Active link to a URL Provides helpful hints or additional information Highlights actions or information that might cause problems to systems or data 1.3 Reference Documents If you need more information about the Kony database setup for SQL Server, please refer to the below documents Kony Database Setup Guide-SQL Server Kony Reports Portal Database Setup-SQL Server Kony Database Data Dictionary-SQL Server Kony Database Logical Design Kony Reporting Data Mapping Diagram Kony Database Purging Plan-SQL Server These documents are available at:http://developer.kony.com/konydatabasedocs. 1.4 Contact Us We welcome your feedback on our documentation. Write to us at techpubs@kony.com. For technical questions, suggestions, comments or to report problems on Kony's product line, contact productsupport@kony.com. Copyright 2013 Kony, Inc. All Rights Reserved. Page 6 of 11

2. Kony Database Frequently Asked Questions In this section, we listed out the Frequently Asked Questions (FAQs) on Kony Database. These FAQs are divided into the following sections: General FAQs FAQs on Replication FAQs on Reporting FAQs on Performance and Availability 2.1 General FAQs 1. Is there a specific version of the DBMS needed? SQL Server 2008 onwards, all the database versions are supported/compatible. 2. Do we need a specific OS version for database installation? Any Windows OS compatible with SQL Server 2008 or above. 3. What driver/protocol is used to connect to the database (ODBC/JDBC)? Supported driver for connecting to the database is JDBC. 4. Do we need any special database related software components? e.g. Partitioning? Not required. At present Our application is not tested with SQL Server partitioning 5. Is there any application tier and/or components that must be co-hosted on same physical server as the database? It is not recommended to host any application tier/middle tier/other components on the same physical server as the database. 6. Does the Database account (Schemas/Application) need elevated privileges? If yes, provide details? In our case we need all the Kony specific databases and schemas should be owned by the DB login which is being used in our Application through JDBC. 7. What are the recommended DBMS settings (configuration variables, private caches, buffer pools, etc)? These things vary on the sizing/number of the application transactions and/or hardware considerations for the database. For more details on this you need to request for Database Planning with Kony Database support team. 8. Are there any special backup and recovery tools utilized? Not required. Clients can go with their original backup plans as per their Business Infrastructure Planning, or as per their DBA s backup plan in their data center. It also depends on the shared/leased/dedicated hosting being selected by the client for the database and their supported backup formats and policies. Copyright 2013 Kony, Inc. All Rights Reserved. Page 7 of 11

9. Are there any database size or user limitations? No. 10. How are the database tables initially populated? There are some static tables whose data needs to be populated through insert scripts, and for dynamic tables, data population happens through data logging. 11. Are audit trails provided? It depends on the hosting being selected for Application tier or DB tier. 12. What is the size of logs generated in the database per service-call? 2 KB per service call i.e. each unique session logs 2 KB of data into the database. This data does not include any session error logging. For each device error/exception 2 KB data is generated. 13. What is Kony's support for scripts for clearing the logger database? Clearing the logger database/flushing the database purely depends on the client's retention policies. Upon request from the client, Kony can only suggest the ways to purge the data as per their requirement. 14. Recommendation on flushing the database over a period of time? This depends on client's retention policies and their storage capacity for the database and its backup. 15. What is the standard format of Kony s database? In SQL Server, our Kony Database will have one database for Device data, another database will have 3 schemas pertaining to Logging data, Reporting data and Reports Portal data. No changes/customization should be done to the above format. 16. What is the basic size of the database? 2 GB of database space is used for initial database setup. From then on, the database increases as per the data volume that is populated into it. 17. How many schemas are there in the database design? In SQL server, In Konydb database - admin, konylogdb, konyreportdb will be schemas. Konydevicedb is also database. Two more database Konyuserdb and konylicensedb are purely based on requirement and are optional. 18. What kind of data is stored in the database? Logging information, device information, client information and reports data per hour/day. 2.2 FAQs On Replication 1. Is replication being used for reporting? Currently replication is not implemented. Copyright 2013 Kony, Inc. All Rights Reserved. Page 8 of 11

2. Is it required to replicate the entire database? Not applicable since replication is not implemented at present. 3. Do you consider the performance while replicating to the same server? Not applicable since replication is not implemented at present. 4. What replication technology is being used by Kony? Presently replication is not implemented. 2.3 FAQs on Reports 1. How many tables are used to generate the reports? 8-10 tables for traffic reports. 2. How often does the data need to be refreshed? Once daily, after the business hours/off peak hours by fetching data from the metrics tables using procedures available in Konyreportsdb schema. 3. How often are reports run? Once in a Day (probably off peak hours) a scheduled job should run and generate the reports data and stores the same in the KONYREPORTSDB tables. 4. How many types of reports can we obtain form the Reports Portal? Once the job is successful, the reports data is available in KonyreportsDB tables. You can get the reports from the reports portal for a day/month/year or reports for any particular date. 2.4 FAQs on Performance and Availability 1. What is the memory requirement for database? Please refer the section System Requirements for Kony Database Setup in the Kony Database Setup Guide. 2. If a largequery locks up the reports database, does this affect the middleware application server performance? If both Kony DB and Reports DB are on the same server, then the Reports need to be run during off peak hours, to avoid adverse impact on the performance. 3. If SQL Server is down, does that lock up or degrade the performance on the application server? If complete SQL Server is down, Kony middleware cannot serve further requests for any new device request, and for device related information present in the database. But, if the device is a repeated visitor, then the device information is returned from the data available in the memory of the middleware. 4. What is the data load rate? The data load rate is in batches of size 50 and 25. Copyright 2013 Kony, Inc. All Rights Reserved. Page 9 of 11

5. What is the percentage of select, inserts, updates, and deletes? It depends on the number of transactions/hits/visits. There are no updates and deletes, only selects and inserts. 6. State any database, application or operating system restrictions on database size No restrictions. 7. Describe any capacity constraints solution, such as the maximum number of users and database size? No capacity constraints are reported as long as sufficient hardware resources (for example: Memory/CPU/Storage) are available on the server. 8. State the system response times, based on the use of a centralized database with remote access? Field to field - Depends on the network bandwidth and the content volume. Update static data item - Depends on the network bandwidth and the content volume. Post journal transaction - Depends on the network bandwidth and the content volume. Run reports - Depends on the network bandwidth and the content volume. 9. What is the adverse effect if a database grows in size, how is the response time affected and what can be done to keep the response time to a minimum? Response time may reduce as the database grows in size. Purging and retention should be defined for log and metrics data to keep the response time minimum. 10. Are there any parameterized automated history transactions, housekeeping jobs - Batch or online mode? Can the jobs be run online and allowed to stop as and when required, with the capability to continue some other time?. Reporting module generate reports. This will be done online, but should run in off peak hours. It has the ability to run at any time, if required. 11. What type of skill set is required to support Kony application? For Databases, a database administrator requires the following skill set: Database monitoring, sound knowledge of database architecture, re-organization, backups and recovery, jobs, batch scripting, performance tuning, database routines, database internals and trouble shooting. 12. How is the report admin data used for this project? Does this data needs to be monitored? Which table should be monitored? "Admin" schema has tables for the data of reports front end navigation. Monitoring is not required for the tables in the "Admin" schema. "KonyreportsDB" schema has PL/SQL objects to generate reports and the tables store the generated reports data. All tables in "KonyreportsDB" schema store the generated reports data for each day, hence space allocation for these tables need to be monitored. Copyright 2013 Kony, Inc. All Rights Reserved. Page 10 of 11

13. What is GET_DEVICE_INFO, VERSION? GET_DEVICE_INFO is a view in KonydeviceDB, for finding the details of manufacture, model etc.version is a view in KonydeviceDB, for finding the device data version. This will be help while applying latest device data updates. 14. Can we add Kony database tables to an existing database? It is recommended to have separate database (dedicated) for Kony database setup. If the database is being used or shared, then we need to have separate schemas and users for Kony database setup where we can create the tables for Kony setup as per the structure supported by Kony application for SQL server. 15. Details for the logging tables. For each table which grows over time Additional per period (Day / Week / Month) - Depends on the traffic over the duration of time, except some device table updates where new device data gets inserted. Bytes per Row - Depends on traffic over the duration of time. Konydevicedb - All tables are static. Konylogdb - Mostly static tables, logger, metrics etc. Kony Reports database - Only for reports portal database. 16. There are multiple schemas in Kony database. Can those schemas be consolidated into one single schema? If yes, then do we need to change the config pointers? What are the implications of making changes/updates to the scripts received from Kony? In SQL server, we recommend not to change or merge the schema. 17. Is it necessary to install KONYREPORTSDB, when there is no need for Kony reports feature? Not necessary. Copyright 2013 Kony, Inc. All Rights Reserved. Page 11 of 11