SQL Server Help & Support
What SQL Server (MSSQL) Triggers and Actions are Supported?
- New or Updated Row - Triggered when a new row is added or modified.
- New Column - Triggered when you add a new column.
- New Row (Custom Query) - Triggered when new rows are returned from a custom query that you provide. Advanced Users Only
- New Table - Triggered when you add a new table.
- New Row - Triggered when you add a new row.
- Update Row - Updates an existing row.
- New Row - Adds a new row.
- Find Row via Custom Query - Finds a row in a table via a custom query you control.
- Find Row - Finds a row in a table via a lookup column.
How to Get Started with SQL Server (MSSQL)
SQL Server (MSSQL) is a bit tricky to get set up properly with Zapier. Our servers run Linux and we have a fickle driver stack to properly communicate with external SQL Service instances. In many instances, it is random whether or not a certain instance will work with Zapier. Here is a short list of compatibility if everything else is set up correctly:
SQL SERVER 2005 - NOT COMPATIBLE
SQL SERVER 2008, 2008 R2 - MAYBE COMPATIBLE
SQL SERVER AZURE - MAYBE COMPATIBLE
SQL SERVER 2012, 2014 - COMPATIBLE
SQL SERVER 2016 - COMPATIBLE
The first thing you can try is adding your SQL Service instance plain. Here is what that looks like:
Most importantly, you'll need to make sure your SQL Service instance is available outside your firewall to the IP address listed here.
If you are able to get your account added without errors (click the "test" button to see) -- congrats! Otherwise, we recommend you do the following, which has been previously tested and confirmed to work:
Set up and install an Amazon RDS SQL Server 2008 R2 instance here: http://aws.amazon.com/rds/sqlserver/
Use the connection detailed supplied when creating the Amazon RDS SQL Server instance on Zapier here: https://zapier.com/app/settings/authorizations/MSSQLAPI
We recommend using an external database like this because it is more secure than directly exposing your production database to the internet.
Common Problems with SQL Server (MSSQL)
Some new rows didn't trigger my Zap#
When using the "New Row" trigger, each poll captures the 50 most recent rows. That means if more than 50 rows are added in a polling interval (5 or 15 minutes 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—no more than 50 records at a time every 5 or 15 minutes (depending on your plan).
Can't Connect To My Database#
Database connections can be very fickle. Here are a few things you can re-check:
- What version is your SQL Server database?
Zapier only supports the newest version of SQL Server and even then minor driver problems can cause incompatibilities. Zapier has tested SQL Server integration against Amazon AWS SQL Server 2008 R2 and 2010 RDS instances.
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
Unknown Connection Timeouts#
One known issue that has been reported by a number of our users occurs if you setup 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 integration doesn't work well in this situation. We recommend 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 you have static port set for the service.
Login failed for user#
The error that commonly looks like
(ProgrammingError) ('42000', " [unixODBC][FreeTDS][SQL Server]Login failed for user 'username'. (18456) (SQLDriverConnect)") None None is a commonly a bug with our password connection string encoding - try switching to a long alphanumeric password - we recommend this tool for generating strong passwords.
Garbled or otherwise incorrectly converted data coming from the Trigger#
As of right now, we only support UTF-8 encoding. You will wish to ensure your DB is set to UTF-8 in order for us to work with the data.
Popular Things To Do With SQL Server (MSSQL)
Need More Help? - Our support team is happy to help -- send us a message