February 25, 2003 at 8:18 am
Preview
I have 2 tables that are joined on 80% of my queries. One is an employees table and the other is a dailyactivity table.
THe employees table is 98% of the time (except for logins) aliased into 3 tables. I made 3 views from the employees table to ease the queries.
I am now wondering if it makes since to create another view to eliminate this on most of my queries..
FROM dailyactivity INNER JOIN technicians ON
dailyactivity.cuid = technicians.cuid
INNER JOIN nm_mgr ON technicians.nm_rc = nm_mgr.nm_rc
INNER JOIN nm_mgr am_mgr ON nm_mgr.am_rc = am_mgr.nm_rc
While making in a view with the often requested information will be easier to write the queries, will it hamper performance any? The dailyactivity table currently has 265000 records, with an average of a thousand added daily. The employees table has 1800 records. I have read here befor ethat views are good and can be used for this type of application, but I am wondering if this stuation would be one that it's "worth" it.
Thanks
February 25, 2003 at 10:01 am
I think its a good idea and I dont think it will hurt performance any.
Andy
February 25, 2003 at 1:22 pm
Shouldn't affect anything, but will be easier to read. (and type)
Steve Jones
February 27, 2003 at 12:22 pm
Sounds like a plan, thanks a lot.
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply