[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 144
  • Last Modified:

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,signal1,equity1,drawdown1,signal2,equity2,drawdown2,etc

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,signal1,equity1,drawdown1

2. or, 1 table which will hold all data?

Regards,
Dennis

regards,
Dennis
0
Schuttend
Asked:
Schuttend
  • 3
  • 3
1 Solution
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
your description is not clear enough to me to comment... could you maybe describe a bit more, with data samples?
0
 
SchuttendAuthor Commented:
Please find example file attached. Only equity field and drawdown fields are missing....

Regards,
Dennis
Example.txt
0
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
that's the data sample... now could you maybe describe a bit more, what that data is about?
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
SchuttendAuthor Commented:
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
0
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
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...
0
 
3_SCommented:
If I look at the file every line could represent on record in a table.  You could add on field in the record to point to the file it was from.
I would prefer that than have every field in a seperate table.  I you need corresponding value from on line you would have to do tremendous effort with multiple joins to recreate on line of the file.
0
 
SchuttendAuthor Commented:
Thank you...
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now