Warning message when comparing

Posted by: vvenk on 3 August 2017, 12:38 pm EST

  • Posted 3 August 2017, 12:38 pm EST

    Using the Schema Designer, I imported a database structure into a new schema. When I verified, it did not raise any errors.

    However, when I compared the schema with the database structure, it produced a whole slew of warning messages. An example of this is as follows:

    Warning: Database relationship 12 has no corresponding schema relation. Relationship condition(s):
    - ACT.Act_ID_N = BATT_ACT.Act_ID_N

    A warning is raised every time there is an foreign key relationship.

    Why is it happening? Should I be concerned? If so, how can I resolve it?

    I checked the database and there does exist a FK relationship between BATT_ACT and ACT.

    venki
  • Replied 3 August 2017, 12:38 pm EST

    Hello Venki,

    We would like to inform you that, this warning occurs when some tables have been left while selecting the objects to import in the schema.

    Let me explain the whole scenario:

    - Database structure has been imported to create a schema.
    - Objects are selected for import from the list of Available tables in the database structure.
    - Some of the tables from the Available tables have been selected and imported in the ‘Create schema tables’ section of the Import wizard.
    - Some tables are not imported.
    - Then the schema is created and verified. No error occurs because the newly created schema is perfect.

    Now when the schema is compared with the actual DataBase, you are getting some warnings. The reason being:
    - Some of the tables have not been selected for importing while creating the schema. These tables might have some relations with some other tables that you have selected for import.
    So while comparing the schema with the DataBase, these relations will not be found and the warnings are shown.

    You need not to worry about these warnings as you must have selected only those tables to import which are necessary for your model. These warnings are just to notify that these relations or tables do not exist in the schema.
    However, in order to avoid these warnings, you can add the absent DataBase objects in the schema. So the relations will also be imported and the warnings will not be shown. Please refer to the following URL for more information on Database Structure Evolution and the Schema.

    Please refer to the attached video for clarification. Hope it helps.

    Regards,
    Arpit Jain
    2015/08/avi_C1SchemaDesigner_ImportDB.gif
  • Replied 3 August 2017, 12:38 pm EST

    Arpit:

    When I imported, I did not do a selective import; I selected all the tables. And, when I chose the menu option, "Add Absent Database objects", nothing was shown. But the warnings exist.

    As I said,these are related to foreign key constraints from the Child to the Parent tables.

    I will also go through the link you sent me.

    Venki
  • Replied 3 August 2017, 12:38 pm EST

    Arpit:

    When I imported, I did not do a selective import; I selected all the tables. And, when I chose the menu option, \"Add Absent Database objects\", nothing was shown. But the warnings exist.

    As I said,these are related to foreign key constraints from the Child to the Parent tables.
    ject
    When I double-click on any of the warning messages, it brings the relationship and it looks fine. I wonder how it is able to infer this relationship without the supporting database object.

    I will also go through the link you sent me.

    Venki
  • Replied 3 August 2017, 12:38 pm EST

    Hello Venki,

    As you can observe in the video attached in the previous response that it is working fine if we add the absent objects in the schema, so we are sorry to mention but we could not replicate the mentioned issue at our end.

    We have tested the issue with the ‘C1NWind.mdb’ database installed with the C1Studio in the system. You can test with the same db which you can find in the following location:
    “C:\Users\[CurrentUser]\Documents\ComponentOne Samples\Common”

    Could you please share a sample database in which we can replicate the issue at our end along with the video demonstrating the same?
    So it would be helpful for us in narrowing down the cause for the issue and assisting you further at the earliest. Without replicating the issue, it would be very difficult for us to comment on the cause of the issue.

    Thanks and Regards,
    Arpit Jain
  • Replied 3 August 2017, 12:38 pm EST

    Arpit:

    I understand. Here's the SQL file to create the DB on Microsoft SQL Server that I am facing issues with.

    Once you execute the file, import it into a schema. Verify it; you should have no errors. But try "Compare the schema with the database structure". You should get a slew of warning messages.

    venki
    2015/08/Venki-DB-Create-sql.txt
  • Replied 3 August 2017, 12:38 pm EST

    Arpit:

    Here's the video of my scenarioa
    2015/08/venki-DBSchemaErrors.mp4
  • Marked as Answer

    Replied 3 August 2017, 12:38 pm EST

    Hello Venki,

    Thank you for sharing the sql file.
    We are sorry to mention but we are unable to execute the sql file which you have provided. While executing the sql file, it shows so many errors. Please refer to the attached text file wherein the error messages are copied. You can also refer to the attached video demonstrating the same.

    Could you please share the backup file (.bak) of some dummy db so that we can replicate the issue at our end with that dummy db?
    Or if possible, please resolve the errors which are shown when using the sql file.
    Or share the dummy database file with us through which we can reproduce the issue.
    Please make sure that you first zip the file whichever you are sharing and then attach it.

    And we would like to inform you that the video that you have attached is not attached properly in the post. So, we cannot get the video. Please attach it again.

    Thanks,
    Arpit Jain

    2015/08/DataBaseCreate_Errors.zip
Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels