sqlDb vs OleDb

[ThePentiumGuy]

hey,

im just wonderin whether Sql is better than Ole databases or vice versa?

The only problem i have with SQL (mySQL.. i used MSDE) is that there's no file associated with it! its all stored... somewhere, there's no specific database file on a certain location on your hard drive! does this hold true with oleDb's ?

 

also i realize that an Acess db = 'mini' sql db - and you can actually create files - does anyone know of a link/resource/tutorial for accessing an Access db?

 

thanks,

pent

[Mister E]

With SQL Server, there's an actual file on your system. It's an .mdf file, but it's not directly accessible by the user. Basically, you need to use something like Enterprise Manager to interface with the database.

 

In terms of a database, SQL Server is far robust than Access. SQL Server supports much more functionality, mainly with things like Stored Procedures. Access really is just a basic DBMS designed for simple projects.

[ThePentiumGuy]

I think i'm gonna go with access here :),

thanks.

[VBAHole22]

SQL Server definetly has more functionality but the shift between Access to SQL Server should not be taken lightly. It requires a major adjustment in the way you think about the database and interact with it. I often find myself using Access as a client to interact with my SQL Server databases. The SQL Server interface is difficult to get used to coming from an Access background. The whole element of the database changes from something that YOU created and YOU interact with to something that is being served up for everyone. Some of the most frustrating things for SQL Server beginners with Access backgrounds are things like getting the number of records in a query result set, setting up queries without a fancy grid, where in the world are the forms?, drag and drop relationships.

There are others. For those thinking of making the leap Access provides the project. An Access project acts like a shell around a SQL Server db. You have access to all of the objects in the server db but you can work in the friendly confines of Access.

[ThePentiumGuy]

Eh..

I'm not really using this for anything big and all. Mainly for experimentation ..etc. Just want to make some games and store data into a db as 'save game' data - so I honestly don't need that robust functionality lol.

 

Thanks dude,

pent

[PlausiblyDamp]

Still worth considering SQL as with SQL 2005 (formally Yukon) you can have the Express version, which can be used without the need to install a server as such, but still uses the same core engine as the full SQL product (stored procs, views, functions, security etc) and is 100% compatible with the full server product (usual disclaimers about beta software apply ;))

[Joe Mamma]

and Access is not a true Relational Database.

[VBAHole22]

There are no 'true' relational databases.

[ost]

and Access is not a true Relational Database.

 

A little off subject here, but can you please elaborate?

Edited August 11, 2004 by ost

[samsmithnz]

and Access is not a true Relational Database.

 

yet its more of a relational database than mysql.