https://navicat.com/en/


On Fri, Oct 6, 2023 at 3:11 AM Graham Brown <gbr...@compsys.co.uk> wrote:

> Thanks
>
> What is Navicat?
>
> -----Original Message-----
> From: ProFox [mailto:profox-boun...@leafe.com] On Behalf Of Virgil
> Bierschwale
> Sent: 05 October 2023 20:04
> To: ProFox Email List
> Subject: Re: FW: SQL Upsize
>
> I use navicat.
> copy the dbf to csv or txt.
> use navicat to connect to sql server.
> and then do a import.
>
> I've added about 10GB data to mysql that way and it works pretty good.
> they have a version for sql server as well.
>
>
> On Thu, Oct 5, 2023 at 11:36 AM Graham Brown <gbr...@compsys.co.uk> wrote:
>
> > Hi
> > Thanks
> >
> > Yes, the database and tables all get created via the upsizing wizard so
> > definitely something to do with the data itself
> > The upsizing wizard has worked in the past probably 2000 to 2005 but
> won't
> > work in 2008r2. Havent done one of these in a long time.
> >
> > In the upsizing wizard I uncheck indices, integrity etc etc but made no
> > difference
> >
> > I have created a simple prg to create a cursor adapter on the local data
> > and another on the server data. This does scatter and gather between the
> > two but on a table with 500k records it takes two days to run so too
> slow.
> >
> > The next thing I am going to try is manually creating the insert sql
> > commands and run these in EM, just a pita if I am missing something
> obvious.
> >
> > Interesting one.
> >
> > Graham
> >
> >
> >
> > -----Original Message-----
> > From: ProFox [mailto:profox-boun...@leafe.com] On Behalf Of Kurt Wendt
> > Sent: 05 October 2023 17:21
> > To: ProFox Email List
> > Subject: Re: FW: SQL Upsize
> >
> > Hey there Graham,
> >
> > Now, I know this is going to be more of a WAG or a total
> Shot-in-the-Dark,
> > Butt...
> >
> > Also, I will admit - I am not familiar with the exact process you're
> > attempting to do. I did try something similar MANY Years ago, admittedly
> -
> > back in like 2012. Anyway...
> >
> > So, my question is this - did your Process at least create the Database
> > files in SQL - and SOME of the records did make it into the Database? If
> > so, why not push the records into SQL Databases from FoxPro after the SQL
> > databases were already created?
> >
> > Now, I know - it's Not Addressing your original problem. But, I figured I
> > would throw some suggestions out there...
> >
> > -Kurt
> >
> >
> > On Thu, Oct 5, 2023 at 8:44 AM Graham Brown <gbr...@compsys.co.uk>
> wrote:
> >
> > > Hi all
> > >
> > >
> > >
> > > I am upsizing a Foxpro DBC to SQL 2008 r2. This worked fine with
> earlier
> > > versions of SQL but gives errors to newer versions of SQL. I am using
> > ODBC
> > > rather than Native client although it doesn't make any difference to
> the
> > > errors.
> > >
> > >
> > >
> > > For one specific table the upsize says 988 rows failed. Only a few
> > records
> > > show an error in the report (6) and this is connectivity error failed
> to
> > > convert numeric to float. The destination fields do not show float so
> not
> > > sure what it is complaining about.
> > >
> > >
> > >
> > > Has anyone seen the same please.
> > >
> > >
> > >
> > > Regards
> > >
> > > Graham
> > >
> > >
> > >
> > > Ps Sent the last one to owner@, sorry Ed.
> > >
> > >
> > >
> > >
> > >
> > > --- StripMime Report -- processed MIME parts ---
> > > multipart/alternative
> > >   text/plain (text body -- kept)
> > >   text/html
> > > ---
> > >
[excessive quoting removed by server]

_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: https://leafe.com/archives
This message: 
https://leafe.com/archives/byMID/CAPuy6VNZqLcxBy6cnqSeJFqZ21T-rPF=yhsch-gmez50bnj...@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to