data-migration

INSERT Data From One Table Into Multiple Tables

家住魔仙堡 提交于 2019-11-30 05:21:35
问题 I'm using SQL Server 2005. I am migrating data over from a current database (single table) to a new database (normalized - many tables). In the new database, I have a base table (let's call it "BaseTable"), and multiple other tables (let's call them "DependentA" , and "DependentB" ). Some of the data from the old database will go to BaseTable, and some will go to the other two. BaseTable has a one-to-one relationship with both DependentA and DependentB, using the Id of them as the foreign key

Error while upgrading Mongodb from 3.2 to 3.6

倖福魔咒の 提交于 2019-11-30 03:15:10
I needed to upgrade mongodb from 3.2 to 3.6 in my environment. For the process i first migrated from 3.2 to 3.4 as recommended. After successful migration to 3.4, i started migration to 3.6 i am not able to start mongod. When checked log file i found error like: IMPORTANT: UPGRADE PROBLEM: The data files need to be fully upgraded to version 3.4 before attempting an upgrade to 3.6; see http://dochub.mongodb.org/core/3.6-upgrade-fcv for more details. MY Mongod.conf systemLog: destination: file logAppend: true path: /var/log/mongodb/mongod.log storage: dbPath: /var/lib/mongo journal: enabled:

South data migration 'instance' error when using south freeze orm

我与影子孤独终老i 提交于 2019-11-29 22:16:01
问题 I have a south datamigration that is trying to create new objects based on data found in other models. When trying to create a new object for the given 'destination' model I keep getting: Cannot assign "<ContentType: ContentType object>": "Publishing.content_type" must be a "ContentType" instance. It seems that there is something wrong with the 'instance' when accessed via the South freeze ORM, e.g.: ContentType = orm['contenttypes.ContentType'] content_type_kwargs = { 'model': ContentModel.

SVN copy between repositories with history

半城伤御伤魂 提交于 2019-11-29 20:07:28
One of my teammates has asked if it is possible to export from one SVN to another, all while maintaining history. To me, this seems like it would be a common request. So: Is it possible to migrate between SVN repositories all while maintaining history? It is important to note that we do not have svnadmin access on the Source, but we do have that on the Destination. If this comes down to just checking out each revision from the source, and checking it in to the destination, we would be OK with that, as long as there was an automated process for that. EDIT: I forgot to mention that the

How to efficiently manage frequent schema changes using sqlalchemy?

喜欢而已 提交于 2019-11-29 19:05:17
I'm programming a web application using sqlalchemy. Everything was smooth during the first phase of development when the site was not in production. I could easily change the database schema by simply deleting the old sqlite database and creating a new one from scratch. Now the site is in production and I need to preserve the data, but I still want to keep my original development speed by easily converting the database to the new schema. So let's say that I have model.py at revision 50 and model.py a revision 75, describing the schema of the database. Between those two schema most changes are

Migration Access to SQL server 2012

北战南征 提交于 2019-11-29 17:00:00
For an project, I need to migrate an Access database to SQL server 2012 express, I found some ways to do this, like using Microsoft up-sizing, but this question is not very technical but just to find out alternative ways, the database in access contains confidential data, so im not allowed to see data and I want to find out is there is any procedure that can be useful for me to achieve migration with out seeing the database itself and how to verify the data is exact in both. I don't have database background so specific directions and resources is useful. I don't know how to search for specific

Migrating DATA - not just schema, Rails

南笙酒味 提交于 2019-11-29 11:58:16
问题 Sometimes, data migrations are required. As time passes, code changes and migrations using your domain model are no longer valid and migrations fail. What are the best practices for migrating data? I tried make an example to clarify the problem: Consider this. You have a migration class ChangeFromPartnerAppliedToAppliedAt < ActiveRecord::Migration def up User.all.each do |user| user.applied_at = user.partner_application_at user.save end end this runs perfectly fine, of course. Later, you need

Can Core Data handle my “system vs. user data” migration needs?

岁酱吖の 提交于 2019-11-29 04:15:32
问题 My iPhone app will have read-only "system" data AND read/write "user" data (stored either using Core Data or a custom SQLite db). The user data may reference the system data. When a new version of the app is installed (e.g., via iTunes): The new system data that comes with the update should overwrite/replace the old system data The user data should be modified to reference the new system data (where possible). Question: How is this kind of migration done with Core Data? Is it feasible? For

Migrating from Postgres to SQL Server 2008

两盒软妹~` 提交于 2019-11-29 03:53:16
I need to migrate a database from Postgres 7 to SQL Server 2008. I am familiar with the SSIS Import and Export wizard but I am stumped about how to define the data source or define the data provider. What is the best way to migrate Postgres to SQL Server, and how do I define data sources/drivers for postgres? I wish you the best of luck in trying to import from PostgreSQL into SQL Server using SQL Server Import and Export Wizard. However, I have read numerous message board threads with people having trouble getting it to work. For example: Import Data from Postgresql to SQL Server 08 Error

Error while upgrading Mongodb from 3.2 to 3.6

萝らか妹 提交于 2019-11-29 00:54:08
问题 I needed to upgrade mongodb from 3.2 to 3.6 in my environment. For the process i first migrated from 3.2 to 3.4 as recommended. After successful migration to 3.4, i started migration to 3.6 i am not able to start mongod. When checked log file i found error like: IMPORTANT: UPGRADE PROBLEM: The data files need to be fully upgraded to version 3.4 before attempting an upgrade to 3.6; see http://dochub.mongodb.org/core/3.6-upgrade-fcv for more details. MY Mongod.conf systemLog: destination: file