Jump to content
  • To Search the Seeq Knowledgebase:


Search the Community

Showing results for tags 'connector'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Community Technical Forums
    • General Seeq Discussions
    • Seeq Admin Forum
    • Training Resources
    • Product Suggestions
    • Seeq Data Lab
  • Community News
    • Seeq Blog Posts
    • News Articles
    • Press Releases
    • Upcoming Events
    • Resources


  • Seeq FAQs
  • Online Manual
    • General Information

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



About Me



Level of Seeq User

Found 4 results

  1. In Seeq's RXX.0.44.00 and later we now offer a connector to the NOAA Weather Service. This can enable your team to perform analysis for weather-dependent processes. For more information on this connector, please visit our Knowledge Base Article -- NOAA Weather Connector
  2. Prior to Seeq major version R20, the only way to bring in data coming from a SQL datasource into Seeq was through the SQL Connector V1. From major version R20 and beyond, Seeq created the SQL Connector V2 that features many improvements. For more information, please take a look at SQL Connectors. In order to gain the improvements from the new connector, admins may want to migrate their old SQL V1 connections to V2 and all of the Seeq calculations built from them. The steps below can be used as a rough guide for the steps needed. Please contact Seeq support if attempting to do this as different
  3. I have successfully setup two (MS SQL) condition queries in the SQL Connector V2 JSON file. When I add these conditions to a trend, the last capsule shows "In Progress" in the Capsules table although the SQL does return an end date for this capsule. The capsule at the top of the trend does end at the correct time, but it is hollow as if the capsule is in progress. Any help on this would be appreciated, Andrew
  4. Microsoft Access databases are contained in a (.mdb) file. To connect Seeq to this file, think of them like an Excel or csv file. The .mdb files must be continuously imported it into an RDBMS, most naturally MSSQL as it is in the Microsoft software family. After that, Seeq can connect to it via our SQL v2 connector. The .mdb file import can be scripted/automated/scheduled, but it is basically like bringing an arbitrary file into MSSQL. This link provides good instructions on the steps to import Access data into MSSQL: https://docs.microsoft.com/en-us/sql/integration-services/import-export
  • Create New...