The query looks ok, so I'd focus on the data and your index density. Here's a blog post I wrote about it. I found that determining if you're looking at...

I don't have an example query handy, but you can also try using the BUFFER and determining if points are within the buffer. That works well for some types of...

You just posted this in the 7, 2000 forum. Most people reading here are unlikely to be doing spatial queries since they don't exist until 2008.

The query looks ok, so...

Honest answer here, if I had to do that, I'd use the command-line utility built into SQL Compare from Red Gate. It's the easiest way I know to make this...

billo (4/27/2012)

---

I appreciate all the help! I'll be going through a couple of those resources to start working through and see where I can increase our efficiency. I...

Or, for that matter, check out Jonathan Kehayias' & Ted Krueger's book. It's a free download.

GilaMonster (4/27/2012)

---

Grant Fritchey (4/27/2012)

---

Focusing on nothin but reads, 23 is worse than 15. But as Gail says, this is a trivial difference. I'd only get worked up if this query...

Is is possible that the issue is not SQL Server? No blocking, low cpu, normal memory, low disk... It sure sounds like SQL Server might be OK (except for the...

Deadlocks aren't going to be the problem. It's blocking that you need to look for. The process that is blocking others is likely to be the issue.

Also, look at the...

Focusing on nothin but reads, 23 is worse than 15. But as Gail says, this is a trivial difference. I'd only get worked up if this query were called hundreds...

Just remember that this is only going to show the executions since the last time a given query was loaded into cache. Recompiles or aging out of cache will change...

I'm not so sure I'd use a trigger. Those things are notorious performance and maintenance headaches.

What about using the OUTPUT clause. You can output the IDs generated from an INSERT...

Just a different technology set. Go for it.

And, if there isn't a MySqlServerCentral, you get to go and create it. Although you might want to change the name.

Data growth? Additional resource use leading to contention? Do you have memory, cpu & IO tracking over the same two time periods to compare how the whole system was behaving?

There's no need for proof. It's right there in the SQL Server documentation as provided by Microsoft, the people who wrote the software.