I have 11 tables to deal with, these tables have relations, Primary Keys and Foriegn Keys. the architeched of the application that uses the SQL allowed to visit the SQL server only once, to minimize the trips back and forth to the server. What would be the best approach, shall I load 11 tables in memory sapartly or create a View and then call that view, less tables to work with, Or Stored Procedure that calls all the tables all put them all in momery.
Not sure what would be the best approach, We would be retreiving information from these tables only. There will not be update or Altering to the tables.
The Tables are small, the biggest table about 50 rows. The client requested The architect to be done that way where we design our code to have one trip to the SQL server and load everything in memory and work with tables from Memory.
Your client doesn't have programming or database experience, it sounds like at least.
Just do a select * for each table you need and put that into memory on the app server. You don't need to use views or anything really. And yes separately is fine. You can't use one view for this as that would be one gigantic result set and probably isn't right.
Multiple Tables Views
Posted - 03/13/2012 : 12:10:39
