It takes 3 minutes to run BUT if I remove the ‘option (LOOP JOIN)’ is completes in 20 seconds, what is happening what is ‘option (LOOP JOIN)’? Is obsolete if...

I recommend you be VERY careful about using either. They both will do HORRIBLE things to your database performance, size and concurrency by creating too many indexes and...

Here's my standard...

http://www.sqlservercentral.com/About/WriteForUs/

Or you can send a PM to Jeff Moden or Steve Jones.

Marios, could I trouble you for the table definitions for your system as well as the rdl for the report(s) you have? Looks like some very useful stuff I...

john j serna (7/25/2008)

---

Hi, I don't know if you understand what i tried to say, but if your tempdb database is too big, you want to reduce it's size, so,...

This is bad advice.

That is worse advice. :w00t:

1) What was the fill factor used for the PK?

2)...

hari255 (7/22/2008)

---

i want to design the database with a requirement of 20gb of data per hour like that the data will grow upto terabytes, so how do i design...

After tinkering with indexes in our test system, I wasn't seeing a huge performance increase whether I used standard rule-of-thumb indexing or even created indexes I thought would be appropriate,...

Still looks to be rife with problems, but I will let them pass. 🙂 If this type of system has worked reliably for you in the past good...

smunson (7/23/2008)

---

Sounds to me like an exam question or homework. Otherwise why ask for 2 different answers. I would suggest that the OP read their...

1) If users don't need to join this output to other tables, then make it a stored procedure that they call.

2) WHERE DATEDIFF(day, RL.TS_ID, @@dt1 ) <0

...

IMHO, last wait type is not nearly so useful as trending all waittypes over time. Search microsoft.com for a word document on SQL Server 2005 Waits and Queues.

That would be nice, but a significant departure from what I got just a few months ago which was late 4th quarter. They weren't going to really start working...