Search

SSMS 2012: Path configured in "Create Full-Text-Catalogue"-Dialog is ignored by Roman Haefeli

Closed

1
0
Sign in
to vote
Type: Bug
ID: 778471
Opened: 2/4/2013 8:25:53 AM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
If you create a new full text catalog using SSMS 2012, the path configured in the "New full text catalogue"-dialogue will be ignored and a standard path will be used for creating the new full text catalogue.
Details (expand)

Product Language

German

Version

SQL Server 2012 - Standard Edition

Category

Tools (SSMS, Agent, Profiler, Migration, etc.)

Operating System

Windows Server 2008 Standard (SP2)

Operating System Language

German

Steps to Reproduce

* Open the SQL Server Management Studio
* Browse to an existing Database that has no fulltext catalogues configured yet.
* Browse to "storage->full text catalogue" ("Speicher" in German locale)
* right-click and choose "Create new full text catalogue"
* In the "New full text catalogue"-dialogue set a path for the new catalogue to be stored.
* Click "Ok" in order to create a new full-text catalogue.

Actual Results

A new full text catalogue is created in the standard full text catalogue path, but not in the path configured in the previous dialog.

Expected Results

The new full text dialog should be created in the path as given in the dialog

Platform

X64

Virtualization

 
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 3/28/2013 at 12:25 PM
Hello

We took a look at this bug along with several others recently.
Unfortunately, triaging it against other critical bugs, I do not think we would get to investigating this in the near future.
However, we have taken note of this internally, and when we revisit this functionality in the future, we will try and get this resolved.

Thanks for writing in to Microsoft.
Alex Grach[MSFT]
Posted by Microsoft on 2/21/2013 at 10:32 AM
Thank you for reporting this issue - we are investigating and will update you when we have more information.

Thanks,

Alex Grach [MSFT SQL SERVER]
Sign in to post a workaround.