Tag Info

New answers tagged

-1

I have good experience with Full Convert.


0

I think just -- exporting db and taking out the json file and import in another system. Or You can directly copy the db from one location to another---- http://docs.mongodb.org/manual/reference/method/db.copyDatabase/


5

Have you looked under Advanced Security Settings? The arrows point to the modifications I've often had to specifically apply when installing SQL Server on Windows 2012 R2. For the SQL Server Root Directory, I'll give full control to the SQL Server Process account. Related official documentation: Configure File System Permissions for Database Engine ...


2

I just quickly grabbed your query and re-wrote it without looking at how you rewrote it. SELECT DISTINCT a_stmt.cyc_dte, a_carr.carr_nm, a_stmt.amt_du_ic FROM a_stmt LEFT OUTER JOIN a_icc on a_stmt.ic_cntct_id = a_icc.ic_cntct_id INNER JOIN a_carr on a_carr.acna = a_stmt.acna INNER JOIN s_dataccs on s_dataccs.acna = ...


0

Straight from the Manual: The easiest approach to migrating convertible data dictionary data is to create a new database in the target character set and then re-create all of the data dictionary and schema definitions by exporting and importing. However, this method means creating a new database. Based on what I'm reading in this manual, that's ...


0

I recently converted an Oracle DB into MySQL using a program called DBConvert There is a free version that inserts watermarks into large tables, but that can be fixed. ;) It's not perfect and might take some tinkering to fix up after the conversion.


1

If your first test showed a problem, assume that there is a problem! Problems don't just disappear on production, even if you have the best possible theory for their existence, you still need to test. BCP copy should be using row-level locks by default. Which should escalate to page-level locks due to the size of your data. If despite these locks, you are ...


1

We recently migrated Oracle 10g/11G databases to AWS and some databases we migrated to MySQL. We used Attunity Replicate for the Oracle->MySQL, which let us keep the AWS database in sync with the Oracle database until cutover. The issues you will hit as other replies indicate are stored procedures and functions, some data type issues, issues with Oracle ...


1

Not sure if the issue is resolved. But as suggested here're some ways you can do this : 1. ALTER TABLE Approach : ALTER TABLE ENGINE=INNODB; Considerations for this approach : As you mentioned you have a big table this command will take time to execute. CREATE TABLE and INSERT INTO Approach : You can create a empty table with INNODB storage engine and ...


1

I have an MyISAM2InnoDB blog that covers your question thoroughly. It discusses index differences, especially PRIMARY KEY and FULLTEXT, space (2x-3x is typical), LOCK TABLES, decreasing key_buffer_size and increasing innodb_buffer_pool_size (very important), etc.


1

Here is what you need to do Open the table in definition view Select a cell in the column which is empty. Add an entry of that data type (I picked the datetime in an example where this happened to me) When done, you should be able to click the data button and see all the data.


3

InnoDB tables tend to occupy more space than MyISAM tables do. While converting, new physical files are being created, so you have to have free space on the disk (Hard to estimate, but to be safe I would say 120G) If you use Percona tools to make the change online, all modifications on the original table will be stored in a temporary table using triggers. ...


1

I would recommend dumping the 9.1 database from your new 9.3 server like this: pg_dump -h remoteserver -U remoteuser remotedbname -Fc -f my_old_server_backup.dump I recommend using the 9.3 pg_dump as pg_dump is always backwards compatible, but not forward compatible. In other words, the newer pg_dump will take care of any syntax changes that the new ...


2

Unless you have data in your SSAS cubes that no longer exists in your source (if this is the case correct that going forward!) then you can simply install a new instance of SSAS then deploy and process your SSAS solutions from SSDT (the 2012+ replacement for BIDS). For SSRS if you have a basic install you can do the same thing - simply install the new ...



Top 50 recent answers are included