There are a lot of different metrics that will tell you about memory. Many of them are available in Performance Monitor. Just go to the memory section, both on the...

The statement completed events, sp_statement_completed or sql_statement_completed. You'll just need to ensure you put a filter in place to ensure you're looking at the right data. Otherwise you'll collect way...

PearlJammer1 (5/14/2013)

---

Grant,

The query with the largest numbers against it is the second one in the list:

INSERT INTO @MemStat

EXEC ('DBCC memorystatus() WITH tableresults');

From query plan: 0x06000100e090292b40e18282000000000000000000000000

*****************************************************************

Thje metrics are:

execution...

PearlJammer1 (5/14/2013)

---

Hello again Grant

Heres what i am finding.

The alert for hash warnings is showing up against server 15 and in the Master database.

I click on 'overview', then my server (server15),...

Tempdb growth has to be because of tempdb use. There's nothing in the OS that's going to affect tempdb. It's not just temp tables. It's also any sort operations, index...

SQL is the original defined language and is maintained by ISO. Transact-SQL (T-SQL) is the name that Sybase gave to their version of the language and since SQL Server is...

You can use extended events to watch for the truncate statement. That's how I'd do it.

You want someone to give you their entire hand-built monitoring system?

For the SQL Server related counters you can just look at sys.dm_os_performance_counters. That will let you run queries to bring...

And remember, the missing index information, as is, doesn't relate directly to any query at all. So simply taking that stuff as written, you might be creating an index for...

When you select the time in the past, it changes the screen as you see. Next, you can click on the instance inside the server. If you do that, at...

Not a problem. Happy to help.

You could turn on profiler or, better still, extended events to capture the query executions that are occurring. But, there's a way to look at what was going on at...

Ha!

Well developers have their cross to bear as well as us. I get it. Entirely. However, I'm pretty sure, based on the info provided, that's where the problem lies.

A bunch of things going on with this one. First off, you're joining on views, which presumably have multiple tables joining together within them. That would reflect in the high...

Generally, but not always, instead of IN I would be doing a JOIN. The optimizer might interpret it that way any for you. Since you're going for matching records that...