I wouldn't focus too much on the buffer hit ratio it is very subjective to the nature of the application you have working on the db. And the usage patterns...

Chris,

Shouldn't serializable be used even with your query since it is possible for two person to run the query at the exact same time and still get the same record...

a search form with the columns for filtering would do.

In the SQL, you can do some logic such as

SELECT TOP 10 * FROM table

WHERE

@col1 IS NULL OR @col1 =...

it would be helpful if you actually showed the stored procedure and the table structure.

Also how you called it from query analyzer.

What do you mean by

"No the indexing is all properly given.

I want to know, an alternative function or something like that ,instead of MAX()"

Additional index can and should be...

what you want should be better accomplished by using DTS if it's not a one off thing. Using it you can do several tasks in parallel or sequence them.

However if...

Hi all,

I meant exactly what i wrote

Where

(@SearchCol='SurName' and A.strSurname like @strFirstLetter)

or

(@SearchCol='FirstName' and A.strFirstname like @strFirstLetter )

This way, the db can make...

better yet, the where order should be changed to:

Where

(@SearchCol='SurName' and A.strSurname like @strFirstLetter)

or

(@SearchCol='FirstName' and A.strFirstname like @strFirstLetter )

This way, the db can make better use of short circuiting,...

instead of

Where

(SubString(A.strSurname,1,1) = @strFirstLetter and @SearchCol = 'SurName')

or

(SubString(A.strFirstname,1,1) = @strFirstLetter and @SearchCol = 'FirstName')

I would first replace append a '%' to the @strFirstLetter then write:

Where

(A.strSurname like @strFirstLetter and @SearchCol='SurName')

or...

Possible reason is that in t-sql your query is using literals, so the optimizer chosed the correct plan.

With stored procedures you are passing the values in, so the optimizer might...

Based on the requirements I would have a single table.

Index on barcode. Another index on timestamp.

Consider having a purging/archiving mechanism to move the old data entirely out of the database....

Based on the requirements I would have a single table.

Index on barcode. Another index on timestamp.

Consider having a purging/archiving mechanism to move the old data entirely out of the database....

Based on the requirements I would have a single table.

Index on barcode. Another index on timestamp.

Consider having a purging/archiving mechanism to move the old data entirely out of the database....

hi folks,

The post above gives an example why partitioning isn't a good idea, when you have a unique indexable column for your queries.

Partitioning = 2 + 3 + 2 +...

hi folks,

The post above gives an example why partitioning isn't a good idea, when you have a unique indexable column for your queries.

Partitioning = 2 + 3 + 2 +...