Posted by CK on 09/29/81 11:32

You absolutely are right about me using Enterprise Manager to index the
table. I guess it's now the time for me to brush up on my SQL skill!!!


"Erland Sommarskog" <esquel@sommarskog.se> wrote in message
news:Xns9714D735F65AYazorman@127.0.0.1...
> CK (cf276@hotmail.com) writes:
>> It's not blocked. After some testings, I realised the problem was caused
>> by insufficient free harddisk space for the transaction log file. It
>> worked fine after I created another log file in a drive with plenty of
>> space. Nevertheless, I was surprised that SQL Server didn't give me any
>> warning message about this.
>
> I bet it did. But it sounds like you ran this through Enterprise Manager,
> and there could be some hickup in this tool, hiding the error message
> from you. Had you run the CREATE INDEX from Query Analyzer directly,
> you should have seen an error message. (Or at least so I like believe. :-)
>
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
>
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

[Back to original message]