Using production DB data locally

[Jeremy Woertink]

What is the best(easiest...) way to get all the data from a production
DB, so I can throw it onto my development DB, and use it locally?

~Jeremy

--
Posted via http://www.ruby-forum.com/.

[Philip Hallstrom]

> What is the best(easiest...) way to get all the data from a production
> DB, so I can throw it onto my development DB, and use it locally?

If it's the same database type then just dump it out of production, copy the dump file to your development machine and import it.

If it's not the same database type, you might look into taps... http://rubygems.org/gems/taps

-philip

[Jeremy Woertink]

Philip Hallstrom wrote in post #962498:

Sweet! Thanks for the link. That's pretty awesome.

Ok, so, I've never actually done a data dump or import before. Both my
production, and development databases are using MySQL (the production
being on a server). Is there a rake task that creates a SQL file? I know
there's rake db:structure:dump, but I'm not sure if this actually will
throw all the data into the SQL file, or just the overall structure of
the DB like the schema. I also need to make sure that whatever command
this is, doesn't just drop my production DB (Don't need a "github
incident") lol.

Thanks for the help,

[Philip Hallstrom]

>>> What is the best(easiest...) way to get all the data from a production
>>> DB, so I can throw it onto my development DB, and use it locally?
>>
>> If it's the same database type then just dump it out of production, copy
>> the dump file to your development machine and import it.
>>
>> If it's not the same database type, you might look into taps...
>> http://rubygems.org/gems/taps
>>
>> -philip
>
> Sweet! Thanks for the link. That's pretty awesome.
>
> Ok, so, I've never actually done a data dump or import before. Both my
> production, and development databases are using MySQL (the production
> being on a server). Is there a rake task that creates a SQL file? I know
> there's rake db:structure:dump, but I'm not sure if this actually will
> throw all the data into the SQL file, or just the overall structure of
> the DB like the schema.

Just the structure...

> I also need to make sure that whatever command
> this is, doesn't just drop my production DB (Don't need a "github
> incident") lol.

Read up on mysqldump.

-philip

[Jeremy Woertink]

> Read up on mysqldump.
>
> -philip

Awesome, that would be what I'm looking for. Thanks man!

[Bala Paranj]

Here is the syntax for export and import: http://bparanj.blogspot.com/2007/06/how-to-export-data-from-one-database.html

--

You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonra...@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-ta...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.

--

Cheers,

Bala

RoR Developer Now Available for Hire