Why not to use views in Sisense

Sisense works basically on importing all of your data into its Ecubes and then doing the processing which you require. It insists that it can act as your ETL provider too. But there are some issues which novices can be hit hard by. One of them is using views.
By using a view you have basically pushed the logic at your warehouse instead of at sisense. When you try to import a large table into Sisense its structure gets there within no time and then on, it will only consume your time when its time to load data. However when you try to upload a view with a large resultant volume, you will observe that it takes a lot of time to get the structure in your Ecube.
It can be irritating to sit in front of the idle screen for long and sadly there is no way to cancel it, pressing any buttons will crash the machine.

Exporting/importing Ecubes.

The first thing to remember is the difference between Ecube data and ecube structure.

Its the difference between .ecdata and .ecube data files- while the former contains the data from the last build of your cube, the latter is the structure of the cube you have created.

The second thing to remember is how to export. Based on your security settings there can be multiple ways to do this.  Data file- .ecdata are generally large and may require you to setup an ftp; however you can simply copy the .ecube files from one server and paste it on another.

Now you can open them from the sisense elasticube manager. Though you will have to build it again as its only structure and no data.