Forum Discussion
SQL Server fails login with password having semicolon
Hi ACarrera1971
It can help if you provide us with the queries you run, because the mind reading ability of some of us does not work well. When you have an issue, then first of all you should describe what you did and as possible provide the tool to reproduce the case.
In general BY DEFAULT there is no issue in using semicolon in password. You can use any UNICODE character as well and not just English - Note that "can" DONT NOT mean "should"!
USE master GO CREATE LOGIN [RonenרונןWithsemicolon;] WITH PASSWORD = '[PassWithsemicolon;AndHebrewעברית]'; GOThe above code uses semicolon and Hebrew characters and it run without any issue.
Note! It is highly recommend NOT to use special characters in the LOGIN name, but for password it is a good idea to do so, with that said using non-English characters is not recommended if you cannot confirm that you will have option to use such chars anyway and everywhere.
Hi ACarrera1971
It can help if you provide us with the queries you run, because the mind reading ability of some of us does not work well. When you have an issue, then first of all you should describe what you did and as possible provide the tool to reproduce the case.
In general BY DEFAULT there is no issue in using semicolon in password. You can use any UNICODE character as well and not just English - Note that "can" DONT NOT mean "should"!
USE master
GO
CREATE LOGIN [RonenרונןWithsemicolon;] WITH PASSWORD = '[PassWithsemicolon;AndHebrewעברית]';
GO
The above code uses semicolon and Hebrew characters and it run without any issue.
Note! It is highly recommend NOT to use special characters in the LOGIN name, but for password it is a good idea to do so, with that said using non-English characters is not recommended if you cannot confirm that you will have option to use such chars anyway and everywhere.
- Thanks for your answer,
Really I was not using any query, I was using the SQL Management Studio for carrying out the update/create of the login with semicolon in the password and also to login (although I tested using the ADO after having resolved the issue with semicolon in he connection string).
I fully agree with you that having semicolon in the password should not be a problem at all and this is the reason I wonder if the problem I am experiencing is associated with a special kind of configuration in the server.
I will try using the direct SQL sentences to create the login. Good to know you did not find any issue with such password.
