1 of 1 people found this helpful
You cannot "import" a SQL script file. You can use it in a SQL DB and then export as CSV (one per table) to be imported in to FileMaker.
I'm assuming data with the script, of course.
IF you only have the tables & columns, you can re-create (somewhat) the tables and columns using the script as a "map" to follow. But errors can be introduced, so the above method is preferable.
I work in MySQL, MS SQL and FileMaker DBs, so these are my recommendations based on experience.
IF you already have the data in SQL, you can Import (script step) if you have permissions and access directly to the SQL db with the correct ODBC driver(s). The Import script step allows you to create the table as you import the data.
2 of 2 people found this helpful
I agree with Beverly’s advice that if you have an existing SQL database that you want to recreate in FileMaker, it’s relatively easy to just import the data via ODBC (using the script step or manually via File->Import Records) and let FileMaker create the tables and fields along with each import.
FileMaker does support standard SQL statements such as CREATE TABLE and ALTER TABLE. You can send these statements to a FileMaker database via an ODBC client, a JDBC client, or via some FileMaker SQL plugins.
Here are two reference guides for details on setting up ODBC and JDBC connections and using all of the SQL statements that are supported by the FileMaker platform: