Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Contact Us
  • Home
  • Apps
  • Apps on Zapier

Common Problems with SQL Server (MSSQL) on Zapier

Written by Owner

Updated at August 20th, 2025

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Tables
    Work with tables Manage tables Create tables Troubleshoot Zapier Tables
  • Product updates
    Product updates: January 2023 Product updates: March 2023 Product updates: February 2023 Product updates: April 2023 Product updates: May 2023 Product updates: June 2023 Product updates: July 2023 Product updates: August 2023 Product updates: September 2023 Product updates: October 2023 Product updates: November 2023 Product updates: December 2023 Product updates: January 2024 Product updates: February 2024 Product updates: March 2024 Product updates: April 2024 Product updates: May 2024 Product updates: June 2024 Product updates: July 2024 Product updates: August 2024 Product updates: September 2024 Product updates: October 2024 Product updates: November 2024 Product updates: December 2024 Product updates: January 2025 Product updates: February 2025 Product updates: March 2025 Product updates: April 2025 Product updates: May 2025 Product updates: June 2025 Product updates: July 2025 Product updates: August 2025
  • Zaps
    Zap basics Zap history Troubleshoot Zaps Manage your Zaps Do more with Zaps
  • Your Zapier account
    Plans Billing Account profile Notifications Data privacy & security Get help User roles and permissions
  • Interfaces
    Troubleshoot Zapier Interfaces Create an interface Use interface components Manage interfaces
  • Canvas
    Create a canvas Collaborate on a canvas
  • Chatbots
    Add logic and knowledge to chatbots Troubleshoot chatbots Create chatbots Manage chatbots
  • Getting started
    Intro to Zapier Set up your Zapier account Use case templates
  • Agents
    Create agents Manage agents Troubleshoot agents
  • MCP
    Set up MCP
  • Built-in tools
    Filter & Paths Formatter Schedule & Delay Email, IMAP, SMTP, & Email Parser Webhooks & Code Storage, Digest, & RSS Sub-Zap & Looping Other built-in tools Custom Actions & API Requests Functions AI by Zapier & AI actions Copilot Human in the Loop
  • Lead Router
    Create routers
  • Apps
    Connect and manage your app connections AI apps on Zapier Apps on Zapier
+ More

Table of Contents

Some new rows didn't trigger my Zap Can't connect to my database I'm getting errors about DateTime conversions Unknown connection timeouts Login failed for user Garbled or otherwise incorrectly converted data coming from the trigger My trigger of New or Updated Row isn't picking up any of my updates

Some new rows didn't trigger my Zap

When using the following triggers:

  • New Row
  • New or Updated Row
  • New Row (Custom Query)

Each poll captures the 50 most recent rows. That means if more than 50 rows are added in a polling interval (depending on your plan), some data will be lost.

If you need to capture more than 50 rows at a time, you'll want to add them to your database in batches according to your plan's update time—no more than 50 records at a time per update period.

Can't connect to my database

Zapier only supports the newest version of SQL Server, and even then, minor driver problems can cause incompatibilities. Zapier has tested SQL Server app against Amazon AWS SQL Server 2008 R2 and 2010 RDS instances.

If you are using the latest version and still having difficulties connecting, refer to our can't connect to my database help article.

I'm getting errors about DateTime conversions

If you're using a DateTime column type and receiving errors about converting text into DateTimes, you should try using the date type or the datetimeoffset type.

Unknown connection timeouts

One known issue that has been reported by a number of our users occurs if you set up SQL Server and install a non-default instance (for example, a named instance). When this is done, the communication port is actually changed but SQL Server uses SQL Server Browser to relay messages to and from port 1433. For one reason or another, our app doesn't work well in this situation. Zapier recommends using the default instance for "the path of least resistance," but if that is not doable, you will need to make sure that TCP communication is enabled and that you have a static port set for the service.

Login failed for user

When attempting to connect to SQL Server, you may see the error message (ProgrammingError) ('42000', "[42000] [unixODBC][FreeTDS][SQL Server]Login failed for user 'username'. (18456) (SQLDriverConnect)") None None. This means there has been an issue with the encryption of the password connection string. To fix this issue, switch to a long alphanumeric password. Zapier recommends this tool for generating strong passwords.

Garbled or otherwise incorrectly converted data coming from the trigger

Currently, only UTF-8 encoding is supported. You will need to ensure your database uses UTF-8 encoding.

My trigger of New or Updated Row isn't picking up any of my updates

You'll need to specify ORDER BY by a date/time field such as date_updated or last_modified.

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • How to get started with Skool on Zapier
  • How to get started with Zoho Show on Zapier
  • How to use Stripe Payment Links with Zapier
  • How to get started with Feathery on Zapier
  • How to get started with Front on Zapier

Copyright 2025 – OBZ-Zapier.

Knowledge Base Software powered by Helpjuice

Expand