This article is aimed towards providing the quick insight into ScimoreDB database server. A synopsis of what is covered is shown in
the Table of Contents, listed below. You can go to any topic listed in the Table of Contents simply by clicking on its title.
Database match your needs
At this point, it is assumed that you are interested in using ScimoreDB. If you had not yet made a decision, please take some time
to review the Introduction, Features and License pages.
Install and evaluate ScimoreDB
Embedded database installation is simple. Just go to download page, download either x86/x64 MSI package and install.
During installation, uncheck the "Server" feature. The MSI will install a manager GUI application and .NET provider. The .NET
provider "scimore.data.scimoreclient.dll" package embeds database engine. The application, using ScimoreDB embedded database
only need the provider. The provider works in 32 bit or 64 bit environment, depends of your application configuration. If your
application is .NET and platform independent, the provider will utilize 64 bit engine in 64 bit OS, or, 32 in 32 bit OS.
Next, check how to build your first ScimoreDB application Embedded database in 3 minutes. Additionally, check the Embedded database samples.
Are you looking for highly available, scalable database? Right, sounds like a lot of things to review. We will guide you how to
install cluster of 3 machines, verify it works. Add 3 more machines, verify it scales. Unexpectedly stop machines, verify it
failovers and continues operational. Please follow the distributed database example here....
We assume you already have an existing SQL Server, MySQL or other database. ScimoreDB is aiming to be close to SQL Server, yet, we
hope, importing some other database should be not that difficult.
Importing from SQL Server is easy. Start the Scimore manager and follow the instructions
here.... Alternatively, export the existing database tables to CSV files and import to Scimore
ScimoreDB Distributed and Embedded databases are not secure, by default. This is not such a good idea when you ship your product.
ScimoreDB has the mechanism to secure its data and integrity: sysusers and syspermissions tables. The tables are responsible for
authenticating user access to the ScimoreDB server, and subsequently associating those users granted access with a set of privileges.
These permissions set what a user is capable of doing while connected to the ScimoreDB, controlling the user's activities on a server,database and table level. There are 3 types of users in ScimoreDB security model: Administrator, Users and Database Roles. The Administrator is almighty who creates users/roles and grants the permissions. To secure the database (you might already guessed),
you need to create administrator. Click on the following example to learn how to secure the database,
create users/roles, and, grant, deny or revoke the privileges.
So you got running Scimore database. What’s now? Well, you may start by checking out some useful links:
- Freetext Documentation. Index documents using free text capabilities, provided by Lucene engine.
- Distributed schema. The article explains various data partitioning methods. It will help when design scalable databases.
- Connectivity. Various connection options, connecting to embedded or distributed databases.
- Backup/Restore. How to Backup and Restore database.
- Monitoring - Explains the system and monitoring tables. ScimoreDB expose many activity and configuration details, such as current memory, network usage, transaction statistics, or, active connections details. It's quite useful for troubleshooting and database activity monitoring.