# SQL Server Identity Column Detection

**URL:** <https://community.glideapps.com/t/sql-server-identity-column-detection/73230>\
**Category:** Ask for Help\
**Created:** [May 9, 2024, 8:54pm UTC](https://community.glideapps.com/t/sql-server-identity-column-detection/73230 "2024-05-09T20:54:39Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![raajkumars](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/raajkumars/32/74046_2.png) [@raajkumars](https://community.glideapps.com/u/raajkumars)\
**Post date:** [May 10, 2024, 5:06am UTC](https://community.glideapps.com/t/sql-server-identity-column-detection/73230/2 "2024-05-10T05:06:10Z")

</div>

I apologize if this is a basic question, but I haven’t used SQL Server as a data source in Glide before. When you say “Glide doesn’t detect this column,” do you mean that the column isn’t being imported at all, or that it’s being imported but not recognized as the ID column?

If it’s the latter, Glide doesn’t specifically use primary keys or unique keys; any valid column can be used in a relation or query. If it’s the former, it appears that Glide currently doesn’t automatically recognize SQL Server’s auto-incrementing identity columns as primary keys. This has been discussed by in the Glide community already without any solution. See [SQL Server Identity Column](https://community.glideapps.com/t/sql-server-identity-column/71966).

---

_[View the full topic](https://community.glideapps.com/t/sql-server-identity-column-detection/73230)._