Technically it's not exactly a bug. The max allowable size for a transaction log file is 2 TB, so unrestricted or not, a log file cannot grow larger than that.

What, exactly are you doing to get that error?

SQL 2008? Why is this posted in the SQL 2000 forums?

Thanks Paul

S.saravanan: Out of curiosity, how did you fix it?

SQL_Quest (4/20/2009)

---

index_name avg_fragmentation_in_percent page_count

eg. CLUSTERED INDEX0.675260896255371 ...

brd123 (4/20/2009)

---

Hi Gail, I guess the main reason is that I don't know enough about full-texting in SQL Server but I am assuming it probably has its own language thus...

Bear in mind that the -1/2TB 'bug' only applies to log files. Data files with unrestricted growth do show a -1 there.

Except for the first one, all the others are far too small to even worry about fragmentation.

Gianluca Sartori (4/20/2009)

---

I also own a licensed copy of SQLRefactor, but this tool lacks a feature for performing such kind of operations. Do you know any kind of tool or...

If you're running a profile trace from SQL profiler, it's the client application that's receiving the trace from SQL and writing it to a table. Hence if you close profiler,...

Lynn Pettis (4/20/2009)

---

I am not an expert in SQL Server internals, but I would not be surprised if SQL Server stored all fixed length columns at the front of each...

Eeep....

brd123 (4/20/2009)

---

User wants to find all items/products in database (this is using a common web storefront product) that contain the words 'civil war'. Product name, description, id and stocking...

The generator problem was a series of small problems.

This was a bank of large generators that were designed to supply power to 6 office blocks (one of which was a...

Depends whether the index has been created with PAD_INDEX on or off. If it's on, the fill factor applies to the non-leaf levels as well. If it's off, the non-leaf...

Now that's one I haven't had...