Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Foxpro can't query on two tables more than 7m
Message
De
25/04/2007 14:03:58
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Base de données, Tables, Vues, Index et syntaxe SQL
Divers
Thread ID:
01219859
Message ID:
01219865
Vues:
13
This message has been marked as the solution to the initial question of the thread.
First of all, 7m is not a problem. Secondly, you could do following to collect deleted records:
Select * From oldtable Where mijbrpls+vlgnr_mut Not in (Select mijbrpls+vlgnr_mut From newtable)
I assumed that key fields are character, you can modify code if they are integer.

>Hi all,
>
>I'm having a big problem with a query which doesn't work (the query doesn't finish and computer goes on tilt). I have two tables who are almost identical only that one table is of the previous year and the other of this year. Every year the number of records get bigger but it also happens that there are records that have been deleted in the new download. I want to know the deleted records from the old table by comparing both tables with a query. Both that tables are more than 7 million records (I say this because I think that foxpro can't handle this, is this true?). The query is very simple:
>
>
>Select mutbdrg.*, b.mijbrpls as recdeleted from mutbdrg;
>left outer join b;
>on b.mijbrpls = mutbdrg.mijbrpls and b.vlgnr_mut = mutbdrg.vlgnr_mut
>
>
>
>Mutbdrg is of this year and b of previous year. So the goal is to have the deleted records. But this query doesn't get finished....
>
>I'm having the following datasample:
>
previous year
>
>mijbrpls	vlgnrbsvz	vlgnrplsvr	vlgnr_mut	bdr_srt
>21103076903	1	2	29	VSCPRM
>21103076903	1	2	30	AKPKST
>21103076903	1	2	30	APRV
>21103076903	1	2	30	BNSPRV
>21103076903	1	2	30	INCKST
>21103076903	1	2	30	INCPRV
>21103076903	1	2	30	ISOP
>21103076903	1	2	30	PLSOP
>21103076903	1	2	30	1STKST
>21103076903	1	2	31	BHRKST
>21103076903	1	2	32	RISPRM
>21103076903	1	2	33	VSCPRM
>21103076903	1	2	34	AKPKST
>21103076903	1	2	34	APRV
>21103076903	1	2	34	BNSPRV
>21103076903	1	2	34	INCKST
>21103076903	1	2	34	INCPRV
>21103076903	1	2	34	ISOP
>21103076903	1	2	34	PLSOP
>21103076903	1	2	34	1STKST
>21103076903	1	2	35	BHRKST
>21103076903	1	2	36	RISPRM
>21103076903	1	2	37	VSCPRM
>21103076903	1	2	38	AKPKST
>21103076903	1	2	38	APRV
>
>
this year
>
>mijbrpls	vlgnrbsvz	vlgnrplsvr	vlgnr_mut	bdr_srt
>21103076903	1	2	29	VSCPRM
>21103076903	1	2	30	AKPKST
>21103076903	1	2	30	APRV
>21103076903	1	2	30	BNSPRV
>21103076903	1	2	30	INCKST
>21103076903	1	2	30	INCPRV
>21103076903	1	2	30	ISOP
>21103076903	1	2	30	PLSOP
>21103076903	1	2	30	1STKST
>21103076903	1	2	31	BHRKST
>21103076903	1	2	32	RISPRM
>21103076903	1	2	35	BHRKST
>21103076903	1	2	36	RISPRM
>21103076903	1	2	37	VSCPRM
>21103076903	1	2	38	AKPKST
>21103076903	1	2	38	APRV
>21103076903	1	2	38	BNSPRV
>21103076903	1	2	38	INCKST
>21103076903	1	2	38	INCPRV
>21103076903	1	2	38	ISOP
>21103076903	1	2	38	PLSOP
>21103076903	1	2	38	1STKST
>
>As you can see the set of records where vlgn_mut = 34 has been deleted. This set of records I want have.
>
>How could i do this?
>
>Thanks beforehand
Edward Pikman
Independent Consultant
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform