Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No automagic move for fulltext indexes #72

Open
GoogleCodeExporter opened this issue Mar 14, 2015 · 3 comments
Open

No automagic move for fulltext indexes #72

GoogleCodeExporter opened this issue Mar 14, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

I was doing a pretty basic task with roundhousE -- restoring a backup. Worked 
great for the simpler databases in this app, but when I got to the two with 
fulltext indexes the restores failed badly as it was trying to write the 
fulltext indexes to the original location which did not exist on the dev 
machine. The other databases, which by default would have gone to the same 
place, were automagically fixed. 

In this case our production keeps databases on D:\sql but my laptop has but a 
C:\ drive.

Steps to reproduce:

1) create a database on another machine with a fulltext index located someplace 
you don't have on the dev machine
2) try and restore the data to something that doesn't have that path.
3) Watch the errors.

Original issue reported on code.google.com by [email protected] on 26 Apr 2012 at 1:41

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant