Skip to main content
Question

Seismic Lists and SQL Queries

  • June 4, 2026
  • 2 replies
  • 337 views
carolineloughman
Forum|alt.badge.img

We want to clean up one of our Seismic Lists to remove unnecessary columns. This List is connected to a SQL query which was set up by Seismic during onboarding several years ago. To test what is possible to achieve on our own, I deleted one low-risk column from the List by clicking "Update" to open “Column settings” and then deleting that row. This action successfully updated the data source version to the next major version.

I'm wondering if I should be able to delete the JD column from the SQL query as well and if that will mess anything up. 

2 replies

J
Forum|alt.badge.img+1
  • Jack
  • Richter
  • June 5, 2026

Hey Caroline, 

 

I think we would need more information about your database, data sources, and the use case that the query was set up for originally potentially? 

 

Check out documentation here: 

SQL database data source

Seismic List Data Source

I would also see if anyone on your Seismic account team has any records or email threads from when this was all set up in your tenant, if none of your team does anymore. 

:)
Jeremy Roman
Forum|alt.badge.img

Hi Caroline! You should be able to delete the column reference from your SQL without issue. In fact, if you have specific references to it in your SQL, leaving it in the code will return an error the next time you go to update it. I’d be happy to hop on a screen share to answer more specific questions about the risks and maybe share some additional tips/tricks to incorporate into your clean up process.

Terms & ConditionsAccessibility statement