Hi,
We have a large table and several fields are indexed. We also created a field called 'timestamp' used by the SQL database to refernce its indexing process.
We created a 'timestamp' field after the table had been already populated with a large volume of data.
Because I set the database to do an incremental indexing every hour and my web application is very slow on performing the db searches it leads me to the conclusion that the SQL server does not use the 'timestamp' correctly and/or the fields that already existed in the database when I added the 'timestamp' field have still got null vallues.
Is this the case? And if so what technique do you advise for putting in values for this timestamp field.
We have a large table and several fields are indexed. We also created a field called 'timestamp' used by the SQL database to refernce its indexing process.
We created a 'timestamp' field after the table had been already populated with a large volume of data.
Because I set the database to do an incremental indexing every hour and my web application is very slow on performing the db searches it leads me to the conclusion that the SQL server does not use the 'timestamp' correctly and/or the fields that already existed in the database when I added the 'timestamp' field have still got null vallues.
Is this the case? And if so what technique do you advise for putting in values for this timestamp field.