Closed johnsonjkma closed 3 years ago
Hi, and welcome to the repo. Yes, this can indeed happen with really wildly named objects that break XML. Unfortunately, we don't have a fix coming on our side - your best bet there would be to identify which objects have wildly unusual names, and then see if you can reproduce the specific issue in sp_BlitzIndex by creating a new empty database, and just that one table or index with that name. If you can give us a repro script, we may be able to help, but otherwise, this isn't something we're going to be able to work on.
Version of the script @Version = '7.99', @VersionDate = '20200913'
What is the current behavior? When running for specific database or @GetAllADatabases = 1, returns the following error. Msg 50000, Level 16, State 1, Procedure sp_BlitzIndex, Line 2002 [Batch Start Line 0] HDMS_RF database failed to process. XML parsing: line 1, character 17, illegal name character
For Message output:
If the current behavior is a bug, please provide the steps to reproduce.
What is the expected behavior? Should return the normal list of Index recommends
Which versions of SQL Server and which OS are affected by this issue? Did this work in previous versions of our procedures? SQL Server 2014 SP3 Windows 2012R2 I'm actually not sure if this working in previous versions. I haven't really run sp_BlitzIndex on this database before.
**Here is the debug = 1