I am using SQL Server 2008 Management Studio and have a table I want to migrate to a different db server.

Is there any option to export the data as an insert into SQL script?? 

Exporting data In SQL Server as INSERT INTO

I am involved in a data migration project. I am getting the following error when I try to insert data from one table into another table (SQL Server 2005):

&gt; Msg 8152, Level 16, State 13, Line 1  
&gt; String or binary data would be truncated.

The source data columns match the data type and are within the length definitions of the destination table columns so I am at a loss as to what could be causing this error.


SQL Server String or binary data would be truncated

I currently have a live redis server running on a cloud instance and I want to migrate this redis server to a new cloud instance and use that instance as my new redis server. If it were MySQL, I would export the DB from the old server and import it into the new server. How should I do this with redis? 

P.S.: I&#39;m not looking to set-up replication. I want to completely migrate the redis server to a new instance.

How do I move a redis database from one server to another?

I am currently using Jenkins on my development PC. I installed it on my development PC, because I had limited knowledge on this tool; so I tested on it in my development PC. Now, I feel comfortable with Jenkins as my long term &quot;partner&quot; in the build process and would like to &quot;move&quot; this Jenkins to a dedicated server.

Before this I have done few builds and have the artifacts archived from each build. In particular, the build number is very important to me for version control.

How can I export all the Jenkins information from my current PC to my new server?


How to move Jenkins from one PC to another

Oracle&#39;s table server offers a built-in function, `TRUNC(timestamp,&#39;DY&#39;)`. This function converts any timestamp to midnight on the previous Sunday. What&#39;s the best way to do this in MySQL?

