does anyone have a good idea how i can easily import a mysql dump file in a
sql server 2000 enterprise edition
The dump file is 7 gig big however my MS SQL server is a DELL poweredge 4600
with 2 x 2.8 GHZ hyperthreaded XEON processors 800 gig harddisk space
and 6 gig of memory ( running on Windows 2000 advanced with PAE and AWE
extensions enabled )
hope someone has experience with this
Michel Posseth [MCP ]M. Posseth wrote:
> does anyone have a good idea how i can easily import a mysql dump
> file in a sql server 2000 enterprise edition
> The dump file is 7 gig big however my MS SQL server is a DELL
> poweredge 4600 with 2 x 2.8 GHZ hyperthreaded XEON processors
> 800 gig harddisk space and 6 gig of memory ( running on Windows 2000
> advanced with PAE and AWE extensions enabled )
> hope someone has experience with this
> Michel Posseth [MCP ]
I don't know what a dump file is, but if it's just extracted data from a
MySQL table, you can use the DTS Import/Export Wizard to import the
results into SQL Server.
David Gugick
Imceda Software
www.imceda.com|||MySQL dump file is proprietary and SQLServer wouldn't know what to do with
it. You will need to load the dump file into a MySQL somewhere and then
follow this whitepaper to transfer your data.
http://www.microsoft.com/technet/pr...ploy/mysql.mspx
-oj
"M. Posseth" <michelp@.nohausystems.nl> wrote in message
news:ctr4r3$di0$1@.reader13.wxs.nl...
> does anyone have a good idea how i can easily import a mysql dump file in
> a
> sql server 2000 enterprise edition
> The dump file is 7 gig big however my MS SQL server is a DELL poweredge
> 4600
> with 2 x 2.8 GHZ hyperthreaded XEON processors 800 gig harddisk space
> and 6 gig of memory ( running on Windows 2000 advanced with PAE and AWE
> extensions enabled )
> hope someone has experience with this
> Michel Posseth [MCP ]
>|||David Gugick wrote:
> M. Posseth wrote:
>
>
> I don't know what a dump file is, but if it's just extracted data from a
> MySQL table, you can use the DTS Import/Export Wizard to import the
> results into SQL Server.
>
a sql dump file is just a SQL script with DDL and data ( the same as
you can make in SQL server ) however with its own SQL dialect
so instead that it contains data from one table it contains all data
from a database
i know that it is possible to import the sql dump after changing the
dialect parameters to the corresponding mssql dialect
however we are talking about a 7 gig SQL text file
so i was just wondering if someone knows how i can unleash the power of
my MSSQL server on this mysql dump file so i can import it.
well i guess i am pioneering again ,
how the #$#$$% am i gonna loop through a 7 gig text file and find and
replace the mysql datatypes for the corresponding MSSQL datatypes .......
Michelsql
Showing posts with label easily. Show all posts
Showing posts with label easily. Show all posts
Wednesday, March 28, 2012
Import into SQL Server Oracle Database from Export File (SQL*Loader)
I need to import an Oracle Database into SQL Server 2000.
I know this can be done easily using DTS but I do not have access to the
Oracle Database, I only have an Oracle Database Export File.
The Export file has been generated using SQL*Loader.
Oracle Export File is created with a proprietery format that can only be
read by the importer. This is the same problem if you take a SQL backup file
and try to load it into Oracle without access to a SQLServer.
-oj
"K Kelly" <kkelly@.nospam.com> wrote in message
news:eryCZe8$EHA.2608@.TK2MSFTNGP10.phx.gbl...
>I need to import an Oracle Database into SQL Server 2000.
> I know this can be done easily using DTS but I do not have access to the
> Oracle Database, I only have an Oracle Database Export File.
> The Export file has been generated using SQL*Loader.
>
|||On Fri, 21 Jan 2005 14:42:22 -0000, "K Kelly" <kkelly@.nospam.com> wrote:
>I need to import an Oracle Database into SQL Server 2000.
>I know this can be done easily using DTS but I do not have access to the
>Oracle Database, I only have an Oracle Database Export File.
>The Export file has been generated using SQL*Loader.
>
While it may not be strictly legal from a licensing standpoint, there is an approach that may work. First, Oracle
makes copies of their older software available for downloading from their website. Therefore, you could download a
copy of Oracle and install it on a suitable system. Next, import the Oracle database from the export file. Be
warned -- the export file also includes information on directory locations for database files, rollback segments,
and so on. In order for the import to work properly, you need to make sure that you replicate the file system
environment exactly. Oracle will not re-create it on the fly, so you may spend quite a bit of time reading error
logs before you can get it right. In the end, though, it should work correctly.
Once you have the Oracle database up and running, use DTS from SQL Server to cross over the data you need,
remembering to deal with issues such as data type conversions, etc. (pardon me for straying into "I know that!!"
areas). After you get it crossed over, then kill the Oracle installation before the license police catch you.
I once did a similar thing years ago in the opposite direction. I needed to move a DocsOpen SQL 4.0 database into
Oracle 7.2, but the Docs application no longer supported SQL 4, only SQL 6.5 and above. However, Microsoft had a
120-day demonstration version of SQL 6.5 on their website. So I downloaded that, used it to upgrade the SQL 4
database to SQL 6.5, then ran DocsOpen to move it from SQL Server to Oracle 7.2. Worked a treat. Crazily enough, I
have to now move that same database from Oracle 8.1 to SQL Server 2000 in the next couple of weeks.
Good luck.
|||Clever! ;-)
-oj
"Norm Powroz" <npowroz.delete.this.part@.and.this.part.rogers.com > wrote in
message news:1a45v09n8p0j4ud4ep57cdu91vgav6qv2r@.4ax.com...
> On Fri, 21 Jan 2005 14:42:22 -0000, "K Kelly" <kkelly@.nospam.com> wrote:
>
> While it may not be strictly legal from a licensing standpoint, there is
> an approach that may work. First, Oracle
> makes copies of their older software available for downloading from their
> website. Therefore, you could download a
> copy of Oracle and install it on a suitable system. Next, import the
> Oracle database from the export file. Be
> warned -- the export file also includes information on directory locations
> for database files, rollback segments,
> and so on. In order for the import to work properly, you need to make sure
> that you replicate the file system
> environment exactly. Oracle will not re-create it on the fly, so you may
> spend quite a bit of time reading error
> logs before you can get it right. In the end, though, it should work
> correctly.
> Once you have the Oracle database up and running, use DTS from SQL Server
> to cross over the data you need,
> remembering to deal with issues such as data type conversions, etc.
> (pardon me for straying into "I know that!!"
> areas). After you get it crossed over, then kill the Oracle installation
> before the license police catch you.
> I once did a similar thing years ago in the opposite direction. I needed
> to move a DocsOpen SQL 4.0 database into
> Oracle 7.2, but the Docs application no longer supported SQL 4, only SQL
> 6.5 and above. However, Microsoft had a
> 120-day demonstration version of SQL 6.5 on their website. So I downloaded
> that, used it to upgrade the SQL 4
> database to SQL 6.5, then ran DocsOpen to move it from SQL Server to
> Oracle 7.2. Worked a treat. Crazily enough, I
> have to now move that same database from Oracle 8.1 to SQL Server 2000 in
> the next couple of weeks.
> Good luck.
>
sql
I know this can be done easily using DTS but I do not have access to the
Oracle Database, I only have an Oracle Database Export File.
The Export file has been generated using SQL*Loader.
Oracle Export File is created with a proprietery format that can only be
read by the importer. This is the same problem if you take a SQL backup file
and try to load it into Oracle without access to a SQLServer.
-oj
"K Kelly" <kkelly@.nospam.com> wrote in message
news:eryCZe8$EHA.2608@.TK2MSFTNGP10.phx.gbl...
>I need to import an Oracle Database into SQL Server 2000.
> I know this can be done easily using DTS but I do not have access to the
> Oracle Database, I only have an Oracle Database Export File.
> The Export file has been generated using SQL*Loader.
>
|||On Fri, 21 Jan 2005 14:42:22 -0000, "K Kelly" <kkelly@.nospam.com> wrote:
>I need to import an Oracle Database into SQL Server 2000.
>I know this can be done easily using DTS but I do not have access to the
>Oracle Database, I only have an Oracle Database Export File.
>The Export file has been generated using SQL*Loader.
>
While it may not be strictly legal from a licensing standpoint, there is an approach that may work. First, Oracle
makes copies of their older software available for downloading from their website. Therefore, you could download a
copy of Oracle and install it on a suitable system. Next, import the Oracle database from the export file. Be
warned -- the export file also includes information on directory locations for database files, rollback segments,
and so on. In order for the import to work properly, you need to make sure that you replicate the file system
environment exactly. Oracle will not re-create it on the fly, so you may spend quite a bit of time reading error
logs before you can get it right. In the end, though, it should work correctly.
Once you have the Oracle database up and running, use DTS from SQL Server to cross over the data you need,
remembering to deal with issues such as data type conversions, etc. (pardon me for straying into "I know that!!"
areas). After you get it crossed over, then kill the Oracle installation before the license police catch you.
I once did a similar thing years ago in the opposite direction. I needed to move a DocsOpen SQL 4.0 database into
Oracle 7.2, but the Docs application no longer supported SQL 4, only SQL 6.5 and above. However, Microsoft had a
120-day demonstration version of SQL 6.5 on their website. So I downloaded that, used it to upgrade the SQL 4
database to SQL 6.5, then ran DocsOpen to move it from SQL Server to Oracle 7.2. Worked a treat. Crazily enough, I
have to now move that same database from Oracle 8.1 to SQL Server 2000 in the next couple of weeks.
Good luck.
|||Clever! ;-)
-oj
"Norm Powroz" <npowroz.delete.this.part@.and.this.part.rogers.com > wrote in
message news:1a45v09n8p0j4ud4ep57cdu91vgav6qv2r@.4ax.com...
> On Fri, 21 Jan 2005 14:42:22 -0000, "K Kelly" <kkelly@.nospam.com> wrote:
>
> While it may not be strictly legal from a licensing standpoint, there is
> an approach that may work. First, Oracle
> makes copies of their older software available for downloading from their
> website. Therefore, you could download a
> copy of Oracle and install it on a suitable system. Next, import the
> Oracle database from the export file. Be
> warned -- the export file also includes information on directory locations
> for database files, rollback segments,
> and so on. In order for the import to work properly, you need to make sure
> that you replicate the file system
> environment exactly. Oracle will not re-create it on the fly, so you may
> spend quite a bit of time reading error
> logs before you can get it right. In the end, though, it should work
> correctly.
> Once you have the Oracle database up and running, use DTS from SQL Server
> to cross over the data you need,
> remembering to deal with issues such as data type conversions, etc.
> (pardon me for straying into "I know that!!"
> areas). After you get it crossed over, then kill the Oracle installation
> before the license police catch you.
> I once did a similar thing years ago in the opposite direction. I needed
> to move a DocsOpen SQL 4.0 database into
> Oracle 7.2, but the Docs application no longer supported SQL 4, only SQL
> 6.5 and above. However, Microsoft had a
> 120-day demonstration version of SQL 6.5 on their website. So I downloaded
> that, used it to upgrade the SQL 4
> database to SQL 6.5, then ran DocsOpen to move it from SQL Server to
> Oracle 7.2. Worked a treat. Crazily enough, I
> have to now move that same database from Oracle 8.1 to SQL Server 2000 in
> the next couple of weeks.
> Good luck.
>
sql
Subscribe to:
Posts (Atom)