I don't quite get the question either. If you read the foreign key constraint, it's going to tell you which table is constraining. From there you can either simply select...

Whatever this job is, I hope it's not too intrusive to the system since it sounds like it's going to be running 24/7. If you're inserting or updating data all...

I don't know. That sounds... almost... on topic. :hehe:

Kendal Van Dyke (3/27/2009)

---

I think it's a bit harsh and perhaps even a bit academic to say never ever run profiler against a production server. Yes, it can create problems...

You can create clustered and nonclustered indexes on temp tables.

Syntax is like this:

CREATE INDEX myindexname ON schemaname.tablename(col1,col2)

INCLUDE (col3)

WITH FILLFACTOR=80

ON Primary

That creates an index consisting of two columns which includes...

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...