best practices in migrating to mysql - part 1

36
Best Practices for Migrating to MySQL For existing Oracle/SQL Server environments Ronald Bradford Principal - 42SQL http://42sql.com Washington DC 18th Feb 2009 1. Reasons to Migrate to MySQL 1 Monday, February 16, 2009

Upload: ronald-bradford

Post on 15-Jan-2015

5.029 views

Category:

Technology


3 download

DESCRIPTION

This presentation to the Federal Government sector was a follow up on my successful "MySQL for the Oracle DBA Bootcamp". Best Practices in Migrating to MySQL was a focus on software applications running on Oracle and Microsoft SQL Server database products. Topic in this 4 hr workshop included: 1. Reasons to migrate to MySQL 2. Ideal application candidates 3. Migration process overview 4. Migration assistance tools 5. Specific migration issues 6. Ideals for minimizing future migrations 7. General MySQL Information

TRANSCRIPT

Page 1: Best Practices in Migrating to MySQL - Part 1

Best Practices for Migrating to MySQL

For existing Oracle/SQL Server environments

Ronald BradfordPrincipal - 42SQLhttp://42sql.com

Washington DC 18th Feb 2009

1. Reasons to Migrate to MySQL1Monday, February 16, 2009

Page 2: Best Practices in Migrating to MySQL - Part 1

Workshop Agenda

1. Reasons to migrate to MySQL

2. Ideal application candidates

3. Migration process overview

4. Migration assistance tools

5. Specific migration issues

6. Ideals for minimizing future migrations

7. Additional MySQL information

2Monday, February 16, 2009

Page 3: Best Practices in Migrating to MySQL - Part 1

Session Agenda

• Is migration possible?

• MySQL in the workplace

• MySQL Client examples

• Where do I start with migration

• Reasons to migration

• Roadblocks to migration

3Monday, February 16, 2009

Page 4: Best Practices in Migrating to MySQL - Part 1

Is Migration Possible?

4Monday, February 16, 2009

Page 5: Best Practices in Migrating to MySQL - Part 1

The short answer isYes

5Monday, February 16, 2009

Page 6: Best Practices in Migrating to MySQL - Part 1

Is Migration Possible?

• Short answer is Yes?

• MySQL is enterprise ready

• 14 year old product

• Provides commercial support and indemnity

• Well established to deliver success on web

• Not just a web product

You interact with MySQL supported systems every day

6Monday, February 16, 2009

Page 7: Best Practices in Migrating to MySQL - Part 1

MySQL in the workplace

• Web

• Web 2.0

• Telecom

• On Demand/SaaS

• Hosting

• Enterprise

• OEM/Embedded

• Gaming7Monday, February 16, 2009

Page 8: Best Practices in Migrating to MySQL - Part 1

Usual Suspects

• Facebook

• Wikipedia

• Craigslist

• Yahoo

• YouTube

• Omniture

• Travelocity

• Twitter

• GoDaddy

• Flickr

• Fotolog

• TicketMaster

8Monday, February 16, 2009

Page 9: Best Practices in Migrating to MySQL - Part 1

Marketing Examples

9Monday, February 16, 2009

Page 10: Best Practices in Migrating to MySQL - Part 1

NASAApplication

Informing the general public on contract opportunities, managing large acquisitions on line

Key Business Benefit Saves NASA and its partners $4 million annually

Catalyst to Migration Decision Previous database vendor restructured its license program, causing NASA to be faced with

fees that were “more than twice the total annual budget”

Post Migration Results - License fees were significantly lower - MySQL averaged 28% faster, compared to other databases - Running 3 years without any loss of data or down time

- “The cost of the optional technical support for MySQL was a fraction of that for the product previously used”

http://mysql.com/news-and-events/generate-article.php?type=ss&id=nasa10Monday, February 16, 2009

Page 11: Best Practices in Migrating to MySQL - Part 1

The Weather Channel

• Software & Hardware overhaul

• Reported

• 30% increased capacity

• 50% decreased cost

• Sun Solaris to x86 commodity H/W & Linux

• Websphere to Tomcat

• Oracle to MySQL

http://mysql.com/customers/customer.php?id=2211Monday, February 16, 2009

Page 12: Best Practices in Migrating to MySQL - Part 1

Google

"Google runs critical business systems with InnoDB and MySQL. The systems require 24×7 operation with minimal downtime. The systems support large OLTP and reporting workloads. We are very happy with the scalability, reliability and manageability of this software."

http://www.innodb.com/innodb/users/12Monday, February 16, 2009

Page 13: Best Practices in Migrating to MySQL - Part 1

Embedded Deployment

• Easy not to realize where MySQL is in use

• e.g Support Systems

• Documentation

• Issue Tracking

• Publication

• Ad Tracking

13Monday, February 16, 2009

Page 14: Best Practices in Migrating to MySQL - Part 1

MySQL and Wordpress

• New York Times

• CNN

• Fox News

• Wall Street Journal

• Reuters

• Time Inc

• Financial Times

• Rolling Stone Magazine

http://wordpress.com/notable-users/

• Harvard

• NASA

• Xerox

• Tech Crunch

• Nancy Pelosi

• Stephen Colbert

14Monday, February 16, 2009

