Currently, the Upload Tool supports uploading only data in CSV (Comma Separated Value) file formats. As an alternative, you can export the Excel file into CSV file format and then upload the data.
Follow the steps below to export Excel files into CSV:
To upload the data of larger size, SkyDesk Reports Upload Tool splits the data and uploads as batches. The user can configure the number of rows to be sent for each batch by modifying the LINES_TO_SEND parameter in the common_params.conf file. By default this will be set to 5000.
Follow the steps given below to specify the batch size:
Yes, you can allow your shared users to upload data into your tables using Upload Tool. Follow the steps given below to do this.
Steps to be followed by you who is the Admin or Workspace Owner:
Steps to be followed by the shared user:
Yes, you can use Windows Authentication to connect to your SQL Server database and fetch the necessary records to be uploaded into your SkyDesk Reports account.
To do this, you need to provide the database name followed by the Windows domain name separated by semi-colon ' ; ' for the parameter DBNAME in thedatabase_connections_params.conf file.
<your_database_name> - This is the database name in SQL Server to connect
<your_domain_name> - The Windows domain name that you use.
Yes, you can upload data from remotely hosted databases (running in a remote machine) into SkyDesk Reports using Upload Tool, provided a network connection via Java Database Connectivity (JDBC) Driver could be established between the remote database server and the machine in which you have installed the Upload Tool.
The connection setting for the hosted database should be done in the same way as you do for a local database. For the "HOSTNAME" and "PORT" parameters, you need to specify the remote hosted database server IP address or host name and the corresponding port number. To know how to specify connection setting, refer to Specify Database Connection Settings section.
You can connect to a particular SQL Server Instance and upload the data into SkyDesk Reports Online Workspace by following the below steps, in addition to configuring the common and workspace connection configurations and SQL Queries.
Yes, it is possible to setup the SkyDesk Reports upload tool to fetch data from multiple database. By default, the Upload tool is designed to upload data from one database in an upload process. However, we can modify the configuration files and executable bat or sh files to upload data from more than one database.
To accomplish the above set up, you need to create different set of configuration files required for each database.
For example, let's say you have two different databases in SQL Server to be connected for data upload. We should have one set of configuration files for SQL Server Database One and another set of configuration files for Database Two.
If you are working on Windows environment you can download the modified sample configuration and batch (UploadFromDB.bat) files from this download link. Similar changes are required for the UploadFromDB.sh shell script if you need to set up these configuration on a Linux/Mac environment.
Follow the below steps once you have downloaded the sample and extracted the same.
The following are the steps to configure two databases in the Upload tool:
Configuration for SQL-Sever Database One:
Configuration2 for SQL-Server Database Two:
Once the above setup is done, execute the modified batch files copied to the bin directory. This will fetch data from both the databases in SQL Server and upload that into SkyDesk Reports.
You can follow the same model if you want to fetch data from different databases such as SQL Server and Oracle and upload that into SkyDesk Reports.
No. You can follow a different column names in SkyDesk Reports table from what is there in your local database and still upload data using Upload Tool. Follow the steps to upload the data from your local database into the corresponding column in SkyDesk Reports table.
The above query will pull the data from column1-local-db, column2-local-db and column3-local-db from your local database databasetable1 and import them into the column in column1-skydeskreports-table, column2-skydeskreports-table and column3-skydeskreports-table in the SkyDesk Reports table.
SkyDesk Reports Upload Tool expect the date format of the data being uploaded as dd/MM/yyyy HH:mm:ss. In case you are using a custom date format in your local database, then you need to convert your date value to the required format in your SQL SELECT Query using the DATE_FORMAT SQL function.
To convert the data format you need to set a date column to the DATE_FORMAT SQL function and specify the required default date format as given below.
In case your date column is set as string field, then you need to convert the data type using DATE function as given below.
Solution: This could be because of improper proxy server settings. If you are connecting the Internet through a proxy server, ensure that you have configured the correct proxy server details in the common_params.conf file. For more details, refer to the Setup: Common Settings and Proxy Configuration section.
Solution: This could be because, the default memory allocated to the Java Virtual Machine (which executes the Upload tool) in your machine was not sufficient to import a large file using our Upload Too. Hence it throws the "Out of Memory". Follow the given steps to resolve this issue:
Solution: To upload the data of larger size, SkyDesk Reports Upload Tool splits the data and uploads them as batches. It is important that the batch size should not exceed 50 MB or 500,000 records per batch. You can increase or decrease the lines/records to send for each batch in common_params.conf file.
Follow the steps given below to set the lines to be uploaded in a batch:
For more details, refer to #Q3.
Solution: You will get the above message when more than one import process is running on the same table at the same time. Ensure that no other user is importing into the same table before initiating the progress.
Solution: You will get the above error message when you have set the import type to UPDATEADD and have not specified any value for the SKYDESK_MATCHING_COLUMNS parameter. This parameter is mandatory when the SKYDESK_IMPORT_TYPE is set to UPDATEADD. Set this parameter to column names based on which the existing records in the table need to be matched. If the record already exists in the table then it will be replaced with the new values in the uploaded CSV file. Remaining rows will be added at the end of the table.
Solution: You will get the above error when the column specified for the SKYDESK_MATCHING_COLUMNS parameter is not available in the table. When you have set Import Type to UPDATEADD, it is mandatory to specify matching column. These columns will be used to check whether a record already exist in the table. Ensure that you have specified a valid column name for matching column before uploading data to avoid failure.
Solution : This error occurs when UploadFromDB.sh/bat file is executed from folder other than <Tool_Home>/bin/. Use the following method to execute the UploadFromDB.sh/bat file:
For Linux/Mac: UploadFromDB.sh <username> <password>
For Windows: UploadFromDB.bat <username> <password>
Solution: When you access the service a session will be created, which will be deactivated once you logout or after 7 days. If you did not logout or access the service from multiple locations then multiple active sessions will be created for your account. SkyDesk service restricts a user to have maximum of 20 active sessions. In case you have exceeded this limit, you will not be allowed the access the service. To overcome this you need to close the active sessions.
Follow the steps below to close the current active sessions.
Solution: This could be because the Column Delimiters (delimiter character which separates one column from another in the data ) was identified incorrectly. Follow the steps below to resolve this issue:
For more details on these parameters, click here.
Solution: This error occurs when the Upload Tool was not able to access the .mdb file that you have mentioned. Ensure that the file exists in the specified location and has proper Read permission.
This error could occur when the table in your local MySQL database, from which you are fetching data, contains a date column with 'NULL' value. When queried MySQL will return the value as '0000-00-00' by default. Since this is an invalid value, the MySQL JDBC driver will throw this error.
You can overcome this error using the database_connections_params.conf file available in the SkyDeskReportsUdToolconf. While configuring the local connection setting, in the DBNAMEspecify your database name followed by the ?zeroDateTimeBehavior=convertToNull& property. This will convert this invalid data and adds null value in the SkyDesk Reports table.