I have several issues with GUID's as clustered indexes. First, they're very wide. This means fewer per page and more pages per index, making them somewhat less efficient. That's a...

I don't think Gail and I are in disagreement here. You need a clustered index on these tables, however, a primary key of GUID is not the best choice, and...

nabajyoti.b (3/19/2009)

---

i have table table1 with two columns col1,col2

my statement is insert table1 values('dummy',xyz)

where xyz is a variable and i want to put some values in a loop for...

RBarryYoung (3/18/2009)

---

Bruce W Cassidy (3/18/2009)

---

[font="Verdana"]Ah, anger management...

As a suggestion, go buy a collection of soft, squishy balls. Not only can you play with them as stress relievers, but you...

Support cycles being what they are, if I were upgrading today (and I am), I'd be going for 2008, not 2005. At this point, it's four years into the 2005...

Compatibility mode is so that older or deprecated code continues to work on the new server, not so you can move backwards. Once it's formatted on the 2008 system, it's...

Unless, by chance, you're using the ordered GUID. It still fragments, but not as much.

Right there with you. I finally developed enough arm & shoulder strength to graduate to the 10lb sledge. Makes a HUGE difference. As you say, it'll fix or replace anything.

You don't need to cluster on the PK. Generally, the best place for the cluster is on the most frequently used access path. More often than not, this is the...

Matt (3/18/2009)

---

GilaMonster (3/18/2009)

---

No. If there's a lock on the messages table it will just affect queries on the messages table. If there's a lock on a portion of the messages...

Nah, blocking can be very isolated. It might be a particular page on the table that's slowing stuff down.

Matt (3/18/2009)

---

The annoying thing is that at the time of posting on this forum the query runs in less than a second, it's only at certain periods throughout the day...

Then it's going to be...

First, just a word of caution, NOLOCK can lead to bad data. I don't just mean the ubiquitous "dirty read" meaning uncommitted changes, but I mean, extra rows, missing rows......

Just a note of caution, running the Profiler gui on a production system can be very problematic[/url]. Best practice is to use a server-side trace to gather the data and...