NO!

Never run the Profiler gui against Production.

It uses a completely different mechanism for gathering the data to present from what the server-side trace uses. This mechanism can, and will,...

I meant the data access layer, regardless of how it's displayed....

suhasini.m (3/27/2009)

---

Thanks for the detailed reply.

I am running both the quries at the same time and also doing DBCC DROPCLEANBUFFER and DBCC CLEARPROCCACHE before for both the queries.

If this is...

It really depends on what you need to do. Let's assume a row into each table. You create a proc with variables for each of the columns, except the two...

CTRL+2 in a query runs sp_who by default. You can change that.

It sounds like you were hitting CTRL+2 to open a table? I've never seen that done before. If you...

They add to the overhead. I use them occasionally when debugging, but always comment them out.

However, I've never tested them to see what the exact cost is.

You can get...

Jeff should do it.

"Pork Chops for the DBA" by Jeff Moden

"SQL Server Performance Tuning by Pork Choping Deveopers" by Jeff Moden

"Better Performance by True Set Based Operations and Pork Chops"...

suhasini.m (3/27/2009)

---

I have 2 queries

SELECT * FROM Table1

JOIN Table2

ON Table1.Column1 = Table2.Column1

SELECT * FROM Table1

JOIN Table2

ON Table1.Column1 = Table2.Column1

AND Table1.Column2 = XXX

Both these query returns same number of results say...

Yes, they are very handy, aren't they?

Just a side note, it's almost always a last resort to start applying blocking through hints. SQL Server is generally much more capable at handling it's locking and blocking processes...

mazzz (3/27/2009)

---

Thanks Grant

So the order in which I'd reorg indexes would not be important then, I expect?

The tables are reasonably small (generally under 20000 rows), so I'm going to monitor...

I'd dig into the performance monitor counters, cpu, I/O, etc. Especially focus on the waits and queues to see what things are slowing down for on the server. Here's an...

That's a very broad topic. Here are a few of my personal pointers

1) Pick the clustered index first and pick it carefully

2) Keep the clustered index as narrow as practical...

You have 4gb of memory on a production box running both SQL Server 2000 and SQL SErver 2005? I'd be willing to bet you're seeing serious memory pressure and probably...

What made you choose those 12 fields? Were you working from a query plan or missing index information or recommendations from the Tuning Advisor?

You need to look at the execution...