Oracle also offers `TRUNC(timestamp,&#39;MM&#39;)` to convert a timestamp to midnight on the first day of the month in which it occurs. In MySQL, this one is straightforward:

    TIMESTAMP(DATE_FORMAT(timestamp, &#39;%Y-%m-01&#39;))

But this `DATE_FORMAT` trick won&#39;t work for weeks. I&#39;m aware of the `WEEK(timestamp)` function, but I really don&#39;t want week number within the year; this stuff is for multiyear work.


How to group by week in MySQL?

I recently switched from Django 1.6 to 1.7, and I began using migrations (I never used South).

Before 1.7, I used to load initial data with a `fixture/initial_data.json` file, which was loaded with the `python manage.py syncdb` command (when creating the database).

Now, I started using migrations, and this behavior is deprecated :

&gt; If an application uses migrations, there is no automatic loading of fixtures.
&gt; Since migrations will be required for applications in Django 2.0, this behavior is considered deprecated. If you want to load initial data for an app, consider doing it in a data migration.
 (https://docs.djangoproject.com/en/1.7/howto/initial-data/#automatically-loading-initial-data-fixtures)

The [official documentation][1] does not have a clear example on how to do it, so my question is :

What is the best way to import such initial data using data migrations :

1. Write Python code with multiple calls to `mymodel.create(...)`,
2. Use or write a Django function ([like calling `loaddata`][2]) to load data from a JSON fixture file.

I prefer the second option.

I don&#39;t want to use South, as Django seems to be able to do it natively now.



  [1]: https://docs.djangoproject.com/en/1.7/topics/migrations/#data-migrations
  [2]: https://stackoverflow.com/questions/887627/programmatically-using-djangos-loaddata

Loading initial data with Django 1.7 and data migrations

**DISCLAIMER:** This question is similar to the stack overflow question [here][1], but none of those answers work for my problem, as I will explain later.

I&#39;m trying to copy a large table (~40M rows, 100+ columns) in postgres where a lot of the columns are indexed. Currently I use this bit of SQL:

    CREATE TABLE &lt;tablename&gt;_copy (LIKE &lt;tablename&gt; INCLUDING ALL);
    INSERT INTO &lt;tablename&gt;_copy SELECT * FROM &lt;tablename&gt;;

This method has two issues:

1. It adds the indices before data ingest, so it will take much longer than creating the table without indices and then indexing after copying all of the data.
2. This doesn&#39;t copy `SERIAL&#39; style columns properly. Instead of setting up a new &#39;counter&#39; on the the new table, it sets the default value of the column in the new table to the counter of the past table, meaning it won&#39;t increment as rows are added.

The table size makes indexing a real time issue. It also makes it infeasible to dump to a file to then re-ingest. I also don&#39;t have the advantage of a command line. I need to do this in SQL.

What I&#39;d like to do is either straight make an exact copy with some miracle command, or if that&#39;s not possible, to copy the table with all contraints but without indices, and make sure they&#39;re the constraints &#39;in spirit&#39; (aka a new counter for a SERIAL column). Then copy all of the data with a `SELECT *` and then copy over all of the indices.

**Sources**

1. [Stack Overflow question about database copying][1]: This isn&#39;t what I&#39;m asking for for three reasons
    - It uses the command line option `pg_dump -t x2 | sed &#39;s/x2/x3/g&#39; | psql` and in this setting I don&#39;t have access to the command line
    - It creates the indices pre data ingest, which is slow
    - It doesn&#39;t update the serial columns correctly as evidence by `default nextval(&#39;x1_id_seq&#39;::regclass)`

2. [Method to reset the sequence value for a postgres table][2]: This is great, but unfortunately it is very manual.

[1]:https://stackoverflow.com/questions/198141/copy-a-table-including-indexes-in-postgres
[2]:http://archives.postgresql.org/pgsql-admin/2005-06/msg00152.php
 

Completely copying a postgres table with SQL

What&#39;s the best practice (or tool) for updating/migrating Mongoose schemas as the application evolves?

Dealing with schema changes in Mongoose

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 destination repo is on windows.

SVN copy between repositories with history

I&#39;ve got a rails application where users have to log in.  Therefore in order for the application to be usable, there must be one initial user in the system for the first person to log in with (they can then create subsequent users).  Up to now I&#39;ve used a migration to add a special user to the database.

After asking [this question][1], it seems that I should be using db:schema:load, rather than running the migrations, to set up fresh databases on new development machines.  Unfortunately, this doesn&#39;t seem to include the migrations which insert data, only those which set up tables, keys etc.

My question is, what&#39;s the best way to handle this situation:

  1. Is there a way to get d:s:l to include data-insertion migrations?
  2. Should I not be using migrations at all to insert data this way?
  3. Should I not be pre-populating the database with data at all?  Should I update the application code so that it handles the case where there are no users gracefully, and lets an initial user account be created live from within the application?
  4. Any other options? :)

  [1]: https://stackoverflow.com/questions/62038/rails-model-validators-break-earlier-migrations

How (and whether) to populate rails application with initial data

I&#39;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&#39;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 trivial, for example a new column is declared with a default value and I just want to add this default value to old records. 

Eventually a few changes may not be trivial and require some pre-computation. 

How do (or would) you handle fast changing web applications with, say, one or two new version of the production code per day  ?

By the way, the site is written in Pylons if this makes any difference.







How to efficiently manage frequent schema changes using sqlalchemy?

I have an application which is in BETA mode. The model of this app has some classes with an explicit primary_key. As a consequence Django use the fields and doesn&#39;t create an id automatically.

    class Something(models.Model):
        name = models.CharField(max_length=64, primary_key=True)
 

I think that it was a bad idea (see https://stackoverflow.com/questions/2011629/unicode-error-when-saving-an-object-in-django-admin) and I would like to move back and have an id for every class of my model.

    class Something(models.Model):
        name = models.CharField(max_length=64, db_index=True)


I&#39;ve made the changes to my model (replace every primary_key=True by db_index=True) and I want to migrate the database with &lt;a href=&quot;http://south.aeracode.org/wiki/Tutorial&quot;&gt;south&lt;/a&gt;.

Unfortunately, the migration fails with the following message:
`ValueError: You cannot add a null=False column without a default value.`

I am evaluating the different workarounds for this problem. Any suggestions?

Thanks for your help

What is the best approach to change primary keys in an existing Django app?

I would like to make my app able to do an automatic lightweight migration when I add
 new attributes to my core data model.

In the guide from Apple this is the only info on the subject I could find:

&gt;**Automatic Lightweight Migration**
&gt;
&gt; To request automatic lightweight
&gt; migration, you set appropriate flags
&gt; in the options dictionary you pass in
&gt; addPersistentStoreWithType:configuration:URL:options:error:.
&gt; You need to set values corresponding
&gt; to both the
&gt; NSMigratePersistentStoresAutomaticallyOption
&gt; and the
&gt; NSInferMappingModelAutomaticallyOption
&gt; keys to YES:

    NSError *error;
    NSURL *storeURL = &lt;#The URL of a persistent store#&gt;;
    NSPersistentStoreCoordinator *psc = &lt;#The coordinator#&gt;;
    NSDictionary *options = [NSDictionary dictionaryWithObjectsAndKeys:
        [NSNumber numberWithBool:YES], NSMigratePersistentStoresAutomaticallyOption,
        [NSNumber numberWithBool:YES], NSInferMappingModelAutomaticallyOption, nil];
     
    if (![psc addPersistentStoreWithType:&lt;#Store type#&gt;
        configuration:&lt;#Configuration or nil#&gt; URL:storeURL
        options:options error:&amp;error]) {
        // Handle the error.
    }

My `NSPersistentStoreCoordinator` is initialized in this way:

    - (NSPersistentStoreCoordinator *)persistentStoreCoordinator {
        
        if (persistentStoreCoordinator != nil) {
            return persistentStoreCoordinator;
        }
        
        NSURL *storeUrl = [NSURL fileURLWithPath: [[self applicationDocumentsDirectory] stringByAppendingPathComponent: @&quot;FC.sqlite&quot;]];
        
        NSError *error = nil;
        persistentStoreCoordinator = [[NSPersistentStoreCoordinator alloc] initWithManagedObjectModel:[self managedObjectModel]];
        if (![persistentStoreCoordinator addPersistentStoreWithType:NSSQLiteStoreType configuration:nil URL:storeUrl options:nil error:&amp;error]) {
    
            NSLog(@&quot;Unresolved error %@, %@&quot;, error, [error userInfo]);
            abort();
        }    
        
        return persistentStoreCoordinator;
    }

**I am having trouble seeing where and how I should add the Apple code to get the Automatic Lightweight Migration working?**

Implementation of &quot;Automatic Lightweight Migration&quot; for Core Data (iPhone)

I have a web application using sqlalchemy (within Pylons). I need to effiently change the schema to be able to change the production version at least on a daily basis, maybe more, without losing the data.

I have played a little bit with sqlalchemy-migrate over the week-end and I would say that it gave me a bad impression. First **I think it cannot help with migration between two databases engines**; that&#39;s something that could probably be done with sqlalchemy alone. 
Second the docs do not seem up to date. I had to change some command-line options, like giving the repository path at each command, this could be a bug of migrate. 

But the worst thing it the &quot;manage.py **test**&quot; command. Not only it actually **modifies the database** (this point is clearly indicated in the documentation so I can&#39;t blame migrate) but my first migration script just made plain stupid schema migration, leaving the upgraded-downgraded db with a **different schema than the original**. But the &quot;manage.py test&quot; just answered something like

     success !

That is, it did not even check if the schema was left in a coherent state. 
So **is it worth using migrate?** Is there any advantage compared to the Do It Yourself method associated with good practices [as proposed by S.Lott][1] ?
Are there alternatives to sqlalchemy-migrate actually simplifying the migration process or am I just trying to use migrate with a bad a *priori* (then please show me why is&#39;t clearly superior to creating CSV columns as proposed in the link above)?

Many Thanks!


  [1]: https://stackoverflow.com/questions/4165452/how-to-efficiently-manage-frequent-schema-changes-using-sqlalchemy/4165496#4165496

Is it worth using sqlalchemy-migrate ?

I am trying to use Entity Framework data migrations, as described in &lt;a href=&quot;http://blogs.msdn.com/b/adonet/archive/2012/02/09/ef-4-3-code-based-migrations-walkthrough.aspx&quot;&gt;this post&lt;/a&gt;.

However, when I try to execute the &lt;code&gt;Enable-Migrations&lt;/code&gt; step, I receive the following error in Package Manager Console:

    The target context &#39;MyDataContext&#39; is not constructible. Add a default constructor or provide an implementation of IDbContextFactory

So, I created a factory class that implements &lt;code&gt;IDbContextFactory&lt;/code&gt; in the project that contains my &lt;code&gt;DbContext&lt;/code&gt; class, but data migrations doesn&#39;t appear to recognize it.

Is there something that I should explicitly do to instruct data migrations to use this factory class?


All Data Migration Solutions on Gang of Coders

Total of 15 Data Migration Solutions