Jack Corbett (10/21/2011)

---

Steve Jones - SSC Editor (10/21/2011)

---

Jack Corbett (10/20/2011)

---

On a more serious note, I'd like to put together a new presentation, but I'm a bit short on ideas. ...

Throw out an old one and...

If it's not turned on already, turn on optimizer for ad hoc workload.

Next, news to me, but worth mentioning, NUMA (which most systems have these days) makes the normal page...

Piling on at this point, but nope. Not a chance. the DMO objects store either real time information or aggregation information. They couldn't store historical information without the system databases...

You'd need to get into querying against the DMOs. sys.dm_exec_query_stats will have it.

Ian Massi (10/20/2011)

---

The website for Space Adventures has a video that shows them testing the rocket they would use. Really impressive and seems to work well. That being...

Phil Parkin (10/20/2011)

---

Grant Fritchey (10/20/2011)

---

What about building a drug name mapping table. You run through the data once, nightly, after a load, something, and map the names supplied to the...

Entirely possible.

Here's the appropriate entry from the BOL

ditto

Do they all have the same query_plan_hash value?

Sounds like you might be a candidate for Optimize for Ad Hoc workloads, but it's hard to be sure.

Do you mean every single action taken by the users for a week? You'll need to capture all events. I'd suggest looking up how to use extended events for that,...

Just search Michelle's site a bit. You'll find this[/url].

I've only seen one execution plan posted. It had a table scan, which means no cluster, and was predicated as follows:

[SFDReports].[Sales].[HOWLI_LOAD].[SQL_POST_DATE]>=N'2011-10-15 00:00:00.000' AND [SFDReports].[Sales].[HOWLI_LOAD].[SQL_POST_DATE]<=N'2011-10-19 00:00:00.000'

Based on what I'm seeing here,...

You also have to take into account what happens with the transaction log. When you delete 1000 rows, they're recorded in the log that way, increasing the amount of information...

Hyperbac is a file filter. It doesn't interfere in any way with the operation of SQL Server. Instead it gets between SQL Server and the file system and runs interference...