Reply to thread

On reading through this and noting Kiers comments, the 'time saved vs is it worth it' is something that a lot of people get wrong no matter what database it is in. I work daily with sql server and see some of the other developers making the same mistakes. Not only do they spend time doing something that will save an unnoticable amount of time, they also neglect the areas where they should be spending the time such as writing efficient queries, correct use of indexing, and indeed the setup of the database engine itself. Things that should be at the forefront of any development. Although I do a fair amount of .NET development nowadays I started with database development and its amazing how many really efficient vb.net/C#/PHP/etc programmers cant get their programs to run well because of a badly thought of database.


Back
Top Bottom