Creating a special LoBDb.NET database is an essential step when working with the LoBDb.NET platform. Such a database is not empty, but contains a number of service tables, views and stored procedures. An easy way to create it is to take advantage of the GUI of LoBDb.NET Manager.

1_1_start.png

The left panel of the main window displays all registered connections to different LoBDb.NET databases. At the moment this panel is empty. Press New Connection to create a new connection.

1_2_connection_window.png

If you do not have a LoBDb.NET database you can connect to created yet then press Create Database to create one. Creating a LoBDb.NET database is supported only for SQL Server starting from 2005 with the service pack 2 and for Oracle starting from 9i. The process of creation can be divided into two steps. First of all, LoBDb.NET Manager connects under the account of a privileged DBMS user and then creates an empty database and an application user that will be the owner of that database. After that, LoBDb.NET Manager connects under the application user account and creates all service tables, views and stored procedures and finally the first administrator of the database.

1_3_installation_window_sqlserver.png

The picture above shows an example of the fields populated for the case of connecting to SQL Server.
  • Drive Type determines the target DBMS which is MSSQLSERVER in the case.
  • Driver is the name of the ODBC driver to be used (SQL Server).
  • Host defines the DBMS server location which includes a computer name or an IP address and a name of an SQL Server instance.
  • Port Number can be omitted if it is equal to the default value for the target DBMS.
  • Database is the name of the new LoBDb.NET database.
  • Superuser specifies the name of a privileged DBMS account that has all necessary permissions to execute the script of creating an application user.
  • App user is the name of the application user to be created.
  • Admin user defines the name of the first user to be registered in the LoBDb.NET database as an administrator.
1_3_installation_window_oracle.png

The picture above shows an example of the fields populated for the case of connecting to Oracle. In that case the Database field is used to specify the target service name which is XE.

1_3_1_installation_window_skip_app_install.png

If you do not trust LoBDb.NET Manager to execute any scripts under an account of a privileged DBMS user, you can execute the script of creating an application user manually. When you set the Skip the application user installation checkbox LoBDb.NET Manager assumes that the application user is installed and it has all necessary permissions to create all service tables, views and stored procedures. In order to view the script of installing the application user you should press the View the app user installation script hyperlink. That script is generated based on the values in such fields as Driver Type, Database, App user and App user password.

1_3_2_installation_window_view_app_script.png

When all required fields are populated you can press the Create button and the process of installation takes off. After the installation is completed press the Connect button.

1_5_connection_window.png

Most of the fields on the form for connecting to a LoBDb.NET database are populated based on the values used when creating that database. LoBDb.NET Manager uses the first admin user account in order to establish a connection.

Please specify for the User name field only those users that were registered using the LoBDb.NET platform but not the application user account and not the superuser account you used for creating the application user.

Unset the Save user credentials in the connection string checkbox if you do not want to store you first admin user credentials in the LoBDb.NET configuration file. In that case you will have to specify those credentials each time you connect to the database. Change the value in the Alias field if you want to display a more user friendly name for the connection. After everything is ready press the Connect button and the new connection should appear in Database Explorer.

1_6_success.png

Last edited Jul 21, 2012 at 8:57 PM by mapase, version 7

Comments

No comments yet.