Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Azure_DevOps_Server_2019/ReIndexFiles.ps1

Open
#93 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
powershell, sql
Domain
database, tooling

Research direction

Start with Azure_DevOps_Server_2019/ReIndexFiles.ps1 at line 67 and inspect the SQL input used by Invoke-Sqlcmd. Compare that call with the listed Search.prc_MergeFileLevelFailures signature, including @maxFailureThreshold. Done means the script supplies the required procedure inputs and no longer reports the missing-parameter error when rerun.

Written by the indexing model from the issue text.

Description

Has somebody already ran this script ;)

Invoke-Sqlcmd : Procedure or function 'prc_MergeFileLevelFailures' expects parameter '@maxFailureThreshold', which was not supplied.
At C:\Code-Search\Azure_DevOps_Server_2019\ReIndexFiles.ps1:67 char:21
+ ... ryResults = Invoke-Sqlcmd -InputFile $SqlFullPath -serverInstance $SQ ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [Invoke-Sqlcmd], SqlPowerShellSqlExecutionException
    + FullyQualifiedErrorId : SqlError,Microsoft.SqlServer.Management.PowerShell.GetScriptCommand

prc_MergeFileLevelFailures parameters:

-- Hash: 66F9F9467AC87713D89D5AB3A184B27B3A12FB6D
ALTER PROCEDURE [Search].[prc_MergeFileLevelFailures]
(
    @partitionId               INT,
    @indexingUnitId            INT,
    @fileLevelFailureRecords   Search.typ_FileFailureRecord READONLY,
    @maxFailureThreshold       INT
)
Dominant language
PowerShell
Stars
57
Forks
68
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/Code-Search

All issues in microsoft/Code-Search

Similar issues

More Databases issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.