| title | MSSQLSERVER_1793 |
|---|---|
| description | MSSQLSERVER_1793 |
| author | MashaMSFT |
| ms.author | mathoma |
| ms.date | 04/04/2017 |
| ms.service | sql |
| ms.subservice | supportability |
| ms.topic | reference |
[!INCLUDE SQL Server]
| Attribute | Value |
|---|---|
| Product Name | SQL Server |
| Event ID | 1793 |
| Event Source | MSSQLSERVER |
| Component | SQLEngine |
| Symbolic Name | FILESTREAM_BASEDATA_NEED_SAME_PARTITION |
| Message Text | Cannot drop index '%.*ls' since a partition scheme is not specified for FILESTREAM data. |
This message occurs when you try to drop a clustered index on a table that contains FILESTREAM data, and you specify a MOVE TO clause for the base data, but you do not specify a FILESTREAM_ON clause for the FILESTREAM data.
When dropping a clustered index on a table that contains FILESTREAM data, use one of the following options:
-
Specify both a MOVE TO clause for the base data and a FILESTREAM_ON clause for the FILESTREAM data.
-
Do not specify either a MOVE TO clause for the base data or a FILESTREAM_ON clause for the FILESTREAM data.
The following example fails because a partition scheme is specified for the base data, but is not specified for the FILESTREAM data.
DROP INDEX [<clustered_index_name>] ON [<table_name>]
WITH ( ONLINE = OFF, MOVE TO [PRIMARY] )
GO
The following example succeeds because both a MOVE TO clause for the base data and a FILESTREAM_ON clause for the FILESTREAM data are specified.
DROP INDEX [<clustered_index_name>] ON [<table_name>]
WITH ( ONLINE = OFF, MOVE TO [PRIMARY], filestream_on 'default' )
GO
The following example also succeeds because neither a MOVE TO clause for the base data nor a FILESTREAM_ON clause for the FILESTREAM data is specified.
DROP INDEX [<clustered_index_name>] ON [<table_name>]
WITH ( ONLINE = OFF )
GO