Could also be long-running transactions, snapshot or RCSI isolation level use, many concurrent queries doing large hashs and/or sorts, suboptimal indexing, crappy queries, huge/bad cursors, etc.

bantrim (1/11/2015)

---

TheSQLGuru (1/11/2015)

---

Most of my healthcare work has been directly for services providers or insurers, although I have worked directly with Centricity and a few others, especially on data movement...

bantrim (1/11/2015)

---

Jeff Moden (1/11/2015)

---

Ah... understood on the OR.

I'm thinking that a UNIQUE NIX on the ID and Hash (and that combination should be unique because the ID is unique) might...

Your statement of the problem, even with a second posting, isn't making sense to me, especially given the data you have provided. I/we need one more thing: expected...

Not true Jeff. You can absolutely receive...

Markus (1/12/2015)

---

Just because there is 30gig of free space doesn't mean that that 30 gig is at the end of the file. The data can be spread all over...

Depending on what they are doing you could perhaps store...

Most of my healthcare work has been directly for services providers or insurers, although I have worked directly with Centricity and a few others, especially on data movement stuff. ...

This is the dreaded IS NULL OR scenario (with paging thrown in for good measure). Best solution BY FAR is dynamic SQL. It could also possibly benefit from...

1) you REALLY need to read Thomas Kejser's blog post on hashing in SQL Server: http://kejser.org/exploring-hash-functions-in-sql-server/. I believe he has others.

2) I have used what you are doing for...

Why in the world are you worried about 10GB on a 170GB file?!? Leave it and move on - I GUARANTEE you that you have MANY more things to...

Please start a new thread. This one is 4 years old.

1) The reason for it is performance

2) Did you make the trace flag a startup parameter?

Search the web for Glenn Berry SQL Server hardware and you will get a number of relevant links, including his free eBook: http://download.red-gate.com/ebooks/SQL/sql-server-hardware-ebook.pdf

I bet you were doing STATEMENT completed (which the default Tuning trace in Profiler traps), in addition to unnecessary bloating columns like application name, database name, etc.

Here is my Profiler...