SQL isn't used commercially for giggles.
So we could store some indexes and stop reading the file if we got what we want?Quote:
Yes they are just binary files, but i assure that the lookup a SQL server performs on the binary file is significantly faster than the lookup that the standard 5165 server performs.
SQL would be out of the job if anyone could just write a simple binary search and beat them on speed.
Oh sure you could do things to optomize your access to binary files, but whats the point when you could just use sql?Quote:
So we could store some indexes and stop reading the file if we got what we want?
Please answer to that, because i dont rly know if i got it right. (im not fighting for flat-files)
Also do you have an article about how/why binary files are that fast? All i know by now is coz it stores them in 0 and 1 which means the computer can understand it right away without need to convert it.
By the way... dont bring Tanels 5165 into that.. we both know.... its not the best ;)
The "lookup" or reading on the binary file should be the same speed. Granted it'll be slower because the code is managed vs native SQL server, the core functions are the same speed. Reading one value from a binary file vs querying one value from a SQL server - the binary file wins hands down. Think about it.Quote:
Yes they are just binary files, but i assure that the lookup a SQL server performs on the binary file is significantly faster than the lookup that the standard 5165 server performs.
SQL would be out of the job if anyone could just write a simple binary search and beat them on speed.
Kinda disagree.. IMO MySQL is better, specially when it comes to portability to my knowledge MSSQL isn't portable, and well windows is already slow compared to other platforms (regarding i/o, and I know you can possibly run it on other platforms as well. A Linux distro for instance using WINE, but isn't it better if it was built specifically for Linux?).Quote:
MSSQL > MySQL
I agree, straight reading from a binary file is faster, but in terms of a database theres practically no contest.Quote:
The "lookup" or reading on the binary file should be the same speed. Granted it'll be slower because the code is managed vs native SQL server, the core functions are the same speed. Reading one value from a binary file vs querying one value from a SQL server - the binary file wins hands down. Think about it.
The reason why people say SQL is faster than managing your own database is the time thats spent sending data over a connection (even a local one - it still takes time) is made up for. Opening a file is a big task, and SQL database get rid of/lessen this need (in a variety of ways). The reading is not any faster. Reading a binary data file for one thing (such as a map file) is faster than querying a database for the same information.
MSSQL far outperforms MySQL on super huge databases. I personally would use MySQL no matter what because as you said, it's portable and it's also free, but that doesn't change the fact that MSSQL has better performance.Quote:
Kinda disagree.. IMO MySQL is better, specially when it comes to portability to my knowledge MSSQL isn't portable, and well windows is already slow compared to other platforms (regarding i/o, and I know you can possibly run it on other platforms as well. A Linux distro for instance using WINE, but isn't it better if it was built specifically for Linux?).
yea mysql is select, insert and know the exactly place to do it.Quote:
my topic at hand was not of binaries. mysql is selected almost same way as you may think binaries is... its mysql only SELECT or INSERT into is mysql not binaries so backup think about it get back to me on that one