microsoft / microsoft/Code-Search
SqlServer module instead of SQLPS
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 57
- Forks
- 68
- PR merge metrics
- No merged PRs in 30d
Description
It would be nice to start switching to SqlServer module instead of SQLPS, which is no longer being updated and is only available with SQL Server.
In general, when managing Code Search instance, it is not convenient to switch to SQL server and run part of the scripts there. Sometimes, in bigger organizations, there is a dedicated team, who is responsible for managing and maintaining SQL Servers and you typically do not get sufficient access to the server to run scripts. Which is why it would be a way better to be able to manage the Code Search instance from the same box, where it is installed.
I think, amending PS scripts to start depending on SqlServer PS module would be beneficial.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the PowerShell scripts that depend on SQLPS and identify the SQL Server commands they use. Compare those dependencies with the SqlServer PowerShell module; done means the management scripts can run from the Code Search host without requiring SQLPS or access to a separate SQL Server.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- databases
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100