Lowell (11/4/2010)

---

maybe he was doing a select * from BillionRowTable so he could see the column names, and the error threw him off.

He may not be familiar with sp_help [TableName]...

I don't think so. I looked at the users previous posts (click on the user, select "Find all member's posts")...

raistlinx (11/3/2010)Depending on what kind of a RAID environment you may be working in (often beyond your control) it can take a lot longer than that. So let's suppose...

raistlinx (11/3/2010)

Because of the time it takes to create a new clean DB. Often times in developement you may want to clean out the tables quickly to have a fresh...

HoustonFirefox (11/1/2010)

---

As I've been mostly involved with DB2, Sybase, mySQL and SQL Server 2000 over the last several years, I'm just now getting back into SQL Server 2005.

.....

Why can't...

Probably SQL is using a cached query plan. Try doing a DBBC DROPCLEANBUFFERS.

Note that this may impact performance while new query plans are built and cached. You can get the...

I would almost never use DB Snapshots for reporting, there are a lot of better options and a lot of restictrions with snapshots.

Far better to use replication. This allows you...

How often are you doing this and...

This doesn't make sense, if you put a filter on the table and select the...

The execution plan won't return any user data, at most it will return some tables and index info.

Also seeing the code for the underlying view makes a big difference. They...

sqldba_icon (10/19/2010)

---

pavan_srirangam (10/19/2010)

---

same results no improvement. It is retrieving from a view and it was working fine until yesterday..

Run both queries and include exec plans and see you will find...

Nullable columns can cause problems for queries like this. NULL is an undefined value, think of it as "noise". This means SQL can't do an EQUALS test on it. To...

premkuttan.lakshmanan (10/19/2010)

---

My tempdb raised to 25 GB since i was executing a query but even after execution of the query the size of tempdb remains same can anyone help...

As per the clustering key width, it would be 17 bytes instead of 8, it's not that bad (is it?).

..

Also, the table is partitioned (6 partitions) on Receiving_Number, but just...

Unless the user suspects you are tracing them and runs:

SELECT * FROM :: fn_trace_getinfo(0)

and then runs:

SELECT * FROM :: fn_trace_getfilterinfo (trace_id),

They won't see the trace.

You could block their execute rights...