C# and a free database ?

[bambo]

Hey everyone!

I'm new to C# and need to rewrite an old access application in C#.

It should be on a small budget so SQL Server License or such is not an option.

I'm wondering what database to use - so far I'm considering two options:

1. MDB- already exists, but I can't seem to find any good tutorials for connecting it with C# - any tips on that ?

2. MYSQL - I haven't worked with that before. it seems like a good option, but again- can't seem to find tutorials for it with C#


thanks for any comments/ tips in advance,
Bambo

[dglienna]

MSDE is a free version of MS SQL Server, but cut down.

[kaihirst]

Hi,

first question.

Has anybody used MSDE yet? Its terrible and extremely hard to work with!!!!

there ar elots of good tutorials on C#. some fo the ones I use to referr are .

www.msdn.microsoft.com (of course.)
www.dotnetspider.com
www.csharp-station.com

Theres a few, but doa search, theres loads.

with regards to using mySQL, jsut get a connection string, and develop usign ADO.NET and applied C# programming, and youre away.

www.connectionstrings.com

here youll find the connection string to connect to mySQL. To download it, visit the site and select whats right

www.mysql.com

its a bit of anass to set up, but once you get it, youll be glad!!

Also, if youre interested in developing with a larger scale database, you can download a copy of Oracle developer free, if you can register as theyre sites sh*t.

www.oracle.com

hope this helps

ta

kai

[jmcilhinney]

If you've already got the MDB then you may as well just use that, for now at least. Any ADO.NET information applies to connecting to Access. If you read the examples that Microsoft provide, they are all for the SqlClient namespace and SQL Server, but all you have to do is use the OleDb namespace instead and there is an almost perfect 1:1 correspondence between the members, e.g. SqlConnection <=> OleDbConnection. Just get the correct connection string from www.connectionstrings.com and you're set. If you want to upgrade to a more fully featured database then I'd say MSDE or MySQL would be the way to go. Accessing MSDE is exactly the same as for SQL Server. To configure MSDE in the first place try here: http://www.codeproject.com/database/ConfigureMSDE.asp

[bambo]

Thanks for all your replies!

Let me get this straight:

1. What are the limitations of MySQL - DB Max size, Max users simultaneously, efficiency , reliability etc. ?

2. What are the other advantages of bigger DB's such as SQL Server and such?

3. Is MSDE completley free ?

Thanks again,
Bambo

[dglienna]

1 Not sure, but mysql works better with more users than MSDE

2 More concurrent users

3 Yes, but limited number of concurrent users. You can buy tools for $50

[mendhak]

1. In MySQL, the size of the database is limited to OS factors. For example, the db can be 4GB on a FAT32 partition and 2TB on an NTFS partition. MySQL handles concurrent users well. Many intensive forums using vBulletin use MySQL and it handles the load effectively.

[RobDog888]

2. MS SQL is more powerful and includes utilities and tools like Query Anaylzer, Profiler, and Enterprize Manager.

[Hack]

Hey everyone!

I'm new to C# and need to rewrite an old access application in C#.

It should be on a small budget so SQL Server License or such is not an option.

I'm wondering what database to use - so far I'm considering two options:

1. MDB- already exists, but I can't seem to find any good tutorials for connecting it with C# - any tips on that ?

2. MYSQL - I haven't worked with that before. it seems like a good option, but again- can't seem to find tutorials for it with C#


thanks for any comments/ tips in advance,
Bambo

To me, some of the most important questions have not yet been asked.

How many people will be using this application? How many concurrently (if any)?

Is it to be networked?

What are your reporting requirements?

Over a years time, how many records will that database have? Must they all be available in real time, or can you "clean" up your database by deleting or archiving old records?

MySQL has its own web site. Have you visiting that site and looked at what they have to offer and how that would fit in with your existing needs?

[bambo]

Thank you all for your replies.

the database is for max 15-20 concurrent users, database size is small and should not exceed 20MB in the future (MDB size) . I do archive old records once a year in a different db file.

The database is to be networked in the near future. 1-3 network users will need to access the database remotley.

network access together with reliability are the main reasons to move from MDB.

I've considered upgrading to SQL Server but the license costs (server+ clients) is just too dear.

after going over few options, I'm thinking to go for MSDE. It seems like it works the same as MS SQL , without any real limitiations to my db scale. it's free, and upgrades to MS SQL costs are basically buying licenses.

considering my database, do you have any thoughts why not to upgrade to MSDE ?

Thanks again,