New answers tagged import
since you are using TSV file you can use the following command to import the data: LOAD DATA INFILE 'data.tsv' INTO TABLE database_name.my_table; references: http://dev.mysql.com/doc/refman/5.1/en/load-data.html http://forums.devshed.com/mysql-help-4/importing-tab-separated-file-tsv-table-853669.html ...
As a solution for someone who can't get pv to work or for whom pv tells lies. You can monitor the size of ibdata1 file in /var/lib/mysql which contains the data. This will end up the same size (or thereabouts) of the filesize in your source server. If there are many tables you can also watch them appear one by one in /var/lib/mysql/< database name>.
i think you need to use path/to/file.sql instead of path\to\file.sql and "database < path/to/file.sql" didnt work for me for some reason - i had to use "use database;" and "source path/to/file.sql;"
In FoxPro, under the Wizard menu, choose "upsizing". From there, choose an ODBC connection to the SQL Server database and step through it. Also, there is a much improved upsizing Visual FoxPro project that you can download here. I have had trouble upsizing to SQL Server 2008 and above so if you have a SQL Server 2005 database around, you might have more ...
You can't directly restore a MySQL backup to MSSQL. What you can do is use tools such as Microsoft SQL server migration assistant. But those still won't help you if you don't have the proper permissions on the destination server. You'll most likely be creating a database, editing schemas and creating logins and users. Which means you need the sysadmin ...
From BOL: If the database being restored does not exist, the user must have CREATE DATABASE permissions to be able to execute RESTORE. If the database exists, RESTORE permissions default to members of the sysadmin and dbcreator fixed server roles and the owner (dbo) of the database (for the FROM DATABASE_SNAPSHOT option, the database always ...
The size needed in a temporary tablespace depends on the data volume manipulated, but including potentially other actions also requiring temporary space. What you should be doing is this : monitor temporary tablespace usage, (temporarily) expand the temporary tablespace. Maybe, you need to recreate your temp tablespace. That is, if there is corruption of ...
You would need to use Dynamic SQL to pass a dynamic file path to the Bulk Insert. DECLARE @FileName NVARCHAR(4000); SET @FileName = '/path/to.csv'; DECLARE @sql NVARCHAR(4000) = 'BULK INSERT #CSV FROM ''' + @FileName + ''' WITH ( FIELDTERMINATOR ='','', ROWTERMINATOR =''\n'' )'; EXEC(@sql);
Top 50 recent answers are included