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.
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.