MSDE vs Access

[wyrd]

I believe this was asked some time ago, unfortunately I couldn't find any thread on it (maybe I was dreaming things up again) and since I haven't looked at any database programs in probably 3 months, I've forgotten.

 

In any case, I was wondering what would best be suited for a small business application that was going to be used on a single computer; MSDE or Access? Or does it not matter?

 

I just can't keep up anymore with all this darn school stuff. It's making my poor brain hurt. :( Data Structures with C++ in one class, Assembly in another, Philosophy in another... and some other class which I forget what the heck we're even doing, and still trying to keep up with .NET and Microsoft. Life is such.

:eek:

[hog]

I was the one asjking this and the upshot was in this situation stick with Access. :-)

[Nerseus]

If this is mostly for you to learn DB stuff, I'd definitely stick with Access. It's *much* easier to setup, connect to, backup (copy a file!), etc. etc. The only real difference in .NET is in the providers - I think you can use the SqlClient objects for MSDE (though I'm not 100% sure), whereas Access will use the OleDbClient objects.

 

The other objects (DataAdapter, DataSet, DataReader, etc.) are the same since they're in System.Data, not specific to OleDb or Sql.

 

The usual reason to choose MSDE in the "real world" is to more easily port any queries, tables, etc. into SQL Server if your app demands that level of database support.

 

-Nerseus

[wyrd]

So in other words, you have no idea? :D

 

Both Access and MSDE are easy to connect to, Access uses OleDb and MSDE uses Sql. MSDE, as far as I can tell, is almost identical to SQL Server. You can even use triggers and stored procedures.

 

As I said I'm looking for the best solution for a small business application. I'm interested in performance, not ease of use.

 

I'll try and find an answer on MSDN (if there even is one).

[hog]

wyrd read my thread about this I posted some weeks ago as there was a lot of discussion about it. It may help you decide

[wyrd]

Thanks hog.. I had to do some more searching to find it (I couldn't find it the first time, but being smart this time I searched using your name).

 

http://www.xtremedotnettalk.com/showthread.php?s=&threadid=70921&highlight=MSDE

 

To only prove how bad my memory is.. I actually replied in that thread;

 

Access is perfectly fine for a "small" business.

 

However you'll want to change to MS SQL eventually (MSDE will work fine for development). It's much more efficient to use for larger apps. Also the .NET framework offers a specialized namespace just for the SQL Server (rather then using OleDb), which is made to take advantage of SQL Server and give you faster programs overall.

 

Perhaps I should see a doctor about my lapse of memory problem. :eek:

[hog]

Ah, how I chuckled reading this.......so I'm not the only one who is loosing memory at a rate of knots!!

[APaule]

So did rereading your thread :D answer your question, or do you need more info?

[Robby]

So wyrd, you needed help with something that you had already helped someone else on previously? Just pulling your leg. :eek:

[wyrd]

Robby:

Seriously, you have no idea how bad my memory is. If I don't use something (in this case MSDE and .NET) for about 3 months or longer, I have to basically relearn 99% of what I knew previously. It makes me wonder how I'm able to program anything...

[hog]

wyrd! dude we must be related in some way? I am forever complaining to my wife about the very problem you have. 9/10 if I start a new app and require a certain feature I know I've learned before I got to that app, import it and modify it as I can never remember how I did it until I read my comments!!

[jfackler]

Wyrd,

Check my profile.

We have drugs for that.....now of course there are also drugs that cause that.

 

Jon

[wyrd]

You mean there are drugs that allow me to retain memory for longer periods of time? Interesting. What are they called so I can ask my doctor about 'em. :)