Search

Unable to perform Full Text DDL after reverting from DB Snapshot by J. Granden

Active

4
0
Sign in
to vote
Type: Bug
ID: 773710
Opened: 12/6/2012 12:21:37 PM
Access Restriction: Public
0
Workaround(s)
4
User(s) can reproduce this bug

After reverting to a database snapshot that contains fulltext indexes, you are unable to create any ft_catalogs until you either restart sql server, detach/attach the db, or take the db offline/ set the db online.

This error didn't happen in 2008 ( 10.0.5826.0 )

Microsoft SQL Server 2012 - 11.0.2383.0 (X64)
    Oct 5 2012 19:35:54
    Copyright (c) Microsoft Corporation
    Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)

Details (expand)

Product Language

English

Version

SQL Server 2012 - Enterprise Core Edition

Category

SQL Engine

Operating System

Windows Server 2008 R2 Enterprise

Operating System Language

US English

Steps to Reproduce

CREATE DATABASE [TestFTAfterRestore]
go
use testFTAfterRestore
go
create table t1 (id int not null, Msg varchar(100))
go
create unique clustered index IX_t1_id on t1 (id)
go
create fulltext catalog ft_cat
go
create fulltext index on t1 (msg language 1033) key index IX_t1_id on ft_cat
go
create database t1_snap on (name=TestFTAfterRestore, filename='N:\MSSQL11.MSSQLSERVER\MSSQL\DATA\TestFTAfterRestore_snap.ss') as snapshot of [TestFTAfterRestore]
go
use master
go
restore database [TestFTAfterRestore] from database_snapshot = 't1_snap'
go
use testFTAfterRestore
go
create fulltext catalog ft_cat
go
--use master
--go
--drop database [T1_snap]
--go
--drop database [TestFTAfterRestore]

Actual Results

Error Message:
Msg 9972, Level 16, State 100, Line 3
Database is not fully started up or it is not in an ONLINE state. Try the full-text DDL command again after database is started up and becomes ONLINE.

Expected Results

No Error, and FT Catalog is able to be created.

Platform

X64

Virtualization

 
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 4/23/2013 at 7:38 PM
Thanks for reporting the issue. We are currently investigating.
Sign in to post a workaround.