Re: The connection is dead
- From: "m.posseth" <michelp@xxxxxxxxxxxxxxx>
- Date: Sat, 24 Dec 2005 18:11:04 +0100
> You were about to tell me to use the databases migration tools weren't
> you :)--can't
Nope ...
I have been there ,, however in my case it was a 7,5 gigabyte mysql dump
database that i needed to import in SQL server 2000
tryed everything to automate this process ,,,, but in the end i succeeded
with a processing time of +- 30 minutes
my solution was to dump the file to a MYSQL dump wich is text based then i
wrote a VB.net program that run through this file and converted the Mysql
dialect to MSSQL Dialect
run the DDL SQL and batch inserted a few hundred records at once to MSSQL .
this was much faster as ODBC connections etc etc that could be made to MYSQL
to MSSQL this process took for this program a whole weekend to complete
maybe this gives you some ideas :-)
regards
Michel Posseth [MCP]
"cj" <cj@xxxxxxxxxxxxx> wrote in message
news:%23GxPcyJCGHA.1032@xxxxxxxxxxxxxxxxxxxxxxx
> I'm moving all the tables in a remote informix database to a local sql
> server database. Fill via the odbcadapter and update with the sqladapter
> was the best way I could come up with. Don't even go there. You were
> about to tell me to use the databases migration tools weren't you
> :)--can't--don't have time to explain.
>
> Still there's a nice feeling knowing that the computer is spending a lot
> of time on this project especially after all the work it's put me through.
> Let it work over Christmas. Otherwise it'd be wasted processing potential
> anyway.
>
>
> m.posseth wrote:
>> maybe a glitch in the line ???
>>
>>
>> i can`t inmagine why you would like to transfer such a hughe amount of
>> data , i work also with databases that contain millions of records
>> however i never encountered a situation when i needed to transfer such
>> amounts in a dataset
>>
>> regards
>>
>> Michel Posseth [MCP]
>>
>>
>>
>>
>> "cj" <cj@xxxxxxxxxxxxx> wrote in message
>> news:%23J8uiqDCGHA.1028@xxxxxxxxxxxxxxxxxxxxxxx
>>
>>>I left a program running Thursday when I left for the holiday. It was
>>>filling a dataset with just over 3 million records from a table across a
>>>VPN connection. Estimates I made from other large, but not this large,
>>>tables suggested it would take approximately 18 hours to run. I just
>>>checked in on it and it had failed in the fill command. The error
>>>message it gave me was the "connection is dead" Given the length of time
>>>it was to take I don't doubt something happened but nothing should have
>>>happened. Is there anything I can do to make the odbcadapter.fill less
>>>likely to have these problems?
>>
>>
.
- References:
- The connection is dead
- From: cj
- Re: The connection is dead
- From: m.posseth
- Re: The connection is dead
- From: cj
- The connection is dead
- Prev by Date: RE: Data validation - Mouse / key press
- Next by Date: Re: ENUM is string or integer ??
- Previous by thread: Re: The connection is dead
- Next by thread: Re: The connection is dead
- Index(es):
Relevant Pages
|