Take a look at UNPIVOT operator in BOL.

http://msdn2.microsoft.com/en-us/library/ms141723.aspx

http://msdn2.microsoft.com/en-us/library/ms177410.aspx

If linked server is not on a fast connection, it's the latency that makes it slow - each insert waits for reply. So, you can insert data to a local...

Right, but Steve once mentioned that QoD is not about best practices. Some are about bad practice, probably to spark discussions like this, which is OK for me.

If the solution...

select sum(salary*age)/sum(age)

Good editorial. Jeff, well worded rules, they remind me of 3 rules of robotics. 🙂

Most of customer requests break the first rule. Then there are poorly thought requests that introduce...

kevriley (4/15/2008)

---

There is always 101 ways to do anything in t-sql - the trick (or more specifically, the skill) is knowing which is the right way:D

That's one of the attributes...

They're truncated visually as it sizes column based on data size. You can always enlarge the column to see full column names.

I don't think there is much sense putting such code into trigger, as it unnecessarily complicates logic. It's the duty of client to send a correct update/insert/delete statement containing only...

My apologies, Paul.

It indeed wasn't harsh.

I first read this:

That would be a bit useful if they were on SS2000, but they're not. Please check which forum you're in before posting...

If you rebuild clustered index explicitly with ALTER, you have to rebuild other indexes too.

DBReindex rebuilds them all, in SSMS just run:

DBCC DBReindex ('[database.]schema.table')

Of course. I stated that what Paul wrote is correct, just that there's no need to be harsh. Most of things from ss2k work fine on ss2005, though some should...

Is there anyway to build a SQL Update that can test the fields during the update and not update them if they are the same, but still update fields that...

Ouch, your second harsh post on this topic. While it is true, proper directions are far more relevant than exact steps. If you always provide exact steps to solve the...

Backup with truncate_only restarts the log file, but does not shrink it.

Huge log file means there are huge table transactions and/or transactions over huge blobs. So the source of problem...

KB (4/9/2008)

---

Clustered index created on an ID (int) column on a table shows Logical Scan Fragmentation = 92.86% (I ran DBCC showcontig for the table). This column is also the...