Yes. Its a small table.  Question is , when there is 0 rows in the table, and when we say SELECT * FROM <Tname> , why SQL Server is...

So, yeah, about what I expected. A clustered index scan and nothing else.

So, your #1 problem query is SELECT * from a table with two rows in it?

Dude, go home....

but... why? Two rows or sometimes empty? Honestly,...

I'm afraid I don't understand. What's that? It's a picture of some data from a query running SELECT * returning 2 rows. I'm confused.

What do the execution plans look like? What do the queries look like. There's not a 'run faster' switch that can be flipped here. Without some understanding of the behaviors...

Not if it's just processing all the validations, scanning tables looking...

I read through the interview questions at the link, and yeah, I'd say those are somewhat tough questions. I've been doing this for 30+ years. I've written a few books....

Nope. But I am in Austin for SQL Saturday here.

Just wanted to say thanks on this again, Grant. Work has given me the green light for SQLBits; it's a bit (no pun intended) last minute though so all...

Also, salaries are very regional. A DBA in Tulsa probably isn't paid what a DBA in NYC is paid (honestly, they should be, but they aren't). This isn't specific to...

Exactly that, or, have a second job scheduled two hours after the one that starts it.

So catching up and getting back into the forums here...

Saw the talk about the SQL conferences and this may be the first year I go to PASS Summit!  When...

Always a fan of "whatever works". Glad you found a solution.

Full text indexes are an option. Although, in all honesty, I hate 'em. Hard to maintain and frequently don't actually speed things up much, if at all. Extra storage. Ugh....

Trying to get different perspectives! May be I am looking at the things might not be the right. Getting awareness from wise people will definitely make me think with...