You'd have to search each database on the server. You can look for the table name in the system view INFORMATION_SCHEMA.Tables.

Or, you could go to Red Gate Software and get...

Using the sys.dm_exec_query_stats DMV, all you can do is what you've done. Take the average and split it up by execution count. If you want a precise measure, you'll need...

I'd prefer querying the information schema too, but there is always sp_help

EXEC sys.sp_help 'sales.salesorderheader'

To a very large degree, a query is a query. As Gail says, it will be the same. The main thing would be how the query is put together. Let's...

ramana3327 (1/19/2014)

Thanks to everyone.

I read that update is faster. Why because already table space is fixed, and you are just changing the value but for the insertion it...

Availability Groups are not in any way like clustering. You're defining various systems that share no hardware at all to belong to an Availability Group. Then, you can define a...

I'm right there with Gail. Not seeing the code, there's just not enough to go on. Heck, you may have just had contention the first time you ran the query.

sys.dm_exec_requests is my bestest buddy in the whole world. It's my go to position for this type of scenario. Assuming no long running query or blocking scenario, I might expand...

Further, it's completely dependent on a number of factors that you haven't outlined. You're not comparing apples to apples in this question.

Remember, while it has the word "table" in the definition of Common Table Expression, a CTE is nothing but a query. It's not a table. Comparing it to a temp...

Sure. You can. I'd be cautious about adding unique indexes because if you don't have a matching constraint on the other side, you could get incorrect data input and then......

Jeff has already addressed question 1. On question 2, yeah, most tables ought to have a clustered index. Much of SQL Server's storage and retrieval optimizations are built around the...

There are basically two good ways to get query metrics out of the system. You can query the cache and see what's there for query performance, or you can audit...

Yeah, just run a query on the server that uses RAISEERROR and the appropriate error level. Nothing else needed. It won't hurt the server or any processes on the server.

Any login can have a query that causes blocking. That's just how SQL Server works. Based on what you've described, that's about all I can see. To minimize blocking, go...