Common Problems

  • 1
    Acknowledged

    numeric(precision, scale) data type in PostgreSQL

    Initialkommit · 1 · Last reply by Initialkommit

    Hi

    I don't generate precision and scale of numeric from database.

    I just see only numeric in Data type.

    Is there solution? or could you please support numeric(precision, scale) in postgresql!?

    Thank you

  • 1
    Solved

    Missing table from PostGreSQL

    Sebastien · 8 · Last reply by Piotr Tokarski

    Hello,

    We are using Dataedo 7 (64 bits), and we imported a PostGreSQL database.

    But a few tables do not appear in the dataedo documentation. I do not see any privilegies issues with that tables.

    The only difference between these missing tables and the tables that were correctly imported is that : these tables were created in PostGreSQL with the tool phpPGadmin.

    I do not know what to check. Do you have any idea ?

    Thanks,

    Sébastien.

  • 1

    Error while synchronizing the columns

    Tanner Spaulding · 1 · Last reply by Piotr Tokarski

    When attempting to import the schema from an Azure SQL Database, into an Azure SQL DB for the dataedo repository.  I am seeing the attached error message.  Any ideas how to avoid this?

    Dataedo version:  7.0.3 beta

    Source and Target DB:  Microsoft SQL Azure (RTM) - 12.0.2000.8 

  • 1
    Solved

    Import error "Unable to synchronize objects Index 0 is either negative or above rows count."

    Piotr Tokarski · 1 · Last reply by Piotr Tokarski

    We've found an issue in Dataedo 7.1 which causes an error during import if repository contains ignored objects.

    A fix for it will be released in Dataedo 7.1.1 planned for 2018-09-27.

    Additionally, there is a workaround. If during import you encounter this error, connect to your repository using SQL Server management studio and run the commands below:

    update [dbo].[tables] set [subtype]=[object_type] where subtype is null;  update [dbo].[procedures] set [subtype]=[object_type] where subtype is null;

    This solves the issue in our tests.

  • 1
    Solved

    System.FormatException: Incorrect key length

    John M Kiener · 1 · Last reply by Piotr Kononow

    When trying to enter Dataedo key for Version 7.1 license which I just purchased and installed.

  • 1
    Solved

    System.FormatException: Incorrect key length

    Jmk · 2 · Last reply by Piotr Kononow

    When trying to enter Dataedo key for Version 7.1 license which I just purchased and installed.

  • 1
    Acknowledged

    When on network drive, slow

    Jason · 1 · Last reply by Piotr Tokarski

    When we do the file-share, it is slow as molasses on a network drive. Is there a way to have the network drive not be a real-time connection? Or, any other way to have a local copy reconcile with a network copy at certain points?

  • 1
    In Progress

    Dataedo window looks wrong, text doesn't fit

    Piotr Tokarski · 1 · Last reply by Piotr Tokarski

    Recently we found out about an issue with Dataedo when Windows10's display scaling feature. It seems that the window and label fields don't scale up proportionally with the text, causing it to look similar to this:

    We're still working on this issue.

    [Originally posted on Flarum on 2018-03-29 08:16:41]

  • 1
    Acknowledged

    Arabic supporting in Tables documentation

    A Alkhalifah · 1 · Last reply by Piotr Tokarski

    The arabic langauge is not supported under the table documentation as show :

  • 1
    Solved

    Mysql Connection fail

    Margarita Mejia · 3 · Last reply by Piotr Tokarski

    Hello,

    I'm using Dataedo version 6.4 pro but I'm not able to connect to my MYSQL 5.6.40 database, I have my root user and password for the database but I still see it as a connection issue. Could you please help me. Are there any issues now for a particular windows version, because I used to be able to connect maybe like 6 months ago. I have try with the latest version Dataedo 7.1.1 and I have the same issue just that the error is "Access denied for user 'root'@'localhost' (using password: NO)"

  • 1
    Solved

    Changes or additions to MS_Description in MSSQL objects not detected during "Update Documentation." I have to remove the object from repository and re-import it to pick up MS_description

    DMoney · 3 · Last reply by Tomasz Wasiewicz

    To reproduce, add MS_Description to a table or column in SSMS and then run "Update Documentation."  the schema compare does not notice the change and doesn't update the descriptions.  We are trying to keep MS_description maintained in the DACPAC as the source of truth and surface it via DataEdo. This is an issue if we have to remove objects from the Dataedo repo and reimport.

  • 0

    Error logging with cmdline execution

    rromanczuk · 8 · Last reply by Piotr Tokarski

    Hello,

    We are having issues with an automated job to handle importing and exporting. When it errors, the log file is fairly unhelpful beyond acknowledging there was an error and which database was being processed. It's not clear if it was related to a module, table, procedure, etc.. Is there any configuration that can be changed to increase the level of information provided? Here's an example:

    [2018-03-14 21:35:29] Processing file: update_ALPHA.dataedocmd (C:\W\dataedo\update_ALPHA.dataedocmd).

    [2018-03-14 21:35:29] Update: ALPHA@de***********.com => dataedo@b*********01 [2018-03-14 21:36:55] 3627 objects found: 0 objects synchronized, 0 objects unsynchronized, 3462 objects new, 23 objects removed, 142 objects ignored. [2018-03-14 21:36:55]

  • 0
    Acknowledged

    Objects with same name, different case ('TABLE' and 'table')

    Piotr Tokarski · 0 · Posted

    By default, Dataedo repository is created as a case insensitive database, and most comparisons are run as case insensitive.

    This may cause issues, if your DBMS supports having two objects of the same type, with the same name but in different case (eg. two tables named 'TABLE' and 'table').

    We don't recommend using naming objects this way, but if it's impossible to avoid and causes issues for you, please post here or contact us at support@dataedo.com

    [Originally posted on Flarum on 2018-03-15 11:52:19]
  • 0
    Solved

    Export error: Object reference not set to an instance of an object.

    Piotr Tokarski · 1 · Last reply by Piotr Tokarski

    Some of our users ran into an error in export wizard that causes a crash with message mentioning templates and null reference, for example:

    Error while searching for templates. Object reference not set to an instance of an object. System.NullReferenceException: Object reference not set to an instance of an object.

    We're still looking into the cause of this issue, but it seems that removing a folder containing custom templates (path below) solves the problem: %USERPROFILE%\documents\dataedo\templates

    If you run into this issue if possible please zip the entire folder and send it to us before deleting it.

    [Originally posted on Flarum
  • 0
    Acknowledged

    Renamed SQL objects

    loosleef · 3 · Last reply by Piotr Tokarski

    Found a little bug with SQL objects that were renamed via sp_rename but the object name was not actually changed. This was being thrown as an exception in MetadataServer.FillUsedBy (possibly others, just where we saw it)

    I needed to run this script in order for the editor & export to continue to run (in this case the procedures were for debugging only and can be discarded)

  • 0
    Solved

    V6 - custom template not copied

    Luc · 2 · Last reply by Piotr Tokarski

    When exporting to html and choosing a custom template, the custom files (i.e. user.css) are not copied into the generated folders. I only tested user.css, don't know for the other files.

    V5 - ok V6 beta 2 - ko

    Luc

    [Originally posted on Flarum on 2017-11-21 13:24:19]
  • 0
    Solved

    Missing PKs

    Jon · 5 · Last reply by Piotr Tokarski

    When importing a database with multiple columns as the primary key, it appears that only the last column is being flagged as a PK unless all the PK columns are defined one after the other.

    For example, in this case both Column1 & Column2 are being reported as primary keys in Dataedo: Column1 (PK) Column2 (PK) Column3

    But in this case only Column3 is being reported as a primary key: Column1 (PK) Column2 Column3 (PK)

    [Originally posted on Flarum on 2017-12-06 00:32:34]
  • 0
    Solved

    Export broken due to incorrect dependency on CROSS APPLY

    loosleef · 6 · Last reply by Piotr Tokarski

    Awesome job on this product! Evaluating for purchase for my company (using 6.0 beta for cross-DB relation feature), and the only issue that I'm running into is when I import some stored procedures if they have a CROSS APPLY to a XML .nodes() the alias is being determined to be a dependency, which then I believe is causing the export feature to throw an exception. (?)

    To reproduce, the source SQL needs to be something like:

  • 0
    Solved

    V6 - user-defined relations not preserved with forced reimport

    Luc · 4 · Last reply by Luc

    When updating documentation with a forced reimport:

    V5: any user-defined relation in an ERD is preserved ( = OK) V6: all user-defined relations in an ERD are deleted (=bug)

    [Originally posted on Flarum on 2017-10-26 12:31:38]
  • 0
    Solved

    Missing Dependencies?

    rsliva · 7 · Last reply by Piotr Tokarski

    I'm missing some dependencies in 5.2.10. For example, I have a simple procedure:

    CREATE PROCEDURE dbo.CallDetail_ETL_Create_ReportingDetail_Pre ( @maxdt Date = null ) AS if @maxdt is null return DELETE FROM ReportingDetail WHERE StartDate >= @maxdt

    When I look at the dependencies for procedure CallDetail_ETL_Create_ReportingDetail_Pre, I see the table ReportingDetail. When I look at the dependencies for the table ReportingDetail I see nothing. I was expecting to see the procedure. In fact there are 6 procedures that reference that table.

    (Also, in 6.0.0 beta I'm seeing almost no dependencies at all in either direction. I tried documenting hundreds of tables, views