Integrated monitoring with 2005 and earlier isn't that sophisticated. You could build your own process to do this. SQL Server 2008 has a monitoring mechanism that is much more sophisticated....

Based on a meeting earlier this week, a significant part of our developers consider database access the mostly costly and least productive part of their work. They're skipping LINQ and...

Chirag (9/19/2008)

---

GilaMonster (9/18/2008)

---

Chirag (9/18/2008)

---

another way is to right click on the proc in SSMS and select view dependencies. It will show all objects that depend on the proc and...

Yes, that's it. Jeremy Brown described it well above.

My take. The optimizer doesn't decide on parallelism or not, it's the query engine. Any given query can have two execution...

You may also want to change the parallelism threshold. I've always found the default, 5, to be way too low. I've usually bumped it up to somewhere between 20 and...

Time to do a point in time recovery, if you can. If not, get a log browsing tool.

There's an introduction to exactly this here[/url].

There are a lot of drill down points you can make from there, but it generally covers the basics.

Cool. Keep an eye on it though. We eliminated recompiles using this method, but, if I recall correctly, we were seeing a few more scans and a few less seeks.

Single user mode will take the first connection that comes along.

We usually try to set servers to restricted user mode. That way, only people with admin privileges can connect.

You...

One way you can do this, and it's a bit problematic let me say up front, is to do something like this (p-code):

WHERE... 1 = CASE WHEN (ColA IS NULL)...

Too true. You're right. I keep forgetting those things are in there.

To determine what's happening with the system, yes, you use Perfomance Monitor. For a detailed look inside the databases, to get individual query performance and behavior, then you use a...

Or, write all your code in a syntax checking tool like Visual Studio Team System Database Edition. I can't even save a script with bad syntax without getting an alert...

Yet another option is to look at the execution plans. sys.dm_exec_cached_plans has a column usecounts that shows how many times a plan has been used. This won't be perfect because...

And do a search on the site here. There are a bunch of useful articles and scripts on this topic.