Access Database or Sql Database-which differences?

[PT Exorcist]

whats their differences? why choose one or another?

[Cander]

Access for single user desktop apps. SQL Server for multi user applications.

[TheExtreme]

"Just my opinion"
Access is a horrible excuse for a database it gets dog slow after 10,000 records too. MSDE (Desktop SQL) should be used in almost all cases. MSDE makes upscaling to full blown SQL with almost no changes. Consider the providers you must use.

[Slow_Learner]

Needless to say, if you have any users who are using Windows98 then you can't use MSDE/SQL (at least not locally).

[Pirate]

Originally posted by TheExtreme
"Just my opinion"
Access is a horrible excuse for a database it gets dog slow after 10,000 records too. MSDE (Desktop SQL) should be used in almost all cases. MSDE makes upscaling to full blown SQL with almost no changes. Consider the providers you must use.

To some extent yes , but access is faster and meant to be the ideal option sometimes , MSDE needs a lot to learn stored procedures but not access (it uses regular and common SQL statements ) ......Just a thought

[hellswraith]

Originally posted by Pirate
To some extent yes , but access is faster and meant to be the ideal option sometimes , MSDE needs a lot to learn stored procedures but not access (it uses regular and common SQL statements ) ......Just a thought

MSDE can use regular and common SQL statements also. Access is not faster than the MSDE. If it is, I would like for you to show me where you get the numbers from.

If you are a regular desktop user that doesn't know how to program and need a database to query, that is where Access fits in.

If you are a programmer and storing/retrieving values from a DB, you should be using MSDE. First of all, you can use it for free and redistribute, and second it is faster and more scalable for later.

[Edneeis]

I'd have to say Access' strength is its portability. You don't need to install anything or run any scripts. Although having said that, I almost always go with SQL.

[Pirate]

Originally posted by hellswraith [B]
MSDE can use regular and common SQL statements also. Access is not faster than the MSDE. If it is, I would like for you to show me where you get the numbers from.

When I said faster ,sorry , I meant you can build it quicker than MSDE . If you one don't know these stored procdures , then can't get full performance over his MSDE .

If you are a regular desktop user that doesn't know how to program and need a database to query, that is where Access fits in.

I agree %100 .

If you are a programmer and storing/retrieving values from a DB, you should be using MSDE. First of all, you can use it for free and redistribute, and second it is faster and more scalable for later.

only for storing huge data I guess .

[Pirate]

Originally posted by Edneeis
I'd have to say Access' strength is its portability. You don't need to install anything or run any scripts. Although having said that, I almost always go with SQL.

definitely, Ed .

[VBCrazyCoder]

Also, I think Access still has a size limitation of 2 gigs, unless 2002 got rid of this - but something to be aware of.

[hellswraith]

I am trying to remember, but Access was supposed to go over to using MSDE wasn't it. It might be right now, not sure.

[Lunatic3]

Access is a horrible excuse for a database it gets dog slow after 10,000 records too

You make me think of moving one of my applications from Access 2002 to MSDE. IT already has about 10000 records and it soon will be doubled. So if they are going to face a performance problem then I should change it as soon as possible

[Pirate]

hellswraith , well done . The forum is nice . Keep it up !

[hellswraith]

Originally posted by Pirate
hellswraith , well done . The forum is nice . Keep it up !

Thanks. It is pretty much my first 'full' attempt at using asp.net. I got to tell you, I love asp.net. Now if I only could get better at the design and styling aspect of web development. I am a programmer not an designer....lol.

Thanks.

And to keep this thread on topic, I am using an SQL Server 2000 DB as the backend utilizing stored proceedures.

After really using stored proceedures in your apps, you won't want to go back. The code is seperated so your code doesn't get so confusing. Also, if you are getting the wrong results in your resultset returned from the db, you know exactly where to look. You don't have to go through all your code and look for the SQL query string that is calling it. Plus, you can call the same proceedure from multiple places in your code, and you don't have to worry about messing up the sql statement because you are always calling the same one (although, I create custom classes that control all access to the db).

A good book for learning SQL Server (most of the book applies to the MSDE also) is SQL Server 2000 Programming by Robert Vieria from Wrox publishing. I LOVE this book. I highly recommend it for anyone wanting to learn SQL Server and all the stuff you can do with it. I used mainly this book to learn SQL Server, and to pass the MS Cert test for SQL Server to get my MCSD.