Posts in Category: sql

Accessing Data with LiteDb

In my last post I talked about how easy it was to create a database with LiteDb.

But accessing your data is even easier.

To start off, assuming we have no document (i.e., structure) associated with our data – we can create a generic table on the fly using the built in BSonDocument structure.

In this example, I first use my database to get a collection of documents under “FirstTable”.  If it’s your first time creating this document, don’t worry, it’ll be created for you, so no need to do any “CREATE” mumbo jumbo.

var FirstTable = database.GetCollection("FirstTable");

Now I’m going to create some data.  The simplest, most brain-dead way to do this is to create a Dictionary, make some columns and give them whatever values I want that are of type BsonValue

Dictionary<string, BsonValue> docs															

Read More


Getting Started with LiteDB

Every project you do will have data and eventually you’re going to need to store that data somewhere.

And config files are such a pain to manage (and also so early 2000s) so as much as possible I try to use a database or some unit of storage.

And like anything you build, once you start building it, it takes on a life of it’s own that you twist and turn and wrench into something useful until one day you look at it and go – maybe storing our configuration in a 25,000 line XML file wasn’t the best idea?

So if it’s going to be a bad idea down the road, why not start doing the right thing from the get go – enter LiteDb.

LiteDb is an incredibly easy to use,

Read More


Tips for a Successful Dynamics365 Data Migration

When moving data from either a homegrown application or even a pre-existing Dynamics365 system there are few tricks that can save you a great deal of time and take your project beyond simply completing the data migration and to instead making it a cornerstone in the success of your migration to Dynamics365.  I’ve done a number of data migrations ranging from the small (less than 25,000 records from one database) to the larger (greater than 1,000,000+ records from a variety of databases).

Whether you are using tools like Scribe or Kingsway or building your own application – you should always use the available SDKs and not go to the database.  In writing that I feel as though as this is slowly becoming a double-negative as you cannot access the database directly for cloud instances of Dynamics365.

Check

Read More