SQL Server Connections
By default, SpeedBase connects to its built-in, file based database and does not require a server machine or installation of a server side software.
Starting from version 4.0 and above, SpeedBase supports connection to a remote SQL server so you may keep your database on an SQL server.
This option allows you to remotely connect to your SQL server from anywhere around the world via internet.
Before evaluating this option, make sure that you have reviewed all other available connection options given on this page
as this option requires more technical skills to setup and maintain.
- This options is available in SpeedBase version 4.0 and above.
- This option is available only if your license covers "SQL Server Connectivity" component, otherwise you may need to purchase it separately.
- You, or an IT professional in your company must have the necessary skills and technical knowledge to install, manage and backup your SQL server.
- You must have a running SQL server installation on a server machine which was configured to accept remote connections.
- Microsoft SQL server 2005 and above editions are supported.
SpeedBase does NOT install or manage SQL server software for you. It also does NOT backup your database on SQL server.
You must have the required skills and technical knowledge to install, manage your SQL server and deploy an appropriate backup solution.
Technical support is only provided for the issues that are related to SpeedBase product and does not cover sql server specific issues.
How to Switch to a SQL Server Database
Note that, even after migrating to SQL server, you may still choose to save file attachments to local data folder. This, however may complicate
backing up file attachments on a multiuser license as each user would then save files to the data folder on their own machine.
You are recommend to move your data folder to a shared network drive and update connection settings for the shared data folder location
on all machines before starting the migration.
Before you can start to use an SQL Server to manage your database, your current data
must be migrated to a new, empty database on your SQL server.
Follow the steps given below to setup SpeedBase to use your SQL server to access your database:
- While not mandatory, you are recommended to complete the initial design and customization of your database on your local computer
before moving it to your SQL server.
- Make sure that your SQL server is configured to accept remote connections.
- Open firewall settings of your server machine and make sure that the port numbers used by your SQL server are enabled.
- Open the management software of your SQL server and create a new database, also assign a user with full modification
rights to this database.
- Open "connection settings" window of SpeedBase, select "SQL Server" from "database type" selection box.
- Enter connection information and then click "Test Connection" to verify that SpeedBase is able to connect to your SQL server.
- Click "migrate" button to start the transferring of all your data to the SQL server. This may take some time depending on the
size of your data. Once finished, the database on your SQL server will be an identical copy of your local database.
- Save changes. All changes you make from now on will be done on the remote database on your SQL server.
- For multiuser connection, go to each of other client computers and just adjust the connection settings to connect to your SQL
server. Do NOT attempt to initiate the migration again.
Files are NOT migrated to SQL Server. If you have attached files to your records, they will still be accessed from your computer
or local network.
If for some reason you decide to redo the migration of your database, you must first delete the database created on your SQL server
and then create a new database.
If for some reason you decide to return to your local database, you may do so by adjusting the connection settings. Beware that
you may only return to the latest state of your local database just before the migration. It is NOT possible to migrate your current data in the
opposite direction i.e. from SQL server database to the local database.