Latest Contributions by ChetDobbins

@mpboyle  I am wondering whether using database roles would help you achieve the same solution and ultimately make managing database permissions much easier. What i am suggesting is that you would create database roles that fit each user groups specific permission needs, then grant the needed permissions to the roles. When a new staff needs to connect to the database, you can determine which permissions role they fit into and simply create a new database user and add it to that database role.  ... View more

Hi John, Have you opened a technical support case for this? That may help us identify if this is something specific to your data and be able to troubleshoot further. If you have not or can not open one please let me know. ... View more

Yes, updating with SQL is fine for this change, and yes the update would be just setting the ATTRBUFSIZE = 1000000 (1 million). No need to change the MAXARRAYBYTES for now. We can look at other changes if this change doesn't provide enough improvement. ... View more

It is possible that you are noticing the effects of the ATTRBUFSIZE parameter that is specified in the SDE_server_config table. Could you provide more information about the data you are working with? I suspect that the data that copies faster either has less columns or just smaller sized columns (think NVARCHAR(max) versus INT). Also please confirm what release of ArcGIS you are using? ... View more

Good morning, I am wondering if you captured any sort of tracing that might help explain why the performance is better with the higher database compatibility setting. Often Microsoft will tie optimizer and other general improvements to the compatibility level so what you are seeing could be related to that, but it does peak my curiosity about what queries are actually being affected. It is always good to update the compat level though, whenever you upgrade SQL Server.  ... View more

Hi Shane, I think i know this particular issue, and believe it may be something we have recently fixed in the software which was related to ring order. You mentioned that you are using ArcGIS Pro 2.2, and ArcMap as well... can you confirm the version of ArcMap? I suspect it is 10.6.1 because that is when the issue I am thinking about would have been introduced.  The reason you wouldn't see the issue with data created by ArcGIS is because we will always follow our ring order requirements when inserting the data into a feature class. I suspect the method used to insert directly into the spatial table where you see this issue is not following our required ring order direction. SQL Server really does not care about this when the data is stored in the geometry spatial type so STIsValid would return the shape as valid no matter which way you inserted. In 10.6.1 we made some changes to our validation method which improved performance, but also resulted in problems when reading shapes that have this reversed ring ordering.  What is the  possibility that you could log a case with technical support so that we can get you hooked up with a defect? ... View more

I would like to try to simplify this discussion to clarify the root cause of the issue: There are only two ways that a SQL Server login can be mapped to the DBO user in a database. The login is a member of the sysadmin server-level role. The login is the owner of the database. If you create or enable a geodatabase using the SDE login and the SDE login meets either or both of those criteria, then the geodatabase will be stored in the DBO schema instead of the SDE schema. If you want to have an SDE schema geodatabase, you need to start over. Ensure that the SDE login is not configured with either of the items above, and then create a new database and geodatabase. If you created a geodatabase using the SDE login, and the geodatabase was correctly created in the SDE schema, but later the SDE login was configured to meet either or both of those criteria, the geodatabase will still be stored in the SDE schema. However, you will encounter issues when managing the geodatabase because SDE is no longer SDE, it is DBO. Ensure that the SDE login is not configured with either of the items above. Remove SDE from the sysadmin role, and/or change the ownership of the database to a user who can act as DBO in the database. ... View more

Currently Microsoft Azure SQL Database have not been certified for full geodatabase functionality. We are in the process of extending geodatabase support to this platform and hope to do so in the next major release. You can still create and work with geodatabase functionality in a test-only, or beta capacity but they are not yet supported in a full production environment. I would also like to mention that due to some limitations with Azure SQL Database v11, enterprise geodatabases will only be certified on v12 instances. ... View more

Hi David, The workflow for users who require the ability to work with views, is to access the view as a query layer or simply drag/drop the view (assuming it has a spatial attribute) into the map and define the required properties when necessary. The workflow you have described can lead to unknown behaviors and errors in the application (ArcObjects) when working with this object. The reason is because, the object they are deleting is a geodatabase table and we support additional capabilities on tables that we cannot support on views. With that said i would be interested in hearing more about situations where a view needs to be registered with the geodatabase. Could you describe workflows where you have required this capability? ... View more