warning message during re-attachment of databases

643
1
Jump to solution
07-05-2017 05:13 AM
ErikBlake
Regular Contributor

Good morning.

We are in the process of moving from 2008 sql server to 2016 sql server. I am moving the databases via detach-Attach method. During the attachment part I got a few of these warnings:


Warning: The check constraint "g21_ck" on "dbo"."g21_ck" was disabled and set as not trusted because the implementation of "geometry" have changed.
Warning: The check constraint "A_g20_ck" on "dbo"."A_g20_ck" was disabled and set as not trusted because the implementation of "geometry" have changed.
Warning: The check constraint "A_g30_ck" on "dbo"."A_g30_ck" was disabled and set as not trusted because the implementation of "geometry" have changed.

It said that my sql query executed successfully and I was able to connect to the databases in ArcCatalog and republish all of my map services and tested them and everything seems to work fine. I was just wondering if anybody else has got these warnings and if they are something that I should be concerned about, or not worry about them since everything seems to be working fine.

0 Kudos
1 Solution

Accepted Solutions
ShannonShields
Esri Contributor

Hi Erik,

I was just forwarded your post - sorry that no one responded earlier. This Microsoft documentation can shed a little light on your issue: sys.dm_db_objects_disabled_on_compatibility_level_change (Transact-SQL) | Microsoft Docs 

It is nothing to really be concerned with - there were some functional changes to spatial type methods between 2008 and 2012 (or any later release) that 'invalidated' certain objects like check constraints. The check contraints in your database are placed automatically on the spatial column of any feature classes created by ArcGIS software. They are there to prevent shapes with invalid SRID values from being inserted into the column. If you ever insert or update shapes outside of ArcGIS software (e.g. at the SQL level or a 3rd party application) then you will want to change these contraints back to 'CHECK' from NOCHECK. If you don't then they can be left as-is.

-Shannon

View solution in original post

0 Kudos
1 Reply
ShannonShields
Esri Contributor

Hi Erik,

I was just forwarded your post - sorry that no one responded earlier. This Microsoft documentation can shed a little light on your issue: sys.dm_db_objects_disabled_on_compatibility_level_change (Transact-SQL) | Microsoft Docs 

It is nothing to really be concerned with - there were some functional changes to spatial type methods between 2008 and 2012 (or any later release) that 'invalidated' certain objects like check constraints. The check contraints in your database are placed automatically on the spatial column of any feature classes created by ArcGIS software. They are there to prevent shapes with invalid SRID values from being inserted into the column. If you ever insert or update shapes outside of ArcGIS software (e.g. at the SQL level or a 3rd party application) then you will want to change these contraints back to 'CHECK' from NOCHECK. If you don't then they can be left as-is.

-Shannon

View solution in original post

0 Kudos