New answers tagged migration
You can use this method (assuming both tables have same columns in same order): with T as (delete from only company where id=? returning *) insert into school select * from T
The following logins will be created on installation. They are containers for the accounts that the SQL Server Database Engine & Agent run under. [NT SERVICE\MSSQLSERVER] [NT SERVICE\SQLSERVERAGENT] The other accounts are groups that have been manually added into your SQL instance. BUILTIN\Administrators was installed by default in SQL Server 2005 ...
This is a simple backup and restore process, with the additional step of making sure you backup the Reporting Services key, so you can restore that as well. A number of links on the internet, but this one is a step by step guide with screenshots, much easier than trying to follow MSDN ...
Report Server Database can be backedup and migrated over to the new server in the new network which shouldn't be a trouble. Only problem I see is the Report Server URL, which is not mostly same as before. But, you should still have the same data as before after migration, but, with a different URL after migration.
No need to de-install Oracle rdbms software. Just install and configure ASM. If you have enough storage available you can copy your database to ASM using rman.
The Oracle docs for 11.2 ASM migration are here: http://docs.oracle.com/cd/E11882_01/server.112/e18951/asm_rman.htm#OSTMG12000 These explain the process that you need to go through to migrate to ASM from filesystem storage.
PostgreSQL creates subdirectories named for the PostgreSQL version within each tablespace. So AFAIK pg_upgrade doesn't need to be told to take special action for the tablespaces. It will use the same tablespaces as the original database, but won't conflict because of the use of different subdirectories within the tablespace root. The caveat is that if you ...
You use mysqldump. Step 1. Dump your original 32 bit database. mysqldump my32bitdb [options...] > mydb.sql Step 2. Copy the file mydb.sql to your new server Step 3. Load the 32 bit database mysql -u root -p my64bitdb < C:\path\to\mydb.sql With 10GB of data, it shouldn't take much more than ~ 1hr. For reference, see here and here.
If you are moving the database (backup on old server and restore on new server) the MVs will come along. Are you creating an empty database on the new server? If so you could use Data Pump to export the MVs from the old and import them into the new. I would opt for using a full RMAN (or filesystem) backup and restore over Data Pump.
Top 50 recent answers are included