Hmm, isnt mysql GPL or $495, depending if your app is opensourced or not.iebidan said:
http://www.mysql.com/products/licensing/
Database with .NET
- Thread starter Madz
- Start date
http://www.mysql.com/products/licensing/
AlexCode said:That is one thing I may try one day...
Assemble a Linux Server to be a DB Server and try to manage it...
Im only waiting for the v5 witch will support SPs and Triggers among with other several very very nice features...
http://www.mysql.com/products/mysql/
Alex
SPs!
Access to the one of the fastest lightest freeist database engines while still allowing convience? Id move all of my data intensive projects over to mySQL then
michael_hk
Well-known member
Over 1/3 ppl are using Access, unbelievable.... 
Joe Mamma
Well-known member
lets hear it for hybrids!
Most of my apps use a jet DB for local data manipulation and configuration settings, even if the app uses a DB server for backend.
I dont care for Oracle, but then again my apps are mostly OLAP and not OLTP.
In that arena Oracle, in my experience, is over kill.
Lack of SPs and Views (and I think triggers too) rules out MySql.
Borlands Interbase is a great SQL-92 compliant database that should get more attention. I really love IBM (Formerly Informix) Universal Server. IBM-US is the standard for ORDBMS.
Mattise looks interesting.
Most of my apps use a jet DB for local data manipulation and configuration settings, even if the app uses a DB server for backend.
I dont care for Oracle, but then again my apps are mostly OLAP and not OLTP.
In that arena Oracle, in my experience, is over kill.
Lack of SPs and Views (and I think triggers too) rules out MySql.
Borlands Interbase is a great SQL-92 compliant database that should get more attention. I really love IBM (Formerly Informix) Universal Server. IBM-US is the standard for ORDBMS.
Mattise looks interesting.
Menge
Well-known member
im starting to take a look at MySQL.
ost
Well-known member
michael_hk said:Over 1/3 ppl are using Access, unbelievable....
Well it is posible to choose more than one database in the poll. I guess most people have tried to develop a small app with an underlying Access base.. Thats why i checked it Other than Access I use SQL-2000 ( my primary choice ). I have used both Oracle and My-Sql but mainly because the projects I was assigned to used these platforms
I really cant figure out what you have against Access DBs.
Is it possible that there are developers that only see SQL Server?
I think that the main problem here is a base problem.
A developer that only sees one programing language and also one database engine didnt have a proper programing education...
Sorry for those who see themselfs in this scenario but... its true!
Alex
Is it possible that there are developers that only see SQL Server?
I think that the main problem here is a base problem.
A developer that only sees one programing language and also one database engine didnt have a proper programing education...
Sorry for those who see themselfs in this scenario but... its true!
Alex
ost
Well-known member
AlexCode said:I really cant figure out what you have against Access DBs.
Is it possible that there are developers that only see SQL Server?
I think that the main problem here is a base problem.
A developer that only sees one programing language and also one database engine didnt have a proper programing education...
Sorry for those who see themselfs in this scenario but... its true!
Alex
I dont think anybody have anything against Access. In IMO its a great application for creating smaller solutions. But if you have to create larger applications, few would choose Access because its not made to serve that purpose.
I absolutly agree with you...
The problem is that you see 90% of the developers ONLY working with SQL either on small and large applications.
Second, you see them, even on large applications, use SQL as a simple data repository... That Access or Fox Pro do as well...
You can see Access pointed as a lame tool by people who dont even know what a SP is...
If you deeply analyse 50% of the SQL based applications Im shure that they could be working as well as they are but in Access...
I think the guilt here can be pointed to Microsoft on its quest to promote SQL as the supra DB Engine, most of the times compromizing its own related products as Access and Fox Pro...
I just think that would be good for everyone that posts like the one from michael_hk
Just to clear things up... Im a VS.net developer, MCSD, MCSA, MCDBA, working with enything that more likelly will suite my DB needs... Access, SQL, Oracle, Fox Pro, mySQL...
Alex
The problem is that you see 90% of the developers ONLY working with SQL either on small and large applications.
Second, you see them, even on large applications, use SQL as a simple data repository... That Access or Fox Pro do as well...
You can see Access pointed as a lame tool by people who dont even know what a SP is...
If you deeply analyse 50% of the SQL based applications Im shure that they could be working as well as they are but in Access...
I think the guilt here can be pointed to Microsoft on its quest to promote SQL as the supra DB Engine, most of the times compromizing its own related products as Access and Fox Pro...
I just think that would be good for everyone that posts like the one from michael_hk
simply didnt had a point...Over 1/3 ppl are using Access, unbelievable....
Just to clear things up... Im a VS.net developer, MCSD, MCSA, MCDBA, working with enything that more likelly will suite my DB needs... Access, SQL, Oracle, Fox Pro, mySQL...
Alex
michael_hk
Well-known member
AlexCode said:I just think that would be good for everyone that posts like the one from michael_hk
simply didnt had a point...
Alex
I think no one will deny Access is a weak database, how many simultaneous user support can it support?? But I DO agree Access is good for some situation, like for a small app.
I am just surprised by the fact that many are using Access, NOT having anything against Access.
Joe Mamma
Well-known member
Hybridization!!!michael_hk said:
Jet (or BDE in Borland situations) is great for doing local processing and configuration management. Server for the enterprise wide portion of the app.
Now that JET can handle DDL outside of Access proper (MDAC 2.7 and above) this approach is fantastic.
I mean, christ, MS-SQL server uses the jet engine to do somethings.
At least that what I figure geven I couldnt delete some JET*.tmp files without shutting down my SQL server process.
samsmithnz
Well-known member
Ok, Im jumping into this conversation a year late... BUT. the main disadvantage with access as I see it, is that the connection initalization is too slow. Especially with the way Microsoft promotes only having a connection open for as long as you need it, an application using an Access database is noticably slower opening each database connection.
Nerseus
Danner
@samsmithnz:
MS recommends only keeping a connection open as long as you need it for multi-user applications, mostly those accessed through a common server - usually a webserver. MS Access is primarly single user. I would never open/close a connection on every query to Access. If you have a multi-user application, MS now recommends MSDE over Access.
-ner
MS recommends only keeping a connection open as long as you need it for multi-user applications, mostly those accessed through a common server - usually a webserver. MS Access is primarly single user. I would never open/close a connection on every query to Access. If you have a multi-user application, MS now recommends MSDE over Access.
-ner
"... the connection initialization is too slow"
We can use connection pooling.
"...MS now recommends MSDE over Access"
The deployment is the big issue. We cant compare the two on this field.
We sell about 6 apps on top of an Access DB... we just have to add the .mdb file to the installation...
"...MS Access is primarily single user."
Agree and disagree. I believe it was meant for a single user access but it behaves very well on a multi-user scenario. The problem isnt how many people access the mdb file, its:
- How many field changing queries (Updates, Inserts & Deletes)
- The amount of records processed per query
- The amount or existence of concurrency
- The predicted DB growth
- The predicted DB Clients growth
For me, these are the factors that make me choose between MS Access and a SQL Server Engine (MSSQL Server 2000, MySQL or Oracle).
Alex
We can use connection pooling.
"...MS now recommends MSDE over Access"
The deployment is the big issue. We cant compare the two on this field.
We sell about 6 apps on top of an Access DB... we just have to add the .mdb file to the installation...
"...MS Access is primarily single user."
Agree and disagree. I believe it was meant for a single user access but it behaves very well on a multi-user scenario. The problem isnt how many people access the mdb file, its:
- How many field changing queries (Updates, Inserts & Deletes)
- The amount of records processed per query
- The amount or existence of concurrency
- The predicted DB growth
- The predicted DB Clients growth
For me, these are the factors that make me choose between MS Access and a SQL Server Engine (MSSQL Server 2000, MySQL or Oracle).
Alex