Re: The connection is dead

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



> 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?
>>
>>

.



Relevant Pages

  • CREATE AGGREGATE failed because type Concatenate does not conform to UDAGG specification due to meth
    ... Now register the assembly and the aggregate in the SQL Server database you want ... I'm trying to do some CLR integration with sql server 2005. ...
    (microsoft.public.sqlserver.programming)
  • Re: How do i move an SQLDatabase to another location?
    ... I went to my clients and installed SQL Server ... Express and copied my database to the same location it was in while i was ... knowing that i can bring a database with me and install ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: New to Windows CE Development - Have some questions
    ... validating against the main database, or querying the database during data ... iterate through the SQL CE table and create new entries in the ... SQL Server database that correspond. ... >>> not connected to the Enterprise. ...
    (microsoft.public.windowsce.app.development)
  • RE: Logging in in background
    ... wold take all kinds of modifictions as I'd need to be checking that each SQL ... my database and all have connection strings associated with them. ... I suspect that there is also an issue on the SQL Server side as I keep ...
    (microsoft.public.access.modulesdaovba)
  • RE: SBS 2003 Unable to connect to database STS_Config
    ... MSDE to store SharePoint uses the MSSQL$SharePoint database, ... SharePoint named instance to full SQL. ... You cannot upgrade the Monitoring instance to SQL ... What I see is the SQL server group and under ...
    (microsoft.public.windows.server.sbs)