SQL

  • 24 May

    SSL Security Error on SQL-Source for MSSQL in Limagito File Mover

    User: It seems that we started to receive a connection error by SQL-source which should connect to a Microsoft SQL Server recently.

    This is the error message:

    TFDPhysMSSQLConnection DB SQL Exception: [FireDAC][Phys][ODBC][Microsoft][ODBC SQL Server Driver][DBNETLIB]SSL Security error

    Open Database Exception [FireDAC][Phys][ODBC][Microsoft][ODBC SQL Server Driver][DBNETLIB]SSL Security error

    I googled a little and found out that it might have something to do with the fact that SQL Server now uses TLS 1.2 as standard

    A: We adviced the user to switch from MSSQL to ODBC as ‘Database Vendor’

    Limagito File Mover SSL Security Error ODBC

    .. and asked them to check the following link:

    ssl-security-error-for-microsoft-sql-driver

    Limagito File Mover SSL Security Error

     

    We received the following feedback:

    • Installed recent ODBC Driver for MSSQL 17 to the Server where Limagito File Mover is running.
    • Created System-DSN for specific Database with that newest ODBC-Driver.
    • Switched settings in Limagito Rules to ODBC.
    • >> Seems to work!

    #FileTransfer

    If you need any info about this error, please let us know.

    Best regards,

    Limagito Team

  • 04 Dec

    Export Chinese Text Data from SQL server database to CSV file

    Q: I want to export Chinese Text data from an SQL server database to a CSV file. Setting up the Limagito rule was simple: SQL input and an output directory. I am actually using an SQL Select because the data that I want to export results from a join. Unfortunately the exported file is in ANSI encoding. Since my SQL Server source has nvarchar fields, some of them with Chinese text in them, I cannot use the CSV. Is there any way to tell Limagito to output CSV from an SQL Server source as UTF-8?

    A: We had to add some new options in version v2020.12.4 to achieve this.

    We added a basic example to get you started:

    Added SQL as Source

    Limagito File Mover SQL as Source

    We’ll be using a simple QRY to get all the date from a database table:

    Limagito File Mover SQL as Source Select Statement

    We are using a MS SQL Database, connection Setup:

    Limagito File Mover SQL as Source database setup

    Some info about the Database table (Demo_10

    ) we’ll be using:

    Add the query, simple seclect all statement:

    Limagito File Mover SQL as Source Query

    Important, Add the encoding you need. In this example we added UTF-8.

    Limagito File Mover SQL as Source Common options

    Destination Setup, WIN as Destination:

    Limagito File Mover WIN as Destination

    Destination File Result:

    Limagito File Mover SQL to Csv File

    RunTime Log Result:

    Limagito File Mover SQL to Csv RunTime Log

    If you need any help with this ‘Export Chinese Text Data’ question, please let us know.

    Best Regards,

    Limagito Team

    By Limagito SQL , ,
  • 25 Jun

    SQLite ERROR: database disk image is malformed

    2020-06-24 13:57:08.764 [WINGET] CheckQrySelect Exception: [FireDAC][Phys][SQLite] ERROR: database disk image is malformed

    One of my moving rules is logging a SQLite error. Some files are processing, but the error was discovered because a select few files aren’t moving. I’m not sure that these failures are related to the error message. The files in question aren’t listed in the log. The rule seems to load OK, as does the file memory database. I’m not sure where else to look.

    Q: Can you help me track down the database and resolve the error?

    A: This is the first time we received feedback about this error message. It seems the File memory database file is damaged.

    We googled a bit and decided to share this in a post.

    1.- First we installed the latest (free) version of sqlitebrowser

    2.- Check your settings directory. The File Memory file starts with LimagitoX.MemXY.sqlite where XY is the ID of the Rule.

    In the example the Rule has ID120 so the File Memory Database file will be LimagitoX.Mem120.sqlite

    LimagitoX File Mover Rule ID

    LimagitoX File Mover Settings Directory File Memory Database File

    3.- Copy the damaged File Memory database file first and open it with the installed SQLiteBrowser tool

    4.- When opened select Tools > Integrity Check

    SQLiteBrowser Integrity Check

    5.- Click OK to start the Integrity Check

    6.- We’re getting error messages so it seems the File Memory database file was damaged. Normally we should get an OK message only.

    7.- Export the content of the damaged database to a temporary SQL File. You’ll be asked to name this SQL file (any name is ok).

    SQLiteBrowser Export

    8.- The File Memory database only contains one table, tblFileMemory

    9.- Exporting ..

    10.- Export completed

    11.- Restart SQLite Browser Tool and select Import, Database from SQL File. Select the SQL file you exported in step 7.

    SQLiteBrowser Import

    12.- Now you’ll have to set the filename of this new database. It must be the same as the damaged database file. You’ll have to replace this file later.

    13.- Import completed

    14.- To be sure we did an integrity check on this new database file, result OK

    15.- Finally you’ll have to replace the new File Memory database file with the damaged one. You’ll have to stop the LimagitoX Application or Service because the damaged File Memory database file will be locked as long as our File Mover Application or Service is running.

    If you need any help with the ‘database disk image is malformed error’, please let us know.

    Best Regards,

    Limagito Team

    By Limagito Error SQL ,
1 2 3 4