database-migration

Is there any way/laravel-command to drop a specific table from the production server? Set up a migration. Run this command to set up a migration: php artisan make:migration drop_my_table Then you can structure your migration like this: <?php use Illuminate\Database\Schema\Blueprint; use Illuminate\Database\Migrations\Migration; class DropMyTable extends Migration { /** * Run the migrations. * * @return void */ public function up() { // drop the table Schema::dropIfExists('my_table'); } /** * Reverse the migrations. * * @return void */ public function down() { // create the table Schema::create

I am looking for information concerning the following: What are the best practices for updating the schema of my dev DB to my production DB, or even more succinctly making DB schema changes in general. The production database is the back-end for two distinct ASP.NET websites. Our schema change process is fairly robust with each "migration" actually being a .cs file containing the schema changes. We will then use ADO.NET to apply the schema changes against the db. My question is more about the connectivity of the database. Should I stop the two websites that are accessing the db. I assume I

Something really annoying is happening to me since using Django migrations (not south) and using loaddata for fixtures inside of them. Here is a simple way to reproduce my problem: create a new model Testmodel with 1 field field1 (CharField or whatever) create an associated migration (let's say 0001 ) with makemigrations run the migration and add some data in the new table dump the data in a fixture testmodel.json create a migration with call_command('loaddata', 'testmodel.json') : migration 0002 add some a new field to the model: field2 create an associated migration ( 0003 ) Now, commit that

I want to remove an app from a django project. I want to remove the tables of the app the content-types foreign-key usages of these content-types Running manage.py migrate app_to_remove zero does not work: django.db.migrations.migration.IrreversibleError: Operation <RunPython <function forwards_func at 0x7ff76075d668>> in fooapp.0007_add_bar is not reversible I guess there are several migrations which are not reversible ... First: Remove references in the code remove app_to_remove from settings.INSTALLED_APPS remove other references in urls.py or other places Second: Clean the database Create

I'm looking to migrate from Postgres 9.3 to 9.4, and have a lot of data in JSON columns. While it's fine, I wanted to have a look at migrating to the more efficient column storage (which JSONB seems to be — a really exciting piece of tech!). To actually migrate, I want to know migration characteristics for something like ALTER TABLE table_with_json ALTER COLUMN my_json SET DATA TYPE jsonb USING my_json::jsonb; (from this helpful question ). Ideally, it would be good to know how long it takes to migrate 1mil and 10mil entries, and how it scales. While I can get these numbers myself, I thought

Are there any tools to convert SQL Server 2014 database to 2012? I tried Generate Script but the generated script with data is too large and SQL Server Management Studio did not execute it, I need to have both schema and data. To my knowledge, there are basically three two options for migrating a database to a lower version of SQL Server, without using 3rd party tools: Generate Scripts (not really suitable for large amounts of data) Custom Scripting and BCP or Import/Export Wizard SQL Server Integration Services (Transfer Database Task) First option is not suitable in your case, as noted.

I made a migration with this setup: $table->increments('id'); $table->integer('user_id', 10)->unsigned(); // this is meant to be used as a foreign key After doing php artisan migrate it returns an error: [Exception] SQLSTATE[42000]: Syntax error or access violation: 1075 Incorrect table definition; there can be only one auto column and it must be defined as a key (SQL: create table `transactions` (`id` int unsigned not null auto_increment primary key, `user_id` int unsigned not null auto_increment primary key) default character set utf8 collate utf8_unicode_ci) (Bindings: array ()) I didn't

The error I get when I try to runserver for my django app is as follows: django.db.migrations.graph.NodeNotFoundError: Migration tasks.0001_initial dependencies reference nonexistent parent node (u'auth', u'0007_alter_validators_add_error_messages') This happened after I followed this heroku tutorial: https://devcenter.heroku.com/articles/getting-started-with-django I modified the settings file to include: import dj_database_url SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https') import os BASE_DIR = os.path.dirname(os.path.abspath(__file__)) STATIC_ROOT = 'staticfiles' DATABASES = {