Page 15: Best Practices in Migrating to MySQL - Part 1

MySQL in the Enterprise

• Dow Jones

• NASDAQ

• Reuters

• ESPN

• NBC/GE

• New York Times

• Comcast

Embedded

• Cisco

• McAfee

• Adobe

15Monday, February 16, 2009

Page 16: Best Practices in Migrating to MySQL - Part 1

MySQL Marketplace

16Monday, February 16, 2009

Page 17: Best Practices in Migrating to MySQL - Part 1

Where do I start with Migration?

17Monday, February 16, 2009

Page 19: Best Practices in Migrating to MySQL - Part 1

MySQL Migration References

• This workshop

• Migration Overview

• Migration Products

• Migration Partners

• Ideal Candidates

• Roadblocks

19Monday, February 16, 2009

Page 20: Best Practices in Migrating to MySQL - Part 1

Reasons

20Monday, February 16, 2009

Page 21: Best Practices in Migrating to MySQL - Part 1

Reasons to Migrate

• Cost / TCO

• e.g. Subscription v License

• EOL H/W & S/W

• Integration into newer systems

• Asked to

• Forced to

• Physical resources

• Trend21Monday, February 16, 2009

Page 22: Best Practices in Migrating to MySQL - Part 1

Cost / TCO

• Truly difficult to value

• Software

• Hardware

• Support

• Skills

• Staff

Can you state your $ per customer investment22Monday, February 16, 2009

Page 23: Best Practices in Migrating to MySQL - Part 1

Cost / TCO

• Easy when starting a new project now

• Open Source

• Zero entry point - Licenses

• Zero entry point - Subscription (if desired)

• VC preferred

But

23Monday, February 16, 2009

Page 24: Best Practices in Migrating to MySQL - Part 1

Cost / TCO

Less measurable incidentals

• Staff skills / proficiency

• Infrastructure

• e.g. H/W

• Integration points

• Reference material / procedures

24Monday, February 16, 2009

Page 25: Best Practices in Migrating to MySQL - Part 1

EOL

• Newer H/W is significantly cheaper

• More verses Larger

• Growth, Redundancy, Co Location

• Existing licensing may be prohibitive

• Potential environmental impact

25Monday, February 16, 2009

Page 26: Best Practices in Migrating to MySQL - Part 1

Going Green

"We do worry about how to maximize page views for kilowatt hours"

Jim Buckmaster, CEO Craigslist

• Page views per kilowatt hour: The socially responsible benchmark?

http://blogs.zdnet.com/BTL/?p=3434

26Monday, February 16, 2009

Page 27: Best Practices in Migrating to MySQL - Part 1

Integration

• Newer deployed systems for additional purposes

• More efficient to retool old systems to integrate with new

27Monday, February 16, 2009

Page 28: Best Practices in Migrating to MySQL - Part 1

Acquisition

• Your company is acquired by another with different technology infrastructure

• Not likely in Government situation

28Monday, February 16, 2009

Page 29: Best Practices in Migrating to MySQL - Part 1

Forced to

• Management Decision

• e.g. "No new nett Oracle licenses"

• New government initiative ?

29Monday, February 16, 2009

Page 30: Best Practices in Migrating to MySQL - Part 1

Physical Resources

• Newer languages being taught

• Desire to update skills

• New staff acquisition

• Off shoring / Outsourcing options

30Monday, February 16, 2009

Page 31: Best Practices in Migrating to MySQL - Part 1

Open Source - Gardner

• By 2012, 80% of all commercial software will include elements of open-source technology.

• By 2012, at least one-third of business application software spending will be as service subscription instead of as product license.

• By 2011, early technology adopters will forgo capital expenditures and instead purchase 40 per cent of their IT infrastructure as a service.

http://gartner.com/it/page.jsp?id=59320731Monday, February 16, 2009

Page 32: Best Practices in Migrating to MySQL - Part 1

Open Source

• Sun releases Java

• Microsoft releases .Net components

• Adobe release Flex/Flash infrastructure

• MySQL, the 'M' of LAMP

• Be wary of different licensing agreements for software reuse

32Monday, February 16, 2009

Page 33: Best Practices in Migrating to MySQL - Part 1

Road blocks

33Monday, February 16, 2009

Page 34: Best Practices in Migrating to MySQL - Part 1

Barriers to success

• Resource commitment

• Set expectations

• e.g. it works in Oracle it should work in MySQL

• It may be cheaper to migrate but it takes a long time

• Fear of change

• Licensing/IP/Patents/Copyright

34Monday, February 16, 2009

Page 35: Best Practices in Migrating to MySQL - Part 1

Actual Client Example

• Management directs use of MySQL

• Technical resources

• Refuse to use optimal numeric datatypes (could be 25% disk saving)

• Refuse to use covering indexes (improved performance in queries)

• Fudge production simulation (3 full table scans in 15 sample SELECT's)

• Place junior inexperienced staff (in company and technology) on evaluation process

35Monday, February 16, 2009

Page 36: Best Practices in Migrating to MySQL - Part 1

Summary

• MySQL can operate in the enterprise

• There are justifiable reasons to consider MySQL

• Migration to MySQL is possible

• Opportunities, Technology and Time to Market becoming more viable

36Monday, February 16, 2009