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

Full text custom collector needs a minor correction to database placeholder for db names with spaces or numeric values at the beginning #193

Closed
PiJoCoder opened this issue Oct 6, 2022 · 0 comments
Assignees
Labels
wave 1 - closed consider this issue for next wave of fixes

Comments

@PiJoCoder
Copy link
Collaborator

PiJoCoder commented Oct 6, 2022

Do you want to request a feature or report a bug?
Bug

What is the current behavior?
sp_msforeachdb 'IF EXISTS (select * from ?.sys.fulltext_catalogs) would fail if the database name contains spaces or numeric values at the beginning

**If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem **
Collect this on a SQL Server where you have db names with spaces

What is the expected behavior?
The script to collect information successfully

Which versions of SQL Server and which OS are affected by this issue? Did this work in previous versions of our procedures?
Issues has been there all along

@PiJoCoder PiJoCoder added the wave 1 - closed consider this issue for next wave of fixes label Oct 6, 2022
@PiJoCoder PiJoCoder changed the title Full text custom collector needs a minor correction to database placeholder for db names with spaces Full text custom collector needs a minor correction to database placeholder for db names with spaces or numeric values at the beginning Oct 6, 2022
@PiJoCoder PiJoCoder added wave 2 consider this issue for next wave of fixes and removed wave 1 - closed consider this issue for next wave of fixes labels Oct 6, 2022
@PiJoCoder PiJoCoder added wave 1 - closed consider this issue for next wave of fixes and removed wave 2 consider this issue for next wave of fixes labels Oct 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wave 1 - closed consider this issue for next wave of fixes
Projects
None yet
Development

No branches or pull requests

2 participants