Latest Contributions by ShannonShields

At 10.1 we still use OLEDB to access SQL Server. The SQL Native client provides oledb as well as odbc access. At 10.2 we've moved from OLEDB to ODBC. We are trying to provide support for the new ODBC driver on Windows soon. It won't be in the 10.2 released, but we'll try to make it available very shortly afterwards. -Shannon ... View more

No, it isn't. It seems Microsoft recently decided to rename the SQL Server Native Client, and it is now called: "Microsoft ODBC Driver 11 for SQL Server on Windows" (/ Linux in the Linux version). This is not the same thing as the Native Client and is not yet supported by ArcGIS. It will be supported at a later release. For 10.1 you must still use the Native Client when connecting to SQL Server from ArcGIS. -Shannon ... View more

Anthony, we don't fully support AlwaysOn at 10.1. At 10.1 you can connect to a read-only database, not a geodatabase. The ability to connect to a read-only geodatabase will be part of the 10.2 release. The ability to do read-only routing via the Listener using the APPLICATIONINTENT connection parameter will be available in the following release. -Shannon ... View more

- In order to connect to SQL Server 2012 you must use the SQL Server 2012 native client, i.e. you cannot use the SQL Server 2008 native client No, the SQL Server Native Client 2008 should be able to connect too. I personally have connected using 2008 R2, but haven't tested the 2008 Native Client, with SQL Server 2012 yet. The SQL Server 2008R2 Native Client can connect to SQL Server 2012, but it is not supported. The native client libraries are backward compatible, but not forward. http://msdn.microsoft.com/en-us/library/cc280356.aspx �??SQL Server Native Client 11.0 supports connections to SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012.�?� http://msdn.microsoft.com/en-us/library/cc280356(v=sql.105).aspx "SQL Server 2008 R2 Native Client supports the version of SQL Server in which it is released, and SQL Server 2000 SP4, SQL Server 2005, and SQL Server 2008." -Shannon ... View more

Unfortunately, this error generally indicates some sort of corruption, probably of the database file header. You can try attaching with the sp_attach_single_db or CREATE DATABASE ... FOR ATTACH commands and see if any additional information is provided. Otherwise, restore the database from a backup. -Shannon ... View more

With the patch installed, you can use the 2012 Native Client again. -Shannon ... View more

I would have expected a patch by now. http://support.esri.com/en/downloads/patches-servicepacks/view/productid/67/metaid/1954 A patch was released in early February. -Shannon ... View more

Like Vince said, it looks as if your data is stored using the Geometry type rather than the Geography type. In the case of Geometry you'd use the STX and STY methods to get the individual coordinates of each point. You can check the properties of your feature class in ArcCatalog to see what the underlying spatial type is, or you can query directly to SQL Server like this: [INDENT]select data_type from information_schema.columns where TABLE_NAME = <your_table> and COLUMN_NAME = 'shape'[/INDENT] -Shannon ... View more

What version of ArcGIS are you using? There has been a fix to address this issue - I'd have to check to see exactly which version it is in. -Shannon ... View more

It looks like you are trying to migrate to SDE Binary format. This is not supported. Migration is only supported from SDE Binary to other storage types, not the other way around. Here is a full list of which migrations are supported: http://resources.arcgis.com/en/help/main/10.1/index.html#//002n00000076000000 -Shannon ... View more

For example, instead of uspsde.'John.Smith'.roads, we can configure it so that it displays (for example) upssde.Florida.roads? Brendan, you could add the John.Smith AD login to SQL Server, and make a user named 'Florida' in the upssde database that is associated with the John.Smith login. The SQL would look something like this: CREATE LOGIN [DOMAIN\John.Smith] FROM WINDOWS WITH DEFAULT_DATABASE=[upssde] GO USE [upssde] GO CREATE USER [Florida] FOR LOGIN [DOMAIN\John.Smith] GO ALTER USER [Florida] WITH DEFAULT_SCHEMA=[Florida] GO CREATE SCHEMA [Florida] AUTHORIZATION [Florida] This would mean that everytime John Smith connected to the upssde database he would be a user named 'Florida'. You could not do this if he was added by way of an AD group, only if he was added individually to the SQL Server instance. Anytime you wanted data created on the 'Florida' schema, John Smith would have to be the person logging in to perform this task. Not really convenient, but it can be done if you are using individual Windows logins, but not groups. -Shannon ... View more

Brendan, >So SDE/ArcCatalog is supposed to display the feature class as "upssde.'John.Smith'.roads"? Yes, this is correct. We'll always display the fully-qualified name. This may be different depending on your data's source. In the case of SQL Server, it is database.schema.table >Will it always assign the Active Directory user's name to the schema/feature class? The basic model is that the user that creates the feature class "owns" it. SQL Server operates a little bit differently in that several releases ago (SQL Server 2005) they removed the concept of "ownership" as it applies to most database objects. Instead, within a database, there can be one or more namespaces called schemas. When data is created, it is associated with a particular schema. So, you could create a schema called 'Payroll' that housed all your payroll data, and multiple users could have permission to create data on the Payroll schema. John.Smith could create a table on Payroll by specifying the schema name in the create table statement - CREATE TABLE Payroll.Employee. Even though he created the data, he doesn't actually own it. However.... and this is a big however, ArcGIS doesn't support schemas in SQL Server this way. We are working on addressing this in a future release, but right now we are still tied into this concept of ownership - the user who creates the data owns the data. There are several operations that restrict functionality based on ownership. For example, when using ArcGIS only the owner of a feature class can add or remove columns from it, or grant permission to other users to see it. Despite the fact that SQL Server may allow other users with elevated permission to perform these tasks, ArcGIS will restrict them. So, if your users are going to create and manage data in a SQL Server database using ArcGIS, any user who will create tables or views must have a default schema that has the same name as their user name. Users can only create data on their default schema, and that schema's name must match the user's. > I thought if I assigned editors to a role or a group, the feature class would take the role or groups name. No. Once an object is created on a particular schema, it stays on that schema. If John.Smith creates a feature class named roads, it will be referenced as "John.Smith".roads, regardless of John.Smith's role or group membership. >What happens when multiple users edit a file? Will the file always have the name of the user that created it?  And if we export the feature class, feature dataset or database, will it display the users name as part of the feature name? Having the ability to edit a table is separate from being able to create one. Users can be granted permission to perform edit operations on a table, but that has no impact on the schema that the table resides on. If you export the feature class, the user name will not be part of the export. If the table is exported to another SQL Server database, the user that performs the export operation will be the new "owner" of the table. So if Dave.Jones exports John.Smith's roads feature class into a new database, that table will become "Dave.Jones".roads. -Shannon ... View more

You choose the SQL Server Native Client based on your OS. If it is a 64-bit OS, you must install the 64-bit client. As Tom says, the 64-bit client contains both 32-bit and 64-bit components. Even though ArcGIS Desktop is a 32-bit application, you'll still install the 64-bit Native Client. -Shannon ... View more