Soonish. 1st draft is done, but my tech editor, Brad McGehee, has probably painted it red with comments & suggestions. I think we're shooting for publishing before the PASS Summit....

Then you're probably running this against a 2000 database as Gail already pointed out. You can't do this with 2000.

But if you're in 2005 or above you can right click on the plan and select "Save As"

Tuning queries is a huge topic. If you start with...

Ninja's_RGR'us (5/23/2011)

---

there's no magic bullet for any global tuning process... always takes...

There have been entire books written on the topic of Execution Plan Operators.

For one example, look in my signature line.

You're seeing the difference between dynamic tsql and prepared statements. You'd see the same thing if you put the code into a stored procedure instead of building the TSQL statement.

Run...

It's fairly rare to need to do a FULL SCAN on all your stats. It's probably only a few tables that really need that. Unfortunately those are usually the larger...

If you know for sure which queries are slow, take a look at the execution plans and see what they're doing. Tune the queries. If you're not sure which queries...

Best bet, take a look at the execution plan. You'll see what is being done by SQL Server to retrieve the data as defined by the CTE and the query...

Way too accurate.

jasonshaw (5/23/2011)

---

Thank you for your ideas.

GUID is a new concept to me and I am not sure that I works in this case as it is not good for indexing...

Q: Ever heard of nHibernate?

A: Yes

Q: Next candidate!

Those are decent questions, but they lean a bit heavily towards database development and little away from straight-up development. You might want...

Thanks. Glad to hear that stuff is useful. That's the goal.

I've seen designs like this in the past and they lead to serious bottlenecks. I'm with Gus. If you have to do this a GUID is your best bet.

But, be...