MOCKSTACKS
EN
Questions And Answers

More Tutorials









SQLServer Identifier

Unquoted identifiers


Unquoted identifiers can use letters (a-z), digits (0-9), and underscore (_), and must start with a letter.

Depending on SQL implementation, and/or database settings, other characters may be allowed, some even as the first character, e.g.

.MS SQL: @, $, #, and other Unicode letters

.MySQL: $

.Oracle: $, #, and other letters from database character set

.PostgreSQL: $, and other Unicode letters


Unquoted identifiers are case-insensitive. How this is handled depends greatly on SQL implementation:

.MS SQL: Case-preserving, sensitivity defined by database character set, so can be case-sensitive.

.MySQL: Case-preserving, sensitivity depends on database setting and underlying file system.

.Oracle: Converted to uppercase, then handled like quoted identifier.

.PostgreSQL: Converted to lowercase, then handled like quoted identifier.

.SQLite: Case-preserving; case insensitivity only for ASCII characters.


Conclusion

In this page (written and validated by ) you learned about SQLServer Identifier . What's Next? If you are interested in completing SQLServer tutorial, your next topic will be learning about: SQLServer Data Types.



Incorrect info or code snippet? We take very seriously the accuracy of the information provided on our website. We also make sure to test all snippets and examples provided for each section. If you find any incorrect information, please send us an email about the issue: mockstacks@gmail.com.


Share On:


Mockstacks was launched to help beginners learn programming languages; the site is optimized with no Ads as, Ads might slow down the performance. We also don't track any personal information; we also don't collect any kind of data unless the user provided us a corrected information. Almost all examples have been tested. Tutorials, references, and examples are constantly reviewed to avoid errors, but we cannot warrant full correctness of all content. By using Mockstacks.com, you agree to have read and accepted our terms of use, cookies and privacy policy.