After building the IMP file the targitDB file is generated by the tiImport command line tool.
If you're taking advantage of the TARGIT InMemory Scheduler component the entire process is automated and you only need to deploy your project to the TARGIT InMemory Scheduler Service.
Should you want to execute an import script externally you can take advantage initiating the refresh of
either calling the tiImport application and reloading the data by using e.g. a batch file or if integrating
TARGIT InMemory Database into a Microsoft SQL Server solution a dedicated custom task is available as a
custom task called TARGIT SSIS InMemory Import SSIS Compoent.
On a typical on-premise solution for a medium sized company (~120GB of data) the import process will
typically run for 2 to 15 minutes, depending on the amount of data and performance of hardware. In our
experience this is a lot less than what you would expect when refreshing e.g. an analysis services cube.
When running the tiImport command it is important to notice that the output targitdb file will be created
with the same same name as the imp file.
After generation the targitdb file built must be moved to the TARGIT InMemory Database Data-folder and
loaded into memory with the tiLoad command.
A batch file automating the full process would typically be structure like this:
Note: the password that is being used is the one entered during the installation of the TARGIT InMemory
REM Create targitDB
"C:\Program Files\TARGIT\TARGIT InMemoryDB\tiImport.exe" c:\path_to_impfile\my_import.imp
REM Move targitDB to the TARGIT Folder updated database for the server
copy c:\path_to_impfile\my_import.targitdb "c:\programdata\targit\targit InMemoryDB\data\"
REM Reload the newly
"C:\Program Files\TARGIT\TARGIT InMemoryDB\tiLoad.exe" database=my_import;pwd=password /reload