I'm using Add Query Layer to connect to a view in SQL Server 2008. This is the first time I've connected to a view that doesn't have a single field I can specify as the unique ID column. The documentation reads that if I don't have one, I can specify multiple fields and internally the software will create a value to go into the ESRI_OID field.
I have a couple of problems. First, I noticed that the fields are truncated to 31 characters. I haven't read anything about a field name limitation, but the two long columns were both cut off at 31. One of these columns is one that I need to create the unique ID.
When I specify the 3 columns that to be used, it validates and I don't get any errors. However, when I open the table, there are no contents. I know there is data in this view, because if I connect to as a straight OLE connection, I can see the data. But since I need to be able to query the data, I have to use 'Add Query Layer' to get there.
I have 3 other views in this database that are working just fine. These 3 all had a single field that could be used as a unique ID, and it so happens that none of them contained such long field names.
I have a couple of problems. First, I noticed that the fields are truncated to 31 characters. I haven't read anything about a field name limitation, but the two long columns were both cut off at 31. One of these columns is one that I need to create the unique ID.
When I specify the 3 columns that to be used, it validates and I don't get any errors. However, when I open the table, there are no contents. I know there is data in this view, because if I connect to as a straight OLE connection, I can see the data. But since I need to be able to query the data, I have to use 'Add Query Layer' to get there.
I have 3 other views in this database that are working just fine. These 3 all had a single field that could be used as a unique ID, and it so happens that none of them contained such long field names.