Booking Pro is supplied the Microsoft SQL Server 2005 Express which is a free of charge edition of Microsoft's SQL Server. This edition doesn't have the all of the features available in the full product and isn't as powerful, however, for Booking Pro it has proved to be more than adequate for the volume of data required and is just as reliable as a the full SQL Server product. Nonetheless we do recognise that some Organisations using Booking Pro may prefer to use the software with a full copy of SQL Server and under these circumstances we would recommend the following:

1. You install SQL Server as a separate instance called "bprsolutions".
2. You enable "mixed-mode" authentication and enter a password for the "sa" login. A record of this password should be kept in a secure place because if you lose this password our support engineers will not always be able to help you if you have a problem.
3. When you use Booking Pro to create a database you should select the "SQL Server Authentication" option (specifying a Username of "sa" and the password used in 2 above) in both of the following dialogs: Create new database and New settings.

Why do you recommend using a "bprsolutions" instance of SQL Server?

We recommend that you install a separate instance of SQL Server for Booking Pro for the following reasons:

1. Using a separate instance helps to isolate Booking Pro from other applications you might have running on SQL Server (e.g. SIMS) and reduces the risk of a support engineer recommending a change which inadvertently affects another vendor's software.
2. A separate instance helps to reduce the downtime experienced by Users of applications as it is possible to stop one instance of SQL Server for maintenance purposes without affecting other applications.
3. It is impossible for a support engineer to be aware of and understand the other applications using the database server. As such using a separate instance helps simplify the work of anyone supporting Booking Pro.
4. A small number of features will only work if the Booking Pro database is installed on a "bprsolutions" instance of SQL Server (e.g. using data within Microsoft Office without have to export the data every time).

Can I create the Booking Pro database on an existing SQL Server (e.g. one being used by SIMS)?

Whilst it is technically possible to create the database on an existing SQL Server we would recommend against it for the reasons given above. In particular we would strongly recommend against creating the database on an instance of SQL Server installed specifically for another software application (e.g. SIMS) as that Vendor's support staff will probably have no knowledge of or even the existence of Booking Pro and may make recommendations which could compromise the integrity of the Booking Pro database resulting in unnecessary downtime or even loss of data.

Can I create the Booking Pro database on a "default instance" of SQL Server?

Again whilst this is technically possible, and not as risky as creating it on another applications instance of SQL Server, we would still recommend that you install a separate instance of SQL Server for Booking Pro as it makes support much easier.

Can I use "Windows Authentication" to connect to SQL Server?

Booking Pro supports "Windows Authentication" but we would only recommend that you use it if you (and anyone who might stand-in or succeed you) have a full understanding of security in SQL Server. If that might not be the case then we would strongly recommend that you install Booking Pro using the approach described above. However if you choose to use "Windows Authentication" then you should be aware of the following:

1. When creating a new database you must be logged onto to Windows as a User with the necessary permissions to create a new databases. Failure to do so will result in an error being reported and Booking Pro will not work correctly.
2. The Windows accounts of each individual user of Booking Pro must be given explicit permission to use the Booking Pro database. The level of permission required is "db_owner". (This would normally be achieved using Microsoft's either "SQL Server Management Studio or using "Active Directory".)
3. Whenever a new user requires access to Booking Pro you must give their Windows account access to the Booking Pro database as described in point 2 above.

Why does each user need to be a "db_owner"?

Users need to a "db_owner" to gain access to the full range of features available in Booking Pro. In particular this includes being able to download new updates and have any schema changes automatically applied.