http://www.simple-talk.com/sql/performance/finding-the-causes-of-poor-performance-in-sql-server,-part-1/

http://www.simple-talk.com/sql/performance/finding-the-causes-of-poor-performance-in-sql-server,-part-2/

Again, partitioning is not about performance. You define the ranges based on your business requirements for loading and removing data, that will guide your partition scheme and function. There's no...

Benki Chendu (2/12/2013)

---

For example, we have a database created in SQL Server 2012. We have an application which is configured to work with this database and it encounters some issues....

Let me guess, tiny table, 2 or 4 pages in size.

My previous advice stands. If no work is being done (and since you didn't post the recovery messages I can't tell), restart SQL. Otherwise wait. Or open a case with...

Please post table definitions, index definitions and execution plan, as per http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Is the distinct really necessary?

Table are unordered sets of rows....

Partitioning is not about performance. It's mostly about data management, fast loads, fast removal of data, compression of different partitions, index rebuilds at the partition level.

MyDoggieJessie (2/11/2013)

---

Regardless, there's little good reason to have that as part of a maintenance plan. If the maint plan rebuilds indexes or updates stats, it'll invalidate the plans that depend...

DVSQL (2/11/2013)

---

GilaMonster (2/11/2013)

---

The plan cache is part of the allocated SQL memory, with 26 GB of allocated memory it'll probably max out at somewhere around 5-6GB, I forget the exact...

They're all data anomalies as far as I know, and the 3 that define the ANSI standards for isolation levels have specific names and meanings, the isolation levels are defined...

The plan cache is part of the allocated SQL memory, with 26 GB of allocated memory it'll probably max out at somewhere around 5-6GB, I forget the exact formula.

Regardless, there's...

No, the sort order is mostly important when you're indexing...

Well, I do hope some future employer doesn't run across this thread.

Vedran Kesegic (2/11/2013)

---

So, it might happen that your statement starts reading a table, and after that other transaction starts and commits a row your query didn't reach yet. Your query...