Support Rebuilding Indexes Online for Tables with Large Objects
Following the guidance from
I attempted to rebuild a heavily fragmented index using Online=ON:
ALTER INDEX ALL ON [Backups] REBUILD WITH(ONLINE = ON)
And received the following error:
'ONLINE INDEX DDL WITH LARGE OBJECT' is not supported in this version of SQL Server.
My table contains a varbinary(max) field. This is a serious flaw. Please fix.
13 comments
-
Anonymous
commented
Hello, i would like to ask that what is the benefits of sql training, what all topics should be covered and it is kinda bothering me … and has anyone studies from this course http://www.wiziq.com/course/125-comprehensive-introduction-to-sql of SQL tutorial online?? or tell me any other guidance...
would really appreciate help… and Also i would like to thank for all the information you are providing on sql training. -
Mike
commented
Throws this error with nvarchar(4000) also. This is very important because it negatively impacts both performance and billing.
-
Shane Milton
commented
I agree with the original poster. This is a SERIOUS flaw. I have a table w/ 250M records in it and it has nvarchar(max) as it contains up to ~32k unicode characters (although usually much smaller). There is no known work-around to this as far as I can tell. :-/
-
Ravi
commented
This is must need feature
-
Joel Bentolila
commented
Impossible to monitor index quality without this feature
-
SQLSERVERGUY
commented
Please enable this DMV to view index fragmentation details.
-
Saravanan Subburayal commented
currently the following data columns are not supported for REBUILD ONLINE.
* XML index
* Spatial index
* Large object data type columns: image, text, ntext, varchar(max), nvarchar(max), varbinary(max), and xmlFor the time being, get to know the max size of binary info that will accomodate in the varbinary column and provide, for eg., if you are sure that it will not have data more than 1024 b, then change varbinary(max) -> varbinary(1024).
-
Saket
commented
Please enable this DMV to view index fragmentation details.
-
Anonymous
commented
Checking index fragmentation is a must! Please ad this feature.
-
gidi aviezer
commented
please. we need check the indexes.
10x
-
Anonymous
commented
Please include this at the earliest
-
Anonymous
commented
With the product we're developing it is difficult to gauge per-tenant and overall database usage. This is required so that we can effectively split tenants across databases.