Stop converting DateTime values to strings - and stop passing strings to SQL by concatenation.
Once a date is in DateTime format, keep it there, and pass it to SQL as a DateTime value via parameters (as you should for all values to pass to a database). Then let SQL stroe it in a DATE, DATETIME, or DATETIME2 column.
When you retrieve it, it comes back as a DateTime value and can be compared directly.
Or it could, if your SELECT statement was valid...
It should be
SELECT columnlist FROM MyTableName WHERE TheColumnIWantToCompare = ValueToCompareItWith
You are missing the WHERE and the column.
But in all seriousness, 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. Use Parametrized 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?