While waiting for a MSSQL backend compatible with Django 1.6, I've been doing development using SQLite and using South to keep my models synced with the DB.
Now that django-mssql v. 1.5 (which supports Django 1.6) is available, I'd like to move my Django models to a SQL Server database. Note that there is only test data in my SQLite database, so there's no need to migrate the data - I'm only interested in implementing the models in SQL Server, and using South to implement schema modifications going forward.
I think the proper procedure after installing django-mssql is:
Change the settings.py to point to the MSSQL database per the
django-mssql installation instructions
Remove all of the existing South migrations and the migrations
folder
Run manage.py syncdb
Run manage.py schemamigration --initial <application_name>
Run manage.py migrate <application_name>
Have I missed anything?
Related
I have a Spring Boot app running for filling a MySQL database with data I want to analyze with OLAP. I chose Pentaho Data Integration, Schema Workbench and Business Intelligence Server (CE versions) to create my data warehouse. In the ETL process I just fill my data warehouse with the data I generated with my Spring Boot app. In the BI-Server I use the Saiku plugin to make all the OLAP operations and it all works quite nicely.
However I want to make all of that public.
Where is it possible to deploy my app with a database (preferably MySQL) and the BI-Server?
I've looked into Heroku and it seems to use PostgreSQL databases and I haven't found out about a possibility to deploy my BI-Server... Or should I move away from Pentaho and use other solutions to make OLAP on my data warehouse?
Any recommendations?
You`d better use some cloud service like https://www.digitalocean.com/ or amazon. For your own linux server. At this server you can install BI server and Mysql.
I'm in OSX and I'm creating a new ASP.NET Core Web API. I've followed this tutorial: https://docs.efproject.net/en/latest/platforms/netcore/new-db-sqlite.html
That's cool and all but what about Sql Server? Now I know SQL Server won't yet run on OSX (https://www.microsoft.com/en-us/cloud-platform/sql-server-on-linux).
The only way I can see to make this work is if I create a cloud remote SQL server (on Azure or similar), then connect with it from my ASP.NET core application. I tried following this, but it assumes VS2015 https://docs.efproject.net/en/latest/platforms/aspnetcore/existing-db.html. We don't have the package manager console in VSCode and I don't know if there is an equivalent to Scaffold-DbContext.
So how do I make a connection to SQLServer and how do I do things like EF migrations to update that database.
All the packages download can be done without the package installer, by using project.json and dotnet restore (if VSCode doesn't do it when project.json is saved).
With the tools installed, you can create migrations with dotnet ef migrations add <migration name> and dotnet ef database update to apply the migrations to the db schema.
Class libraries (where DbContext and models are defined in class library) are not supported yet. There is a workaround in the Entity Framework Core docs though.
For scaffolding the usage is dotnet ef dbcontext scaffold [arguments] [options]. See the Scaffolding docs for details.
I am developing an application that will use SQL Azure for the production database. I will be developing locally against SQL Express on my machine. If I make changes to the schema, how do I migrate those changes to SQL Azure but still retain all of my production data? For the initial migration I used SQL Azure Migration Wizard, but that was before I had any data. Should I make a backup of the data, recreate the database with the new schema, and then restore the data?
I think that its a general schema versioning question. One possible solution is having migration scripts that you write and test during development and run on production during deployment phase. Entitiy Framework offers migrations as one of it features. My current prefered tool is FluentMigrator. I works for Azure Sql as well.
In order to migrate changes to SQL Server but still retain all of your production data, it is highly recommended that you version your database schema. This also applies to SQL Azure and all other RDBMSs.
This is very important when there are several developers working on a project but I believe it is also advantageous when you are working on a project by yourself.
RoundhousE is one of several simple tools you can use to achieve database versioning. It served us well for this purpose for the past 4 years: https://code.google.com/p/roundhouse/
I followed the excellent tutorial on
http://www.jakusys.de/blog/2008/09/grails-and-liquibase-how-to-use/
in regard to my dev database on local machine where grails is installed. All went well.
Now I want to deploy grails war to remote website where I setup mysql on remote server.
But I am at loss now. How do I apply the command:
grails migrate
so that the now the remote database has the DATABASECHANGELOG table.
In the database there is some production data that I will manually copy from my local mysql to fresh install of remote mysql database while most of other tables are fresh and have no data. I am waiting for reply to this question to make sure I don't mess up something before actually launch my grails application on remote production server.
You can migrate a remote DB from your computer, using grails.env variable, like:
grails migrate -Dgrails.env=production
I am on a shared host and whilst in development (umbraco) I think it would be easier to use VistaDB then package up to install to SQL Server. However, I have already started using SQL Server. Is there a way to migrate my SQL Server (2008) database to VistaDB. I assume the schema is identical but I need a way/tool to move the data to VistaDB.
You could migrate to VistaDB in the same way that you want to migrate data from development to production. Create a package from your current SQL Server-based development site, then create a new empty install of Umbraco with a VistaDB database and import the package there.
This would also be a useful dry run to check that migration to production is going to work as smoothly as you expect.
You can also use the Data Migration Tool in VistaDB to migrate any SQL Server database to VistaDB 4. If you need an older migration (I think the current Umbraco is still using VDB3 files) contact support through the VistaDB.Net site and someone will help you.