Logo Tiger ERP Integration
Connect your Logo Tiger ERP to sync materials, orders, invoices, and more via direct MSSQL connection
Overview
Logo Tiger is one of Turkey's most widely used ERP systems in manufacturing. Talos connects to your Logo Tiger database via a direct MSSQL (Microsoft SQL Server) connection and reads your ERP data in real time — no middleware, no API licenses required.
For companies running Logo Tiger 3 or Logo Wings with the Logo Objects license, Talos also supports the Logo REST API on port 32001, enabling bidirectional operations including write-back capabilities.
What You Need
- Your SQL Server IP address or hostname (the machine running Logo Tiger's MSSQL database)
- MSSQL credentials — username and password (typically the 'sa' account or a dedicated read-only user)
- The database name (e.g. LKSDB, TIGERDB — varies by installation)
- SQL Server port (default: 1433)
Step 1 — Find Your SQL Server
You need the IP address of the machine running your Logo Tiger SQL Server. There are several ways to find it:
- Use the Talos AI assistant: ask "scan my network for MSSQL servers" — Talos will use talos_demo_scan to discover SQL Server instances on your local network.
- Check your Logo Tiger client configuration — the server address is usually visible in the connection settings when you log in to Logo.
- Ask your IT administrator — they can provide the SQL Server IP, database name, and credentials.
Tip: If Talos is running on a different network than your Logo server (e.g. cloud-hosted Talos agent), you will need VPN or Tailscale subnet routing to reach the SQL Server.
Step 2 — Get Database Credentials
Contact your Logo administrator or IT department to obtain the following connection details:
| Field | Typical Value |
|---|---|
| Username | sa or a dedicated read-only account |
| Password | Set by your SQL Server administrator |
| Database Name | LKSDB — varies by company; check Logo server config |
| Port | 1433 (default MSSQL port; rarely changed) |
Tip: For security, we recommend creating a dedicated read-only SQL user instead of using the 'sa' (system administrator) account. Your DBA can grant SELECT-only access to the Logo tables.
Step 3 — Connect in Talos
- Log in to the Talos dashboard as an admin
- Go to Settings → ERP tab
- Select Logo Tiger as your ERP type
- Enter your SQL Server connection details
- Fill in the fields below:
| Field | Value | Example |
|---|---|---|
| Host / IP | SQL Server IP address or hostname | 10.0.0.77 |
| Port | SQL Server port (default 1433) | 1433 |
| Database | Logo database name | LKSDB |
| Username | SQL Server login user | sa |
| Password | SQL Server login password | •••••••• |
- Click Test Connection. Talos will attempt to connect to the SQL Server and verify access to the Logo tables.
Step 4 — Auto-Discovery
After a successful connection test, Talos automatically scans the database to detect your Logo configuration:
- Firm numbers are detected from Logo table prefixes (e.g. LG_001_, LG_002_). Each firm number corresponds to a separate company within Logo.
- Period codes (fiscal year segments) are discovered automatically. Logo uses period-based table partitioning for transactional data.
- Select which company (firm number) you want to sync. If you have multiple firms, you can configure each one separately.
Talos reads the table structure to determine which firm/period combination contains your active data. No manual table configuration is needed.
Step 5 — Start Sync
- Click Sync Now on the ERP settings page. The first sync may take a few minutes depending on your data volume.
- Once the initial sync completes, Talos automatically syncs twice daily (06:00 and 18:00 UTC). You can also trigger a manual sync at any time from the dashboard.
- Monitor sync progress in real time from the Synchronization tab. Each sync run shows entity counts, duration, and any errors.
What Gets Synced
Talos reads 9 entity types from your Logo Tiger database. Each entity is deduplicated by a unique key and updated incrementally using SHA-256 hashes to minimize unnecessary writes.
| Entity | Talos Table | Dedup Key | Frequency |
|---|---|---|---|
| Materials | materials | code | 2x daily |
| Recipes (BOM) | recipes | recipeCode | 2x daily |
| Sales Orders | salesOrders | orderNo | 2x daily |
| Production Orders | productionOrders | ficheno | 2x daily |
| Purchase Orders | purchaseOrders | purchaseId | 2x daily |
| Accounts | accounts | accountCode | 2x daily |
| Invoices | invoices | invoiceRef | Delta sync (hash-based) |
| Employees | employees | code | 2x daily |
| Currency Rates | currencyRates | currency | 2x daily |
Advanced — REST API (Logo Tiger 3 / Wings)
If your Logo installation includes the Logo Objects license (Tiger 3 or Wings), Talos can also connect via the Logo REST API for extended capabilities:
- REST API runs on port 32001 by default and exposes 142 endpoints covering all Logo entities
- Enables write-back operations — create and update records directly in Logo from Talos
- Supports real-time queries without direct SQL access, useful for hosted/cloud Logo deployments
- Requires a valid Logo Objects license — contact your Logo dealer to verify your license includes REST API access
Note: The REST API is optional. The direct MSSQL connection is sufficient for read-only synchronization and works with all Logo Tiger versions.
Security
- Talos connects to Logo in read-only mode by default. No INSERT, UPDATE, or DELETE queries are ever executed against your Logo database.
- SQL credentials are stored encrypted and are never exposed in the dashboard after saving.
- All SQL queries executed by the sync agent are logged and auditable from the Synchronization tab.
- Network access can be restricted to specific IPs using your SQL Server firewall rules. We recommend allowing only the Talos agent's IP.
Troubleshooting
| Problem | Solution |
|---|---|
| Connection refused / timeout | Verify the SQL Server IP and port are correct. Check that SQL Server is running and accepting TCP/IP connections (SQL Server Configuration Manager → Network Configuration → TCP/IP must be enabled). |
| Login failed for user | Verify username and password. Ensure SQL Server authentication mode is set to "Mixed Mode" (Windows + SQL auth). SA account may be disabled by default. |
| Database not found | Check the exact database name in SQL Server Management Studio. Common names: LKSDB, TIGERDB, LOGOMUHASEBE. The name is case-insensitive. |
| Firewall blocking connection | Open port 1433 (or your custom SQL port) in Windows Firewall on the Logo server. For cloud agents, ensure VPN/Tailscale subnet routing is configured. |
| Sync runs but some tables are empty | Check the firm number and period code. Data may be in a different firm (LG_002_ instead of LG_001_) or an older period. Verify in the Auto-Discovery step. |
| Connection works locally but not from Talos agent | The Talos agent may be on a different network. Set up Tailscale subnet routing or a VPN to allow the agent to reach your SQL Server's internal IP. |
Useful Links
- Logo Yazilim — Official Logo Yazilim website — ERP solutions for Turkey
- Logo Developer Docs — Logo developer documentation and API reference
- Logo Tiger ERP — Logo Tiger ERP product page — enterprise resource planning
- Microsoft SQL Server Documentation — Microsoft SQL Server documentation for database administration
- Tailscale Download — Tailscale VPN — secure network access for on-premise ERP servers
- Logo Tiger SQL Table Reference (GitHub) — Community Logo Tiger SQL table reference on GitHub
- Logo Tiger REST API Schema (GitHub) — Logo Tiger REST API schema reference on GitHub