New answers tagged migration
This is by no means the only way or necessarily the best way. You should consider streams and GoldenGate as well, but if at least one application is designed to use packages and access the data only through those packages, consider the following: Create a new database and setup views of the original database's tables for one schema using a database link. ...
There are couple of options which you can use to Minimize your downtime with your current available hardware : Foremost step is to run Upgrade advisor (if the SQL Server versions will be different from Old to New server). Also, take FULL backups first for all the databases - just in-case if something goes wrong. Method 1 : Log Shippping Set up ...
Copy 50 to 100 databases to a completely new server with zero downtime? I don't think that's going to happen. When you're talking about a migration, planned downtime is an absolute must. In this case, depending on the size of the databases, I'd take the scripting route with this. If you are proficient with PowerShell, you can loop through all the ...
Apache DdlUtils can help with some of the migration: http://db.apache.org/ddlutils/ You might also have a skim of the tools listed here: http://wiki.apache.org/db-derby/UsesOfDerby to see if any of those have features that help with migration Derby also has some built-in tools for bulk-importing of data: ...
8 months later, but here's the answer: No problem in having a MySQL 5.5 slave to a 5.1 master. There is a problem with having it the other way around -- I've seen it fail. Your approach is very viable and is being done frequently. You have both B and C replication from A. Then, at some stage you: freeze A (via FLUSH TABLES WITH READ LOCK) Verify both ...
I am using Data Loader, it meets the requirement of migrating data from MS SQL Server to MySQL perfectly. Trial edition can be downloaded from http://www.dbload.com
Not if you used any persisted Enterprise features. If you used any of such there will be an entry in sys.dm_db_persisted_sku_features and when trying to open/attach/restore this database on any edition lower than Enterprise you will gen an exception and the database won't open. The list possible of persisted SKU features are: Compression. Indicates that ...
Yes, if the destination version is the same or higher. You can see this by SELECT @@VERSION You can't restore to a lower version which has been asked many times
You can try out with nuodb.com as it has some simple steps wherein you can migrate your database from SQL Server to cloud. You just need to download some simple application which is free of cost and follow some simple instructions on how to install and use it.
Have a look at Importing Data Into SQLServer on Amazon RDS. Also, from codeplex SQL Database Migration Wizard with a reference video as well.
As long as you are not using features from Standard that are not supported in Express you should be able to move the database between versions. Just don't do an inplace upgrade. You will not be able to roll the upgrade back.
SQL Server editions differ by the features and capabilities that they provide like no.of cpu's , memory, database size, High Availability options, Disaster recovery options, etc. You can refer BOL for more details. When you say Trial - it can be Enterprise Edition for 180 Days. Unless you have the same database version, I would recommend your to do a ...
Yes you can, but it can be somewhat tedious if the database versions are different. If you are staying on the same database version, you should be able to re-attach the database files or restore the database from backup -- assuming that you haven't used any features of the new database that can't be downgraded (like compression or partitioning in the ...
Top 50 recent answers are included