database migration in net
Download
Skip this Video
Download Presentation
Database Migration in .NET

Loading in 2 Seconds...

play fullscreen
1 / 57

Database Migration in .NET - PowerPoint PPT Presentation


  • 92 Views
  • Uploaded on

Database Migration in .NET. Continuous Database Evolution. story. 3. Claire Bennet : Database Administrator + Neat freak + Former cheerleader. Hiro Nakamura: Software developer + Haphazard + Addicted to manga. Mohinder Suresh:

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' Database Migration in .NET' - willis


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
database migration in net

Database Migration in .NET

Continuous Database Evolution

slide5

Claire Bennet:

Database Administrator + Neat freak + Former cheerleader

slide6

Hiro Nakamura:

Software developer + Haphazard + Addicted to manga

slide7

Mohinder Suresh:

Software tester (PhD) + Detail-oriented + Efficiency expert

slide25

Hiro! I just upgraded the test database with that script that you gave me last week, but it doesn’t seem to be working. How do I know if the script has been applied correctly?

changes to shared database are immediately available to everyone

#1

Changes to shared database are immediately available to everyone

(whether they want them or not)

c hanges to shared database a re immediately available to everyone
Changes to shared database are immediately available to everyone

(whether they want them or not)

Separate database instances

claire couldn t easily see what had changed to the database1
Claire couldn’t easily see what had changed to the database

All database changes are under sourcecontrol

suresh was applying database scripts one week after they were available1
Suresh was applying database scripts one week after they were available

Automate database migration

hiro had no way to see if database changes were applied successfully1
Hiro had no way to see if database changes were applied successfully

Version all database changes

slide42

dbDeploy.NET*

http://dbdeploy.com

slide43

Tarantino

  • http://code.google.com/p/tarantino/
slide44

Migrator.NET

  • http://code.google.com/p/migratordotnet/
slide48

dbDeploy.NET

Pro:

Con:

  • Simple
  • Supports SqlServer, Oracle, Sybase, HSQL, MySql
  • DBA-friendly
  • Needs better dev environment support
slide49

Tarantino

Pro:

Con:

  • Easy to get started
  • Automates most dev db tasks
  • No control over version numbers
  • SQL Server-specific
  • Rebaselining?
  • Requires NAnt
slide50

Migrator.NET

Pro:

Con:

  • Easy to get started
  • Cross-database support
  • Supports SqlServer, Oracle, MySql, Postgres
  • Data migration
  • Developer-specific
  • No way to easily capture SQL
agile vancouver conference
Agile Vancouver Conference

November 4-6, 2008

slide54

Background:

    • database scripts in sourcecontrol
    • database instances per developer
  • SqlServer generate scripts
    • what happens after version 1.0
    • what version is this anyway?
  • SqlCompare – take a look
  • version table
  • dbDeploy.net – up and down
  • Tarantino
  • Rails migrations
    • multi-database support (ie in-memory db for integration tests)
    • DSL for database update
    • data migration support
  • what is migrated?
  • in example migrate database containing data (use Northwind)
  • rebaselining
  • managing branches
slide55

dbDeploy.net

    • goal: automate the creation of delta script
    • production focused: hand off to production DBA
      • database migration for most organizations is not automated
    • supported DBs: SqlServer, Oracle, Sybase, MySql, HSql
    • version table: changelog (configurable)
    • versioning: derived from filename
    • does three things:
      • 1) determine which scripts have to be applied
      • 2) increment version for application of each script
      • 3) merge all scripts into a single script
slide56

Tarantino

    • goal: automate database creation and upgrade
    • development focus: easily automatable for as part of build process
      • database migration for most organizations is not automated
    • version table: usd_
    • version=# of executed scripts – rebaselining?
slide57

Migrator.NET

    • goal: leverage Rails-style migrations in .NET
    • cross-database migration support
    • leverage domain objects for persistence
    • version table: SchemaInfo
ad