Hi,
I have a table with three hexadecimal computed columns of type varbinary(8000). I did not create this table and I don't know why the author chose a column of varbinary(8000), when the max len on this column is only 16?
Anyways, I had some joins on these hexadecimal columns that were taking forver, so I indexed the hexadecimal columns. The indexes only took a few moments to create and sped up the query tremendously. I did get some errors to the effect that the length can't exceed 900 or something but didn't pay much attention to it because it seemed to work.
However, when I went to delete the indexes, it was taking a really looong time. So I decided to just drop the table. Now that's taking a really looong time. I've never seen this behavior before. Please help. The table has 500K rows.
Thank you
I have a table with three hexadecimal computed columns of type varbinary(8000). I did not create this table and I don't know why the author chose a column of varbinary(8000), when the max len on this column is only 16?
Anyways, I had some joins on these hexadecimal columns that were taking forver, so I indexed the hexadecimal columns. The indexes only took a few moments to create and sped up the query tremendously. I did get some errors to the effect that the length can't exceed 900 or something but didn't pay much attention to it because it seemed to work.
However, when I went to delete the indexes, it was taking a really looong time. So I decided to just drop the table. Now that's taking a really looong time. I've never seen this behavior before. Please help. The table has 500K rows.
Thank you