SQLRNNR (9/2/2013)

---

Koen Verbeeck (9/1/2013)

---

GilaMonster (8/31/2013)

---

Just ....

Sent...

If the DMV shows that the index has 11.111% fragmentation, then the index has 11.111% fragmentation. Not 5%, not 3%, 11.111%. The DMV is accurate.

If the index is small (which...

So how do you decide which of M...

The DMV is correct. If it shows 11.1111%, then that index is 11.1111% fragmented.

Chapter 4: https://www.simple-talk.com/books/sql-books/troubleshooting-sql-server-a-guide-for-the-accidental-dba/

Set max server memory to a sensible value.

Neither rebuild nor reorganise is expected to reduce fragmentation to 0. If the index is very small it's unlikely to change the fragmentation at all. No, it's not a bug.

Also some sample data for the tables would be useful.

Edit: Not a list of the columns in the table. The table's definition, the way you gave the Levels table.

The trigger...

Elapsed time is literally that. It's the actual, real time that elapsed while the query was running. Measured by taking the actual real time that the query started, the actual,...

Query parallels, spends 10 seconds executing on 4 CPUs. Elapsed time, 10 seconds. CPU time used 10 seconds * 4 CPUs = 40 seconds.

Updating with a temp table (# table) is the same as with a normal table.

Can you explain a bit clearer where you're stuck?

There is no SQL Server feature called label policy. SQL Server database engine doesn't have cells, nor does it have row-level security.

SSAS maybe? SSRS? Something else?

As little as possible, only where absolutely necessary and after having paid careful attention to the risks of SQL Injection.

That would be the SGAM page.

Sure it's for SQL Server and not something like Excel?

There's no such feature in SQL as 'label policy'

Where did you hear that phrase and in what context?