#1
  1. No Profile Picture
    Registered User
    Devshed Newbie (0 - 499 posts)

    Join Date
    Jul 2010
    Posts
    13
    Rep Power
    0

    C# and local database


    Hi there,

    I am doing application (short info so you get the idea what I do):
    i got employees
    i got objects (where they do whatever they do)
    i got shifts (time, object, employee)
    and from that I am gonna give outputs like: monthly hours reports, person reports, object reports and so. It's gonna be operated by one user at time only.

    Program will run only on one computer, so I need to find way how to easy store data. I am still university student, and here they learn us how to make own data structures like Btree or so. I believe it's good for learning to code, but not for RL praxes.

    I use C#, Visual studio.
    So I need advice about what would fit this best. I did some research and I believe installing mySQL would be pointless? I mean there are more simple solutions. I've read I can create some local database in VS (mdf files), but no idea whether it's good idea to try to go with that. I also read about SQLite, FireBird.

    But as I said, I have no experience with this, and I do not wanna make mistake at the beginning, when I am choosing what to work with. I need to thing about some backups mechanism and so.

    Any experience with these solutions would be appreciated!

    conta
  2. #2
  3. ASP.Net MVP
    Devshed Specialist (4000 - 4499 posts)

    Join Date
    Aug 2003
    Location
    WI
    Posts
    4,378
    Rep Power
    1510
    Your best options are Sql Server Compact Edition, Sqlite, and MS Access.

    Sql Server Compact is nice because it's easy to deploy with your app and is syntax and upgrade compatible to a full edition of Sql Server, including Sql Server Express, should the day come when you need to provide access for multiple workstations.

    Sqlite is nice because there's a fully managed provider available (can be compiled into your main app's executable) and because a lot of people use it for small apps.

    MS Access is nice because the driver is already built into Windows (there's nothing extra to deploy or include at all) and because if the need arises you can open the database with Access to fix something. It's less nice because it uses some very non-ansi standard syntax for a few things (it's not very portable or upgradeable).
    Primary Forum: .Net Development
    Holy cow, I'm now an ASP.Net MVP!

    [Moving to ASP.Net] | [.Net Dos and Don't for VB6 Programmers]

    http://twitter.com/jcoehoorn
  4. #3
  5. No Profile Picture
    Registered User
    Devshed Newbie (0 - 499 posts)

    Join Date
    Jul 2010
    Posts
    13
    Rep Power
    0
    Thanks!

    I am gonna check out SQLite.
  6. #4
  7. No Profile Picture
    Registered User
    Devshed Newbie (0 - 499 posts)

    Join Date
    Jan 2012
    Location
    delhi
    Posts
    4
    Rep Power
    0
    yes it makes your task easy....

IMN logo majestic logo threadwatch logo seochat tools logo