You don't pass your query string o SQL-GETIT:
$SQLResult = SQL-GETIT -SQLServer $SQLServer -ADCredential $ADCredential -EncryptionFileName $EncryptionFileName -ConvertCredToPassword $ConvertCredToPassword `
-SQLDatabase $SQLDatabase -SQLUserName $SQLUserName -WorkingFolder $WorkingFolder -LogFile $LogFile
And without a query, SQL has no idea what to do!
But ... don't do it like that. Most SQL needs information passed to it:
SELECT ID, Name FROM Customers WHERE Balanace > 1000
When you make a function to do it for you, you have to pass the variable bit - 1000 in this case as part of the string, that means you have to concatenate strings.
Never concatenate strings to build a SQL command. It leaves you wide open to accidental or deliberate SQL Injection attack which can destroy your entire database. Always use Parameterized queries instead.
When you concatenate strings, you cause problems because SQL receives commands like:
SELECT * FROM MyTable WHERE StreetAddress = 'Baker's Wood'
The quote the user added terminates the string as far as SQL is concerned and you get problems. But it could be worse. If I come along and type this instead: "x';DROP TABLE MyTable;--" Then SQL receives a very different command:
SELECT * FROM MyTable WHERE StreetAddress = 'x';DROP TABLE MyTable;
Which SQL sees as three separate commands:
SELECT * FROM MyTable WHERE StreetAddress = 'x';
A perfectly valid SELECT
DROP TABLE MyTable;
A perfectly valid "delete the table" command
And everything else is a comment.
So it does: selects any matching rows, deletes the table from the DB, and ignores anything else.
So ALWAYS use parameterized queries! Or be prepared to restore your DB from backup frequently. You do take backups regularly, don't you? - OriginalGriff
It is possible to do this with a function, but it's even messier than what you have at the moment!