Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
We are on the same page...
I have created a DB with 3 tables and I will run a test for a couple days / weeks to see what this gives
I can already see the first quotes rolling live into my DB
Can you help answer these questions from other members on NexusFi?
It made the most sense to have the table name be the ticker. In my case, I am capturing >5000 tickers, so some of them are reserved words like KEY and some contain special characters like TICK.Z. So be sure you are using proper backtick syntax.
Anyway, one database for daily, minute, ticks, and l2 made the most sense for me, so I could keep the table name uniform across all of it.
And I definitely think you should have one table per symbol.
My comments are based on large data collection. If you are only doing it for a handful of symbols, or only for a few million records, then anything would work. I am dealing with massive amounts of data --- my server holds many times more tick data than IQFeed's does, for example. And I have it for ALL tickers (US).
