It's time to get started with SnowConvert. On this page, you'll get an overview of the following topics:
Getting up and running with Mobilize.Net SnowConvert is quick and easy. Follow the instructions below. Before you get started, make sure that your system meets the requirements list here:
4GB of RAM (recommended)
120MB of Disk Space
If you encounter any issues in the download, installation, or setup process, let us know! Send a message to firstname.lastname@example.org. We'll get you up and running again.
You can download SnowConvert on the Mobilize.Net website. SnowConvert is still in a beta testing phase, but that is nearing completion. To access the Assessment Mode version of SnowConvert, fill out the form on the following webpage. Your download will begin immediately, and license information will be emailed to you shortly thereafter.
If you are interested in the full Conversion Mode of SnowConvert, fill out the form on the page below to talk with an engineer about what your needs are and how SnowConvert can accelerate your migration project.
If you've ever installed a windows application on your computer, this should be pretty straightforward.
Click on the downloaded exe file.
On the next screen, click on the install button.
The installer will setup all the required files in your machine (Note that you will not be asked to input license information until you launch SnowConvert for the first time.)
Once the installation finishes the tool can be started up immediately.
Mobilize.Net SnowConvert is an executable program file. Run it like any other Windows application. When you launch SnowConvert for the first time, it will prompt you for the license key. Contact email@example.com if you are looking to get a license or renew an existing license. If you have an issue with a current license, contact firstname.lastname@example.org for any questions related to problems with your license.
There are two types of licenses that are currently available:
Assessment Mode: When running SnowConvert with an Assessment mode license, you will be able to run an unlimited quantity of code through the tool, but you will only be able to view the output reports.
Full Conversion Mode: If you have a full conversion license, you will be able to run an unlimited quantity of code through the tool, and you will receive the output code (compatible with Snowflake) in addition to the assessment reports.
Before you start using SnowConvert, you'll have to extract your Teradata SQL Code, and put them in a file with any other Teradata extensions (BTEQ, Fastload, etc.) you may have. In order to do this, please follow these steps:
Go to Teradata's Generate DDL Wizard documentation.
Follow the instructions on extracting the SQL code using the Generate DDL Wizard.
Save the extracted .sql code into a folder. This folder will be referred to as the "Input Folder" in the conversion process.
As mentioned previously, once you have one folder with all of your .sql files, be sure to drop any .bteq, .fload, .fl, .mload, .ml, .tpump, or .tpt files that you may have into that same folder. The assessment and performance of SnowConvert is greatly enhanced by getting the maximum amount of your source code into the same folder.
There are alternatives to using the Generate DDL Wizard. Mobilize.Net has provided a few basic extraction scripts that you can tailor to your own needs. You can find them on our GitHub page. Feel free to reach out to email@example.com to learn more about additional extraction options.
When you first start Mobilize.Net SnowConvert, you will see the following screen (or one just like it depending on your target):
Each time you start SnowConvert, the program will check to see if you have any notifications. These will appear in the top right corner of the screen. If you do not have any notification, nothing will appear. The most common type of notifications that you will receive are listed below.
Mobilize.Net is constantly working to improve SnowConvert. If there is an update available, you will get a notification indicating that you may download the latest version. There will be an "Update" button in the notification, and you can download the newest version of SnowConvert by simply pressing that button. A download will automatically start. You do not need to enter new license information as that will be kept automatically. Once the download is complete, you will be prompted to run the installer. (You can see "Execute the Installer" above to learn more about installing SnowConvert.) The upgrade installation for SnowConvert will behave exactly as though you are downloading it for the first time, with the exception that you will not have to re-enter your license information.
When you launch the upgraded version of SnowConvert for the first time, it will prompt you to see the release notes about this latest version of SnowConvert. This will open your default browser and take you to the release notes section of our documentation site.
If you have a time-based license, you will receive notifications as you approach the end of your license period. These will come in three different stages:
The first notification will let you know that your license expires in 15 days.
The second will notify you when your license expires in 2 days.
You will get a final notification if you open SnowConvert and your license has expired indicating that you need to renew your license. Note that you will not be able to use the migrator if your license has expired.
You will be prompted to reach out to firstname.lastname@example.org by each of these notifications to renew your license.
If you are using a lines of code based license, you will not get a notification when you try to run the migrator indicating that the following run will exceed your maximum lines of code. As with the time-based license, you will be prompted to reach out to email@example.com to renew or upgrade your license.
If you're not interested in changing any of the default settings, you can start the conversion process by simply clicking on the "Let's begin" button in the center of the window. If you do want to configure any of the settings first, you can choose File (in the top left of the application) -> Settings. That will bring up the following screen:
Note that you can also reach this screen from the input/output folder screen (described in the next section). Once you have started the conversion process, you can not change any of these settings unless you restart SnowConvert.
There are three pages in the Conversion Settings Window:
DB Object Names
These pages are described in more detail below.
On the general page (as is shown above), there are three options you can select. Each is described below.
Generate debug log: This allows you to specify if you want a debug log to be written while SnowConvert is performing the conversion. Note that you will get a general conversion log and various reports each time you run the tool. The debug log is very detailed and can be helpful in working through any critical errors that may have occurred during the conversion process. This log is set to be generated by default, unless you change it here.
Comment objects with missing dependencies: SnowConvert can comment out dependencies that are not created in the source code or it can provide a comment in the output code that declares that a given dependency is missing. The default setting is to provide a comment declaring that a dependency is missing, but the code will still be converted. An example is given below with one single view created without the declaration of any dependencies (note that the below code is in Teradata, but the same applies for Oracle):
REPLACE VIEW VIEW1 AS SELECT * FROM TABLE1;
If you leave the default setting, this is the resulting code:
/**** WARNING: MISSING DEPENDENT OBJECT "table1" ****/CREATE OR REPLACE VIEW PUBLIC.view1ASSELECT * FROM PUBLIC.table1;
If you enable this option, then the resulting code will be:
/**** WARNING: MISSING DEPENDENT OBJECT "table1" ****//*CREATE OR REPLACE VIEW PUBLIC.view1ASSELECT*FROM PUBLIC.table1;*/
Note that SnowConvert uses an Abstract Syntax Tree (AST) to build relationships between each of the elements in the code you are converting. Due to this architecture, the more complete the codeset you put into SnowConvert, the more complete your output will be. As an example, if you have a table that is created in one .sql file and called in another, but you have not included the .sql file in the input folder... SnowConvert will still convert the input code, but will give you a "missing object warning" regarding the missing table as illustrated above. You could encounter some more serious errors if multiple dependencies are excluded, so please try to include the most complete version of your source code in the Input folder.
Set Encoding of the Input Files (Skip Auto Detection) SnowConvert tries to automatically detect the file encoding. However, it's not always possible to identify the correct encoding, and this can sometimes (rarely) cause an error. In such a scenario, you can manually select the file encoding for the files to process. Below are the encodings supported by .NET Core (the platform used to build SnowConvert):
Unicode (Big Endian)
Unicode (UTF-32 Big Endian)
Western European (ISO)
If you have input code that is saved with Western European (or any other encoding) and you specify a different encoding in the dropdown menu, then you may get an error similar to the one below:
To avoid an error like the above, ensure that you've selected the correct encoding (if you are selecting an encoding at all).
On this page, you can set database or schema names that can be applied to the objects that are converted by SnowConvert. This looks slightly different for Teradata vs. Oracle, so both are described below.
Customize Names (in SnowConvert for Teradata): Since Snowflake uses the DATABASE.SCHEMA.OBJECT naming convention and Teradata generally uses the DATABASE.OBJECT naming convention, you can specify a value for the Schema that you are importing into Snowflake. If you'd prefer the Teradata database name to be used as the schema name, then you can specify a database name to be applied to the Snowflake output instead. An example is given below with a couple of tables created and a view built off of those tables:
CREATE MULTISET TABLE TABLE1(COL1 NUMBER);CREATE MULTISET TABLE MYDB.TABLE2(COL1 NUMBER);REPLACE VIEW VIEW1 ASSELECT * FROM TABLE1UNION ALLSELECT * FROM MYDB.TABLE2;
If you specify a Schema Name
MyMobilizeSchema, you will get the following converted code
CREATE TABLE MyMobilizeSchema.TABLE1(COL1 NUMBER(38, 19));CREATE TABLE MYDB.MyMobilizeSchema.TABLE2(COL1 NUMBER(38, 19));CREATE OR REPLACE VIEW MyMobilizeSchema.VIEW1ASSELECT * FROM MyMobilizeSchema.TABLE1UNION ALLSELECT * FROM MYDB.MyMobilizeSchema.TABLE2;
And, if you specify a Database name
MyMobilizeDb, you will get the following converted code
CREATE TABLE MyMobilizeDb.PUBLIC.TABLE1(COL1 NUMBER(38, 19));CREATE TABLE MyMobilizeDb.MYDB.TABLE2(COL1 NUMBER(38, 19));CREATE OR REPLACE VIEW MyMobilizeDb.PUBLIC.VIEW1ASSELECT * FROM MyMobilizeDb.PUBLIC.TABLE1UNION ALLSELECT * FROM MyMobilizeDb.MYDB.TABLE2;
Customize Names (in SnowConvert for Oracle): Coming Soon!
On this page, you will find several options to help customize some of the formatting of your conversion. As with the previous page, this looks slightly different for Teradata vs. Oracle, so both are described below.
Format Conversion Settings (in SnowConvert for Teradata): In Teradata, there is a feature of explicit cast conversion where one expression can cast from one type to another type. For some explicit casting where the code doesn't indicate the format, Teradata uses default formats in order to parse the given cast value. However, some Teradata users may modify the default formats globally, so in this case, SnowConvert also provides you to specify those default formats.
Example for default Timestamp format: (default is YYYY/MM/DD HH:MI:SS )
-- TeradataSELECTCAST('2007-12-31 23:59:59.999999' AS TIMESTAMP(6) WITH TIME ZONE)FROM TABLE1;-- SnowflakeSELECTTO_TIMESTAMP_TZ('2007-12-31 23:59:59.999999', 'YYYY/MM/DD HH:MI:SS'),FROM PUBLIC.TABLE1;
Example for Character to Number default scale: (default is 10)
-- TeradataSELECTCAST("123.233" AS FLOAT FORMAT 'ZZZ.Z') FROM TABLE1;-- SnowflakeSELECTTO_NUMBER("123.233", 38, 10) FROM TABLE1;
Example for default Date format: (default is 'YYYY/MM/DD')
-- TeradataSELECTCAST(DATE_TYPE AS VARCHAR) FROM TABLE1;-- SnowflakeSELECTTO_VARCHAR(DATE_TYPE, 'YYYY/MM/DD') FROM TABLE1;
Example for default Time format: (default is HH:MI:SS)
-- TeradataSELECTCAST(TIME_TYPE_COLUMN AS VARCHAR) FROM TABLE1;-- SnowflakeSELECTTO_VARCHAR(TIME_TYPE_COLUMN , 'HH:MI:SS') FROM TABLE1;
Format Conversion Settings (in SnowConvert for Oracle): Coming Soon!
While not a separate page, the reset settings option appears on every page. If you've made changes, you can reset SnowConvert to it's original settings. When you select this option, you will be prompted to reset the settings on only this page or every page in the configuration settings.
The help menu can be found in the top left corner of the SnowConvert screen. When you choose the help menu, you will get the following options.
The user guide is this documentation site that you are reading right now. By clicking on "User Guide", your default browser will open and you will be taken to the documentation site for SnowConvert.
This will give you information about your license, and will allow you to change or update your current license. It will also let you know who the license is registered to, what execution mode this license is available for (assessment or full conversion), and when the license expires.
SnowConvert should check for updates every time it starts up. However, if you're not sure whether or not you have the latest version, you can select this option and the program will check for updates. If an update is available, you will be given the option to download it. If there are no updates available, you will get a brief message indicating that "you're up to date!"
This will take you to the terms and conditions page of the Mobilize.Net website. Brace for some legalese, but if you're looking for the terms and conditions of use for this product, look no further.
Finally, this will give you some basic information about the version of SnowConvert that you are currently running, including what version of the application you are currently running and what version of the conversion core the application is using. Sometimes there are updates to the conversion core and not the rest of the application. That should be illustrated here.
Alright... enough with the settings. Let's move on and take a look at the conversion process; how SnowConvert actually works.
So how do you use SnowConvert? Follow the step below on the conversion process, which will walk you through the inputs you will have to provide SnowConvert and the processes that SnowConvert goes through internally.
When you first launch Mobilize.Net SnowConvert, you'll see the welcome screen shown above.
If you select "Let's Begin" in the middle of the screen, you will be taken to the following screen where you can specify the input and output folders for your conversion.
Input Folder: Your Input folder is the folder where you should place all of the files you are looking to convert. Recall that to get the most value out of your conversion with SnowConvert, you should attempt to include all or as much of the source code as possible in the input folder. You can either click on the browse button or type the path manually.
Output Folder: The output folder is the folder you would like SnowConvert to output the logs, reports, and output code from the conversion process. This will all be output in this folder. Note that each of the filenames for the converted code will be the same as they were in the source code. If you had a tables.sql file in the source code, this will be output to a tables.sql file in the output folder. If you have a bteq or other filename, they will be converted to python. For example, if you have a tables.bteq file, that filename will be converted to tables_bteq.py in the output folder. You should get the same number of code files in the input as you do in the output, plus the reports folder, the logs folder, and the snowconver_helper.py code file that is generated if you had any bteq files in the source file.
Note that for both the input and output folder, the program will validate the input and the output directories that you've selected. The following validation checks will be done:
To determine if there are "convert-able" files in the input directory.
If there are already files in the output directory, you will get a message once you hit "Start Conversion" that will ask you if you'd still like to proceed with the conversion.
If one or both of the filepaths are invalid, you will get a message indicating so.
Once you have declared both an input and an output folder, you can select "Start Conversion", and SnowConvert will begin the transformation. The icon with the gear next to the "Start Conversion" button takes you to the same configuration settings page that is described above.
Once you begin the conversion process, there are three different conversion states that will be updated on the following screen.
Note that you will also get a readout of how many files are being converted, and the total size of the source files.
Mobilize.Net SnowConvert's conversion tasks are divided up as follows:
Loading Source Code: The files inside the input folder are loaded into the migrator. The migrator analyzes the input and prepares to parse through the source code. If there are any errors in loading the files, there will be .
Converting Source Code: The conversion process begins and produces some metadata about the loaded files including the size and quantity of the files reported on the screen. While the conversion process is taking place, SnowConvert is building a complete AST and a complete symbol table to properly create functional equivalence on the output code.
Writing Converted Code and Reports: This final state let's you know that the conversion process is complete, and the application is creating the output code and reports to populate the output folder.
During each stage, the cards depicting each stage on the screen will change color to indicate what is currently taking place. The blue stage with the loading icon shows that the state is executing. The green stage with the check icon shows that the state was successfully executed. Finally, if you encounter a red stage with an X icon, that indicates that something went wrong while executing that specific task.
Once the conversion has finished, the "Next" button will be available in the bottom right of the screen. On the next screen, a short summary will be available with some summary statistics about the conversion that just took place.
Included on this screen are the following:
Total Files: The number of files that were processed by SnowConvert during this conversion.
Total Issues: Number of warnings and errors that were generated by "SnowConvert while converting this set of files. You can learn more about issues and errors by visiting our page on Issues and Troubleshooting.
Total Parsing Errors: The number of conversion elements that were not converted due to the parser not being about to process a specific object or element. Again, you can learn more about issues and errors in SnowConvert by visiting our page on Issues and Troubleshooting.
Conversion Time: The actual time it took to convert these files.
Conversion Speed: The speed in lines of code per second that SnowConvert was able to convert the source code. The number listed is the number of source code lines of code converted each second.
LOC Conversion Summary: A summary giving you the percentage of total lines of code that were successfully converted by SnowConvert. The following details are covered in the summary:
Lines of Code (LOC): The total number of lines of code that are in the source code files.
LOC Conversion Percentage: The percentage of the total lines of code (given above) that were successfully converted by SnowConvert.
Object Conversion Summary: A summary giving the percentage of total objects converted by SnowConvert. An object in SnowConvert is generally given as a table, view, procedure, macro, or join. Some objects are within another object, but this count will be of all total objects. You can find more information in the reports about the type of objects that were found in the source code. This is described in more detail below under reports. The following details are covered in this summary:
Objects: The number of objects detected in the source code. Objects could include, tables, views, joins, procedures, and macros.
Object Conversion Percentage: The percentage of the total objects (found above) that were successfully converted by SnowConvert.
After the statistics, there are a few options for examining the output. You can click on one of the following options:
View Reports: If you click on view reports, SnowConvert will take you to the reports file in the output folder that you specified before the conversion. This folder was created by SnowConvert during the "Writing Converted Code and Reports" section of the conversion process. The following reports are generated by SnowConvert:
Assessment Report: This is the report that has all of the details regarding your conversion, and lays out how much work will still be required to complete the migration. A more detailed explanation on the assessment report is coming soon.
There are also 4 csv files that are included in the reports folder:
Assessment: This csv file contains all the raw data used to build the assessment report.
Details: This file contains the data on which elements were observed by SnowConvert in the conversion process. These elements include things like CREATE TABLE, INNER JOIN, HAVING, etc... any keywords that are recognized by Teradata. Each element will be categorized by the filetype and the top level object (such as table, view, procedure, etc.). There is also a count of each element included in the file.
Issues: This may be the most critical report. SnowConvert collects each issue found in the conversion, lists the severity level of each issue, and gives you the exact location in the source code of where that issue took place. If you're interested in what went wrong with the migration, visit the assessment report, and immediately come here. For more information on issues in SnowConvert, visit our page on Issues and Troubleshooting.
Summary: This csv contains some additional data used to complete the conversion.
View Logs: Clicking on "View Logs" will take you to the folder containing the two log files. (Note that if you changed the configuration settings to not output the debug log, you will only receive one log in this folder.) The logs are text files that contain timestamped entries that illustrate the process that SnowConvert has gone through. If there is a critical error, the logs will be the best place to troubleshoot what went wrong, and exactly when did it go wrong. The two logs in this folder:
Errors Log: The errors log contains all of the parsing errors that were encountered by SnowConvert during this run of the program. note that these can also be found in the issues report.
Conversion Log: The conversion log is always included in any run of SnowConvert, and contains timestamped information related to the conversion process in addition to the information found in the errors log.
Debug Log: The debug log contains all the same information as the conversion log, but also includes much more detail. This log will only be generated if you choose to generate it in the configuration settings. note that the debug log will be considerably longer (and a large file size) than the others, but it can be helpful to pinpoint the moment a critical error has occurred.
View Output: The "View Output" button will take you to the output folder. In the output folder, you will also see the tow folders listed above: reports and logs. These are the same folders that are linked to above by the "View Reports" and "View Logs" buttons. However, the output folder also has all of the converted code that is output by SnowConvert. Note that each source code file will have an output file of similar (and equivalent) name in this folder that contains the output code.
Start Over: This button will close and restart SnowConvert. The migrator will need to reset between runs, so this is required if you want to run SnowConvert again... even on the exact same workload. It is not required to use this button, however. Closing SnowConvert and restarting it from your desktop will have the exact same effect.
In this section you are going to see possible errors that may show up in the SnowConvert application and their cause. Note that these are not errors with the parsing or conversion of the code. All parsing and conversion errors and warnings are described in the Issues and Troubleshooting section of this documentation.
The following types of errors are going to be the most common.
On step 1 of the conversion process, you have to declare an input and output folder for the conversion. You could receive one of the following error messages below the pathway if there's an error with the chosen input/output folder.
If you type an invalid filepath or don't browse to a folder in either the input or output directory, you will get a short error in the window asking you to "Please enter an input [or output] path."
Resolution of this error is pretty simple, you have to type a path that exists or choose a folder in the browse menu.
If you choose a folder that doesn't have any files that can be converted by SnowConvert, then you will get the following error message: "Input folder must contain .sql .bteq .btq .fl .fload .ml or .mload extensions."
Resolution of this error requires you to choose a directory that has one of the given file extensions.
If you choose a pathway that contains an invalid character, you will get the following error message: "The path must have the valid format (Can't contain / : * ? " < > |)."
You will need to choose a folder that has a valid file path and doesn't include any invalid characters.
A warning will come up when you try to execute SnowConvert and the output folder is not empty. This will not come up when you attempt to write an input/output folder name, but rather when you click "Start Conversion". The warning looks like this:
You can click the cancel button and select another folder or proceed with the risk of potentially overwrite certain files. If the output of SnowConvert is writing a filename that is already in the output folder, the file that is already there will be overwritten.
In the conversion process you are going to see if a state has an error, in case some state is valid the next button is going to be available.
When you try to see the reports summary and it has errors you are going to see an incomplete conversion page and a button to open the log folder containing the reports.
If the system crashes, you are going to see the "Something went wrong" message. In this message, you will be given the option to send an email to Mobilize.Net of this error report in order for the SnowConvert team to improve the tool.