BiSA for Windows Documentation
Follow installation guide lines on http://bisa.sourceforge.net
BiSA for Linux/Mac Documentation
Restore database with SQL
RESTORE DATABASE bisa FROM DISK='c:\temp\BiSA_SQL_Server_database_backup0.95.bak' WITH NORECOVERY,
MOVE 'bisa_data' TO 'C:\Program Files\Microsoft SQL Server\MSSQL12.SQLEXPRESS\MSSQL\Data\bisa.mdf',
MOVE 'bisa_Log' TO 'C:\Program Files\Microsoft SQL Server\MSSQL12.SQLEXPRESS\MSSQL\Data\bisa_log.ldf' ;
Windows BiSA's import function for SQL Server is much faster than the PostgreSQL equivalent, for the reason that SQL Server supports Table Valued Parameters (TVP) which is an efficient way of inserting multiple records into a database no matter if database server resides on the same physical machine as that of the user front-end or deployed on a different networked machine.
PostgreSQL has COPY command that moves data between PostgreSQL tables and standard file-system files efficiently. In BiSA 0.92 version COPY is default way of importing datasets into database, however COPY can only import a file from a directory that is visible to the database server, so if PostgreSQL is hosted on a different machine than the web front-end then this will not work. A workaround of this problem can be achieved by mapping web front-end machine's datasets folder to the server hosting PostgreSQL. Then inject the COPY command by correcting the path of the file to be imported. Therefore the code in step1importkb.py needs to be modified to a user's specific environment.
Or comment out copySQL function and enable insertSQL function which is written to support various scenarios. Each line of the imported dataset file is inserted by a single insert statement which is a slower way of importing a large dataset into a database. However this works for both local machine databases and databases hosted on a different machine than the web front-end.