Schuttend
asked on
20.000 tables or 20.000 fields?
Hello,
I have data in the following format which needs to be place in an access database.
date,open,high,low,close,s
I have about 20.000 or more signal values and multiple dates. What is better to do if I need to recall data later from the database:
1. create 1 table per signal? Like date,open,high,low,close,s
2. or, 1 table which will hold all data?
Regards,
Dennis
regards,
Dennis
I have data in the following format which needs to be place in an access database.
date,open,high,low,close,s
I have about 20.000 or more signal values and multiple dates. What is better to do if I need to recall data later from the database:
1. create 1 table per signal? Like date,open,high,low,close,s
2. or, 1 table which will hold all data?
Regards,
Dennis
regards,
Dennis
![Avatar of Guy Hengel [angelIII / a3]](https://filedb.experts-exchange.com/files/public/2013/11/25/ddbe0ea6-aa6e-4279-b781-57b735dd3ea0.jpeg){kind=small}
Guy Hengel [angelIII / a3]
your description is not clear enough to me to comment... could you maybe describe a bit more, with data samples?
ASKER
Please find example file attached. Only equity field and drawdown fields are missing....
Regards,
Dennis
Example.txt
Regards,
Dennis
Example.txt
that's the data sample... now could you maybe describe a bit more, what that data is about?
ASKER
data is financial data. The close price is the traded instrument (sp500) . The signals are tradingsignals.
Signal > 0 means buy next day. Signal < 0 means sell next day. Each field with a signal is a different trading system. Following the signal will generate equity. I have 20.000 different tradingsignals divided over 200 csv files. I need to collect them in 1 database to performing further calculation on it and also display graphs of generated equity etc
Signal > 0 means buy next day. Signal < 0 means sell next day. Each field with a signal is a different trading system. Following the signal will generate equity. I have 20.000 different tradingsignals divided over 200 csv files. I need to collect them in 1 database to performing further calculation on it and also display graphs of generated equity etc
I think you should go the following way:
have the table with the values as you have them per file, and add 1 more column to the table, indicating the file the data comes from (it might be the filename itself, or a foreign key value pointing to a table that holds the file names itself), and /or some more relevant data "per file" ...
still the data makes close to no sense to me, basically because I cannot really categorize it, as I was never confronted with trading data...
have the table with the values as you have them per file, and add 1 more column to the table, indicating the file the data comes from (it might be the filename itself, or a foreign key value pointing to a table that holds the file names itself), and /or some more relevant data "per file" ...
still the data makes close to no sense to me, basically because I cannot really categorize it, as I was never confronted with trading data...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you...