Hey all,
I have a shop locator and here are the tables in it.
Is this a good SQL DB schema? It just seems like in order to pull up a shop, I need to make so many calls (I pull the shop, then I gotta pull the city ID, then, from that, I gotta pull the state ID for EVERY record.)
Is there any way this could be optimized? Should I optimize it into one table with all the info for every shop on each line? If so, any recommendations to quickly do this?
Thanks!
Oops, heres the image
I have a shop locator and here are the tables in it.
Is this a good SQL DB schema? It just seems like in order to pull up a shop, I need to make so many calls (I pull the shop, then I gotta pull the city ID, then, from that, I gotta pull the state ID for EVERY record.)
Is there any way this could be optimized? Should I optimize it into one table with all the info for every shop on each line? If so, any recommendations to quickly do this?
Thanks!
Oops, heres the image
