June 19, 2003 at 12:53 pm
I would like to understand the reasons why some people say that it is better to define how a table is read in code (say within a VB application) rather than letting the RDBMS determine which index to use. Surely this is not true when you don't know what questions the end-user is going to ask (when writing ad-hoc queries for example)?
Can anyone offer an idiot's guide response to this please? Thanks
June 19, 2003 at 1:36 pm
Not quite sure what you are referring to with :how a table is read in code". Do you mean table/index hints? or the ADODB.Connection/Command objects' inherent CursorType, CursorLocation type properties? Or do you mean the different ways of actually retrieving the data (in VB, Connection.Execute, Implicit vs. Explicit Commands, Recordset.Open, etc...) (in .NET DataReader vs. DataSet, etc)?
Clearly, there are many different options to discuss here. Could you narrow it down some?
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply