Case Studies


We continue to develop our .NET Provider for OLEDB. In the new build (#1434), we have implemented the methods to obtain database metadata:

  • OleDbConnection.GetOleDbSchemaTable
  • OleDbConnection.GetSchema

GetOleDbSchemaTable

Supported schemas:

  • SchemaGuids
  • DbInfoKeywords
  • DbInfoLiterals
  • All schemas of the OLEDB Provider

Distinctions compared to standard OLEDB.NET Provider:

  • The SchemaGuids schema describes all schemas including SchemaGuids, DbInfoKeywords and DbInfoLiterals.
  • The SchemaGuids schema supports restrictions for the Schema column.

GetSchema

Supported schemas:

  • MetaDataCollections
  • Restrictions
  • DataTypes
  • ReservedWords
  • DataSourceInformation
  • CharacterSets
  • Collations
  • Tables
  • Views
  • Columns
  • Procedures
  • ProcedureParameters
  • ProcedureColumns
  • Indexes

Distinctions compared to standard OLEDB.NET Provider:

  • The MetaDataCollections schema supports restrictions for the column CollectionName.
  • The Restrictions schema supports restrictions for the columns CollectionName and RestrictionName.
  • More accurate population of the DataSourceInformation schema.
  • More accurate population of the Restrictions schema.

Implementation peculiarities

  • Caching of data from its own schemas (SchemaGuids, DbInfoKeywords, DbInfoLiterals, …).
  • Coherence of information from metadata schemas with the descriptions of the resulting rowset columns and command parameters (ensured by IBProvider).
  • Different algorithms of metadata loading for Interbase and Firebird. Including – our provider takes into account the version of the server and the version of database ODS (ensured by IBProvider).
  • Caching of OLEDB metadata schemas is carried out on the IBProvider level (see a property «schema_cache»).

Other changes

  • The OleDbSchemaGuid class added with the lists of known OLEDB schema identifiers.
  • The OleDbSchemaRestriction class added with the lists of restriction indexes for known OLEDB schemas.
  • The OleDbLiteral class added.
  • The OleDbMetaDataCollectionNames class added.
  • The number of tests and debug structures ensuring the correct work of components increased.

New examples

If you are interested in working with stored procedures grouped into PACKAGE, please take a look at the new example for our .NET Provider:

  • Creation and working with PACKAGE (C#, FB3)
  • Nikolay Samofatov wrote about his Large Iron production systems that he maintains :

    We run Firebird to power larger systems (for 12 government agencies and 3 banks).

    It has approximately 100000 end users multiplexed through 2500 (max) pooled connections.

    Here is the snapshot of nearly idle system at night:

    top - 03:20:39 up 10 days,  8:39,  7 users,  load average: 2.08, 1.87, 2.15
    Tasks: 1732 total,   1 running, 1730 sleeping,   1 stopped,   0 zombie
    Cpu(s): 11.9%us,  4.0%sy,  0.0%ni, 83.5%id,  0.0%wa,  0.0%hi,  0.6%si,  0.0%st
    Mem: 529177288k total, 378587600k used, 150589688k free, 761532k buffers Swap: 1073741816k total, 130612k used, 1073611204k free, 333281232k cached
    
    [root  mvv bin]# ps aux | grep -c rdb_inet_server
    719

    Database is on a small FusionIO drive:

    mount:
    /dev/fiob on /mnt/db type ext2 (rw,noatime)
    df -h:
    /dev/fiob             587G  423G  135G  76% /mnt/db

    Also later he mentions that he uses 2TB of RAM machines

    Chipsets that can handle 2 TB of RAM and 8 CPU sockets (<=80 cores, <=160 threads) are the largest “commodity” type hardware available now. These are the largest systems we worked on. 8 GB of lock manager space per database should be just enough for them. With the allocation error check in place we’ll have this problem solved for the next year or two until larger systems become common.

    New Firebird case study from wobe-systems GmbH, German software development house for the graphics industry.
    “…A production database of 100 GB and more containing BLOBs is nothing unusual at our customers sites…”
    “.. Firebird SQL server is at the core of our system helping our customers swift and safely through their daily work. Equipped with near zero administration and ample possibilities of scalability Firebird SQL database offers an operational reliability that does meet the requirements of industrial and time critical applications.”

    Read full article here.

    Beside being free (both as beer and also open source), you don’t need 24×7 DBA and there are generally less headaches. Here’s a nice example explained by Norman Dumbar in a mailing-list post. Norman administers over 600 Oracle databases and about 40 Firebird ones:

    A new case-study was added to FirebirdSQL site. It is always interesting to ready such articles, and know about other companies experiences with Firebird. This time it is about DRB Systems moving from InterBase 6 to Firebird to solve stability problems. Read more.

    Take a look at the new case study published in the FirebirdSQL site. Interesting that they choosed Firebird over Oracle, and cost was not the only factor. Worth reading!

    There are other case studies published in the site. Make sure to read them all, and if you have an interesting case to show, contact the moderator to know how to publish it there.


    This Firebird & Interbase WebRing site owned by Carlos H. Cantu .
    [ Previous 5 Sites | Previous | Next | Next 5 Sites | Random Site | List Sites ]