NauticalGent
Ignore List Poster Boy
- Local time
- Yesterday, 20:37
- Joined
- Apr 27, 2015
- Messages
- 6,635
Lager? Pils? Ale?
Ale, California Ale. I try to support my state when I can, it's pretty good if you could get your hands on oneLager? Pils? Ale?
Weather is the short answer, the vibe is part of it. I've been in So Cal my entire life, nothing compares at any price.How is it a conservative like you can live in California??
Thanks for the help. Actually the entire video is of the same these, about index and its impact of performance.Sorry, don't have time to trawl through 45 minutes of video. If you want a specific comment, please provide the time in the video where the author makes this assertion.
Certainly indexing can slow the bulk insert and update of records since the indexes need to be updated as well. But manual entry of data will not be noticeably affected. There are ways to overcome this which may or may not have been mentioned by the author.
However that small time cost of inserting/updating records is more than outweighed by the time saved when retrieving data.
see this link on why indexing is important
Why indexing is important for good performance
Indexing is essential for the efficient retrieval of data from a db. Some may be concerned about the additional disk space required for the index(es) - but disk space is cheap and they do not take up that much space. For small db's - a few '000 records per table and simple queries it is...www.access-programmers.co.uk
The concern appears to be "indexing":I CAN move posts, but I'm not sure WHERE to move THIS post. Does anyone have a suggestion as to where it belongs?
Given that, perhaps the sub-forum "Theory and practice of database design" would be the most appropriate place to discuss the theory and practices of "indexing" in designing a database.the author says, indexing can impact performance in negative way
suspension-of-disbelief things like people with special superpowers