Select to view content in your preferred language

Capitalization of table feature class name

1422
4
09-10-2012 12:13 PM
ducksunlimited
Deactivated User
Dear All,

I have found very few posts related to my issue. The issue was SDE always returned me a capitalized table feature class (like WATERQUALITY), but a mixed upper and lower case name (WaterQuality) is what i preferred. I contacted ESRI support and was told that SDE has the ability to store a table feature class with mixed cases. I was asked to install the SP 2 (V9.3.1 SDE and SQL Server 08) and the same issue. I can test altering the collation of the database, but want to see if anybody already had the same issue and could your experience. I appreciate any replies.

Thanks
Russel
0 Kudos
4 Replies
JoeBorgione
MVP Emeritus
Dear All,

I have found very few posts related to my issue. The issue was SDE always returned me a capitalized table feature class (like WATERQUALITY), but a mixed upper and lower case name (WaterQuality) is what i preferred. I contacted ESRI support and was told that SDE has the ability to store a table feature class with mixed cases. I was asked to install the SP 2 (V9.3.1 SDE and SQL Server 08) and the same issue. I can test altering the collation of the database, but want to see if anybody already had the same issue and could your experience. I appreciate any replies.

Thanks
Russel


I've never had a problem with it; all my feature classes are mixed case.  I use SQL Server Server 2008 R2, and before that SQL Server 2000.

Why would you need to change the collation of your SQL db?  I'm just not sure that a collation in your db has any bearing on mixed case file names. Why not just change the names to how you want them in ArcCatalog?
That should just about do it....
0 Kudos
ducksunlimited
Deactivated User
Yes, I could take an extra step to manually change the name after I created or imported a new table, but I just wonder why the name was capitalized after I first created or imported a table into the SDE?

Since case sensitivity is controlled by the collation of the database, I want to alter the default CI to CS to see if that will solve the issue or not.


I've never had a problem with it; all my feature classes are mixed case.  I use SQL Server Server 2008 R2, and before that SQL Server 2000.

Why would you need to change the collation of your SQL db?  I'm just not sure that a collation in your db has any bearing on mixed case file names. Why not just change the names to how you want them in ArcCatalog?
0 Kudos
KimPeter
Esri Contributor
Russell,

Don't change the collation of your database; case sensitive (CS) database collations are not supported with ArcGIS.
0 Kudos
ducksunlimited
Deactivated User
Kimberly, thanks for letting me know.

Russel


Russell,

Don't change the collation of your database; case sensitive (CS) database collations are not supported with ArcGIS.
0 Kudos