1 / 74

BID212: Rapid Prototyping with Sybase IQ

BID212: Rapid Prototyping with Sybase IQ. Sid Sipes Principal System Consultant Sipes@sybase.com August 15-19, 2004. The Enterprise. Unwired. The Enterprise. Unwired. Industry and Cross Platform Solutions. Manage Information. Unwire Information. Unwire People.

haven
Download Presentation

BID212: Rapid Prototyping with Sybase IQ

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. BID212: Rapid Prototyping with Sybase IQ Sid Sipes Principal System Consultant Sipes@sybase.com August 15-19, 2004

  2. The Enterprise. Unwired.

  3. The Enterprise. Unwired. Industry and Cross Platform Solutions Manage Information Unwire Information Unwire People • Adaptive Server Enterprise • Adaptive Server Anywhere • Sybase IQ • Dynamic Archive • Dynamic ODS • Replication Server • OpenSwitch • Mirror Activator • PowerDesigner • Connectivity Options • EAServer • Industry Warehouse Studio • Unwired Accelerator • Unwired Orchestrator • Unwired Toolkit • Enterprise Portal • Real Time Data Services • SQL Anywhere Studio • M-Business Anywhere • Pylon Family (Mobile Email) • Mobile Sales • XcelleNet Frontline Solutions • PocketBuilder • PowerBuilder Family • AvantGo Sybase Workspace

  4. Target Audience • Information Technology Management • Project Management • Database Personnel • All Levels • System Administrators • All Levels

  5. For This Presentation • Let’s Keep It Interactive • I will entertain questions on a subject • Would be happy to speak to you offline, if desired • No Question is too Basic • Chances are others may have the same question • Open Question Forum at the end • Time Permitting

  6. Agenda In this Session, we will be discussing: • What is Rapid Prototyping? • Why should I consider using Sybase IQ for a Rapid Prototype? • How To Get Started • How to Optimally • Select Hardware and Software for my Prototype • Setup the Hardware for the Prototype • Setup and Configure The Sybase IQ Database • Summary • Question and Answer

  7. Rapid Prototyping with Sybase IQ • In today's hectic business environment, rapid prototyping may be the best solution for quick implementation of a required functionality, or the rapid proving of a new and potentially helpful technology. • Sybase IQ is a technology that can help you rapidly meet your sometimes unrealistic goals, and provide your users with unparalleled performance gains.

  8. Rapid Prototyping with Sybase IQ • This presentation will focus on how Sybase IQ can be used within a rapid prototype or proof-of-concept project. • Topics covered will include project planning, limitations of scope, prevention of scope-creep. In addition, all technical aspects of utilizing Sybase IQ, including: software installation, design methodology, and IQ system performance tuning will be fully covered. • A complete exploration of Sybase IQ tips and tricks for rapid implementation and high performance is included

  9. Rapid Prototyping - Definition What is a Rapid Prototype? • Think of a Rapid Prototype as a rapidly developed first version of a new application. • The Rapid Prototyping Methodology is a short-circuit to the traditional software development methodology.

  10. Rapid Prototyping - Definition What is a Rapid Prototype? • Traditionally, software is developed in distinct phases, with each phase concluding with approval, before the next phase. These phases include: • Requirements Development • Requirements Analysis • System Requirements Specification • Preliminary Design • Detailed Design • Implementation • Test • Quality Assurance • Deployment • Training.

  11. Rapid Prototyping - Definition • As you probably have experienced, this is a long effort, and doesn’t adequately address changing/evolving user requirements. • The Rapid Prototype Methodology effectively rolls all the previously mentioned phases into a single, quick effort. Some characteristics of Rapid Prototyping include: • Limited Requirements • On-The-Fly changes/modifications • Rapid Response to Changing User Requests • Rapid Deployment.

  12. Rapid Prototyping - Definition Different Types of Rapid Prototypes • Straw-Model – Non-Operational • Limited Model – Limited Requirements Implementation • Full Model – Full system Implementation. For the purposes of this discussion, we will be considering only the Limited Model

  13. Why Rapid Prototype? Rapid Prototyping Offers Many Advantages • Quickly Prove Business Value • Demonstrate value more effectively than talk/slide show • Realistic Implementation • Allow users rapid visualization of requirements • Reduce (or confirm) Implementation Risks • Resulting in: • Concept Proved • Value Shown • Money Saved

  14. Why Rapid Prototype? Any Disadvantages? • Usually No Documentation produced • Not all Requirements Implemented • Implementation may be “Sloppy” • Easy to Lose Resources, especially people to “Real” projects • You should be able to avoid or control any of the disadvantages.

  15. Why Rapid Prototype? Now, Let’s take a closer look at each of the advantages of Rapid Prototyping. At the conclusion of this section, we’ll start diving deeper into the technical aspects, including IQ Performance, of implementing in a Rapid Prototype Mode.

  16. Why Rapid Prototype? Prove Business Value • Seeing is believing • Asking forgiveness is easier than asking for large money/budget • Early/Quick Testing of concept

  17. Why Rapid Prototype? Demonstrate value more effectively • Presentations and Slide Shows not always representative of the finished product • Many are Truly boring • Miscommunication often occurs • Presentations are Usually Heavy on the Technical Side • Light on User Requirements

  18. Why Rapid Prototype? Realistic Implementation • This is not a static mockup • What you see – Is What you get • Actual User Requirements are Implemented • Possible Evolutionary Basis for Final System

  19. Why Rapid Prototype? Allow users rapid visualization of requirements • Users are Involved Early and Continuously • Users Feel Valued, and Empowered • Early and Immediate Feedback is Available • Developers can make Immediate changes/corrections

  20. Why Rapid Prototype? Reduce (or confirm) Implementation Risks Seen by management as smaller risk Easier Management signoff on small budget

  21. Why Rapid Prototype? Easier To Get Management Sign On • Rapid Prototypes Seen by management as smaller risk • Smaller Budget usually easier to Get • Requires Smaller Hardware Investment

  22. Why Rapid Prototype? Rapid Confirmation • Rapidly Confirm Concept • Quickly Change Direction when Problems Occur • Early Confirmation/Discovery of Problems • Developmental • User Interface • Database • Performance

  23. Why Rapid Prototype? To Summarize, Rapid Prototyping Offers Many Advantages • Quickly Prove Business Value • Demonstrate value more effectively than talk/slide show • Realistic Implementation • Allow users rapid visualization of requirements • Reduce (or confirm) Implementation Risks • Resulting in: • Concept Proved • Value Shown • Money Saved

  24. Rapid Prototyping – Getting Started In this section, we will discuss how to get a Rapid Prototype Project successfully started.

  25. Getting Started Pick a Project • One that Has Value to your Organization • One that Users are Requesting • Perhaps one that may seem impossible due to size/cost

  26. Getting Started Once you have identified a Project: Develop a Set of Requirements • Based on User needs • Document exactly what the Prototype will perform • Review Requirements with Users, I.e. • Conduct an informal requirements review • Don’t Let Scope Creep – Stick to Original Vision/Plan

  27. Getting Started For Requirements Analysis, Consider Following • Audience / The Users • Involve Users from the Start • Implement what they Want, not what is “Cool” • Do they have any budget/funding to share? • What do they want • Data Warehouse? • Report Server? • OLTP Server?

  28. Getting Started - Guaranteeing Success There are no Guarantees of Success. However, you can maximize your chances of producing a useful system by: • Implementing your prototype in careful, methodical, structured manner. • Developing a plan • Sticking to the plan • Don’t allow scope creep • Don’t allow requirements creep

  29. Getting Started - Guaranteeing Success • Don’t rush implementation • And MOST IMPORTANTLY: • INVOLVE THE USERS AT ALL PHASES

  30. Getting Started - Guaranteeing Success The goal is to produce a system that has considerable value to your “USERS” • If “USERS” don’t like the system, or if it is too difficult and/or cumbersome for them • They won’t use it • The system will fail • The system will be dismantled • Your Career will be dismantled

  31. Getting Started - Guaranteeing Success Let’s take a look at the steps you can take to maximize your chances of success • Get to Know the “Users” • Conduct a Thorough Requirements Analysis • Develop a Data Analysis • Develop an Implementation Plan • Secure sufficient resources • Personnel • Hardware/Software • Time

  32. Getting Started - Guaranteeing Success Develop a Set of System Requirements • Don’t get into requirements “Analysis Paralysis” • Determine what you can do • Lock into those requirements, discard others for future phases • Make sure you brief users on what you can implement You May not be able to satisfy all users, but it is better to successfully build a subset of needs, than to try to build a super-system that fails and delivers nothing.

  33. Getting Started - Guaranteeing Success Realistically Cost/Schedule The Effort • Based on Requirements Analysis • Determine resources required to fulfill requirements • People • Time/Schedule • Hardware/Software • Don’t Estimate Optimistically • Problems will occur • Nothing ever goes according to plan • What can go wrong – Will go wrong!

  34. Getting Started - Guaranteeing Success Conduct a Detailed Data Analysis • Based on User needs and reports • Locate Legacy/Existing data to support reports • Acquire any/all documentation on existing data • Acquire access to all data sources • Determine if extract procedures are required

  35. Getting Started - Guaranteeing Success Conduct a Detailed Data Analysis • Determine Required Transformations • Data Cleanup? • Lookups/Validations? • Combinations? • Will you automate the process? • Extract, Transformation, Load (ETL) Too

  36. Getting Started - Guaranteeing Success Now What? • The Requirements Analysis, and Data Analysis will form the basis and foundation for your detailed system design. • Remember: • A Weak foundation will only support a weak and limited design • A Strong foundation will form the basis for a strong and expandable design.

  37. Getting Started - Guaranteeing Success Finally, Remember that: • It is better to Under Promise, then Over-Deliver • Than Over-Promise, and Disappoint.

  38. Why Sybase IQ? If your project includes a Database Component, Sybase IQ may be the best choice for your database implementation. In this section we will discuss how and why Sybase IQ will help ensure your project success

  39. Why Sybase IQ? • Let’s first make sure that Sybase IQ is appropriate for your implementation. • If you are implementing an OLTP system • SYBASE IQ IS NOT THE APPROPRIATE CHOICE • Otherwise, if your system falls into one of the following categories, then Sybase IQ will be the best choice • Data Warehouse • Data Mart • Query Server • Online Data Archive

  40. Why Sybase IQ? Why Use Sybase IQ? Here’s just a few of the reasons: • Quicker to Implement • Easier to setup • Requires Less Hardware • Easier to Manage • More Tolerant of Mistakes • Faster Loads and Queries Leading to: • A Much Higher Probability of Success

  41. Why Sybase IQ? Easier Hardware setup • Optimal I/O Throughput is easy to setup • More Tolerant of setup errors/inefficiencies • Don’t need lots of 2 Gigabyte Devices • Don’t need lots of I/O controllers • Much Easier for System Administrator to Set up • IQ Performance is Not Dependant on exact disk layout/setup • IQ Can use File System Files or Raw Devices • System Administrator will spend a Fraction of time perparing for an IQ implementation

  42. Why Sybase IQ? A Sybase IQ Implementation Requires Less Hardware • IQ Implementation will utilize much less disk hardware • IQ Achieves 10-50% compression from Raw Data Size • Fully Indexed, IQ will use approximately 70% Less Disk Space than any other RDBMS • Disk might be getting cheaper, but chances are your organization will not have an abundance of disk space for you to use

  43. Why Sybase IQ? A Sybase IQ Implementation Requires Less Hardware • IQ is CPU Bound • IQ Takes advantage of all available CPU Cycles • CPUs are never idle, waiting on I/O • An IQ Implementation will usually require 50% fewer CPUs than any other RDBMS implementation

  44. Why Sybase IQ? A Sybase IQ Implementation Requires Less Hardware • Give the fact that IQ is CPU Bound and IQ Performance is directly related to CPU Speed • Consider using Wintel CPU’s • Consider Using Linux • IQ on 3 GHz Intel CPU outperforms major Unix Flavors • If choosing Wintel/Linux route • Remember 2Gigabyte Memory Limitation • 64 Bit Linux coming soon.

  45. Why Sybase IQ? An IQ based system is Easier to Manage • Requires average of 75% less DBA intervention • No DBCCs to run • No Index Maintenance • No Index Unload/Load Required

  46. Why Sybase IQ? Sybase IQ More tolerant of Mistakes • Performance is Not Schema Dependant • Spend much less time designing and Tuning schema • You can eliminate expensive “Database Architects” • Easy to redesign/re-implement • Speed of Load and Speed of Indexing allow quick changes to be made to schema (even after all data is loaded) • Ability to quickly add and drop columns • Speed of change and load/reload allow you to react to user’s change requests with unprecedented speed.

  47. Why Sybase IQ? IQ is much Faster • IQ will run queries 5x to 1000x faster • With very little tuning • Very little need to dump and analyze query plans • IQ will load data 10x to 100x Faster • High Speed loads directly into indexes • No need to load, then add indexes • This speed means that your system will be available to the users sooner.

  48. Why Sybase IQ? To Summarize, An IQ system is • Easier to Setup • Easier to Manage • Requires Much Less Resources • Quicker Delivery • Faster Response Which adds up to: • LOWER COST • Quicker Delivery • Increased Probability of Success

  49. Physical Implementation with Sybase IQ In this section, we will take a look at the process of selecting the appropriate Hardware and Software for a successful IQ prototype system. We will discuss • Disks • Layout • Controllers • Computer CPU configuration • Computer Memory configuration • Optimal IQ Version for your Prototype • Selection of User Interface/Visualization Tool

  50. Physical Implementation with Sybase IQ Disk • How Much disk Space Will you Need? • Estimate Raw Data Size • Size Main DB to same size as Raw Data • We don’t know how much compression yet, so be safe, estimate pessimistically • Add 15% more for Temp DB • Don’t Forget TEMPDB • Don’t forget to Estimate Space for Staging Raw Data

More Related