How can we help you today? How can we help you today?

Stored procedure parameter auto-completion

After installing version 11.0.1.16766, stored procedure parameter auto-completion stopped working.

luca.cestola
1

Comments

3 comments

Sort by
  • CR12

    The log files is catching the issue:

    2025-06-05 15:55:37.180 -03:00 [Warning] Database population step failed for database Allied.Live.Database - step parameters
    System.IndexOutOfRangeException: Index was outside the bounds of the array.
      at RedGate.SqlPrompt.Cache.ParameterDefaultValueExtractor.ProcessSingleLineComment(String body, Int32& index, ContextTypes& currentContext)
      at RedGate.SqlPrompt.Cache.ParameterDefaultValueExtractor.GetFilteredBody(String body)
      at RedGate.SqlPrompt.Cache.ParameterDefaultValueExtractor.GetFromObjectDefinition(IEnumerable`1 procedureParameters, String body)
      at RedGate.SqlPrompt.Cache.ParameterDefaultValueUpdater.UpdateFromObjectDefinition(Dictionary`2 objectDefinitions, List`1 parameters)
      at RedGate.SqlPrompt.Cache.Population.Steps.Queries.Filtered.ParameterQuery.Execute(IDbCommand command)
      at RedGate.SqlPrompt.Cache.Population.Steps.ParameterPopulationStep.Populate(IDbCommand command)
      at RedGate.SqlPrompt.Cache.Population.DatabasePopulator.PopulateStep(DebugLogger logger, DbCommand command, IDatabasePopulationStep populationStep, String databaseName, Single overallPercentageComplete)
    2025-06-05 15:55:44.255 -03:00 [Information] [KATDB16].[Allied.Live.Database] Cache finished with no warnings

    CR12
    0
  • graded

    Hi Luca, I’m seeing the same issue after updating to version 11.0.1.16766. The logs show an issue IndexOutOfRangeException in the parameter extraction logic, specifically when processing single-line comments. This suggests the auto-complete issue might be related to how the new version handles comments within stored procedure definitions. If your procedures contain inline comments near the parameters, that could be causing the failure. Until there’s a fix, reverting to the previous version might be the most stable workaround.

    graded
    0
  • luca.cestola

    Thanks for the clarification , indeed our procedure stories have a special comment area. I confirm that with the new release the problem is overcome.

    luca.cestola
    0

Add comment

Please sign in to leave a comment.