The default database in which to store the data dictionary for a project is a SQLite database. SQLite is used because it's lightweight and doesn't require a separate database engine to be installed, configured, and maintained. However, if you wish to use a different database engine, such as the same one used by your application (SQL Server, Oracle, etc.), when you create the project choose other settings as discussed in the Creating a New Stonefield Query Enterprise Project topic.

Note that Studio comes with a file named ConnectionStrings.xml in its Data subdirectory that defines how different ODBC drivers, OLE DB providers, and .NET providers work. By default, it looks like this:

<providers>
    <provider name="System.Data.SqlClient"
        connection="System.Data.SqlClient.SqlConnection"
        specifier="database" filebased="false"
        extension="" assembly="System.Data.dll"/>
    <provider name="System.Data.Odbc"
        connection="System.Data.Odbc.OdbcConnection"
        specifier="database" filebased="false"
        extension="" assembly="System.Data.dll"/>
    <provider name="System.Data.OleDb"
        connection="System.Data.OleDb.OleDbConnection"
        specifier="database" filebased="false"
        extension="" assembly="System.Data.dll"/>
    <provider name="System.Data.SQLite"
        connection="System.Data.SQLite.SQLiteConnection"
        specifier="Data Source" filebased="true"
        extension="dat" assembly="x86\SQLite.Interop.dll"/>
</providers>

There are six attributes for each provider:

  • Provider: the name of the .NET namespace for the provider.

  • Connection: the name of the class used for the Connection object.

  • Specifier: the syntax used to specify a database name in a connection string. For example, for SQL Server, it's "database=DatabaseName," so this attribute contains "database."

  • filebased: "true" if the data engine is file-based or "false" if not.

  • extension: if filebased is "true," this contains the default extension for the database file.

  • assembly: the name and path (if necessary) for the assembly (.NET DLL) containing the provider.

If you're using something other than ODBC, OLE DB, Microsoft SQL Server, or SQLite, add another row to ConnectionStrings.xml and fill in the proper settings for your database engine.